This is a continuation of the earlier posts to enumerate funny aspects of software engineering practice:
401) Build a product where the last mile before the release usually requires everyone to pitch in
402) Build a product where the pre-release efforts can never truly be separated from development efforts
403) Build a product where the last mile gathers unwanted attention even though they don’t have any direct dependence on the product.
404) Build a product where the announcements become something to look forward to both for people building the product and those waiting for it outside.
405) Build a product where the process of building never truly becomes a joyful process.
406) Build a product where the release of a product is never really a starting point for the next version
407) Build a product where the last few weeks for the release is usually reserved for making the customer experience better rather than during the development
408) Build a product where the Murphy’s law seems to be more applicable towards the endgame
409) Build a product where the week after the release still manages to throw surprises.
410) Build a product where the customer celebrations of their success with the product adds joy to the work involved during development but the hands that made the product are no longer there.
411) Build a product where the innovations are from the intellectual intellectual horse power as opposed to the forces shaping the product and find more maintenance down the road
412) Build a product where the people building their product leave a mark and recognition for themselves only to find it revisioned by the next batch
413) Build a product as a v1 in the market and the find the adage nothing remains unchanged holding more truth than ever before
414) Build a product where the product matures version after version and find its customers snowball with loyalty
415) Build a product where the establishment of a product allows ventures in sister products that also do well
416) Build a product where vendors vie to ship together.
417) Build a product where the knowledge about how the competitor products is never too far away.
418) Build a product where the patented innovations spawn open source substitutes and workarounds
419) Build a product where the dynamics of the people building the product shapes the product more than anything else
401) Build a product where the last mile before the release usually requires everyone to pitch in
402) Build a product where the pre-release efforts can never truly be separated from development efforts
403) Build a product where the last mile gathers unwanted attention even though they don’t have any direct dependence on the product.
404) Build a product where the announcements become something to look forward to both for people building the product and those waiting for it outside.
405) Build a product where the process of building never truly becomes a joyful process.
406) Build a product where the release of a product is never really a starting point for the next version
407) Build a product where the last few weeks for the release is usually reserved for making the customer experience better rather than during the development
408) Build a product where the Murphy’s law seems to be more applicable towards the endgame
409) Build a product where the week after the release still manages to throw surprises.
410) Build a product where the customer celebrations of their success with the product adds joy to the work involved during development but the hands that made the product are no longer there.
411) Build a product where the innovations are from the intellectual intellectual horse power as opposed to the forces shaping the product and find more maintenance down the road
412) Build a product where the people building their product leave a mark and recognition for themselves only to find it revisioned by the next batch
413) Build a product as a v1 in the market and the find the adage nothing remains unchanged holding more truth than ever before
414) Build a product where the product matures version after version and find its customers snowball with loyalty
415) Build a product where the establishment of a product allows ventures in sister products that also do well
416) Build a product where vendors vie to ship together.
417) Build a product where the knowledge about how the competitor products is never too far away.
418) Build a product where the patented innovations spawn open source substitutes and workarounds
419) Build a product where the dynamics of the people building the product shapes the product more than anything else
No comments:
Post a Comment