This is a continuation of the earlier posts to enumerate funny aspects of software engineering practice:
240) Build a product where the communication to explain how the product works consumes bulk of the time that could have otherwise been spent on test and development.
241) Build a product where the manual for the product is bulky and can become a headrest
242) Build a product where the user interface real estate is all cluttered up and there is no room to display anything new.
243) Build a product where users register through a third-party identity provider and cannot login to the product if there is an outage
244) Build a product where the home page is a mashup of different websites and the user has to squint at a small portion of the screen
245) Build a product where the forms are so big and large they are never completed in one sitting
246) Build a product that seems to have one form after another to fill on every page.
247) Build a product that shows ads or campaigns that distract the user from their workflows
248) Build a product that makes recommendations even when you want it to stop.
249) Build a product that chronicles every order and makes it creepy to anticipate your next order
250) Build a product that looks simple but when you click the advanced options, it becomes overwhelming.
251) Build a product that makes you think how to query the results
252) Build a product that gives no option to query other than scroll through the results.
253) Build a product that makes you go and forth between pages of search results
254) Build a product that does not let you order the results
255) Build a product that requires you to know the jargon or the domain with little or no warning for consequences.
256) Build a product that has clunky form to create a search criteria
257) Build a product where the forms don’t let you see the entire entry you type
258) Build a product where the forms don’t let you correct your mistakes
259) Build a product that does not let you rename your resources and you have to create more
260) Build a product that does not send out reminders.
240) Build a product where the communication to explain how the product works consumes bulk of the time that could have otherwise been spent on test and development.
241) Build a product where the manual for the product is bulky and can become a headrest
242) Build a product where the user interface real estate is all cluttered up and there is no room to display anything new.
243) Build a product where users register through a third-party identity provider and cannot login to the product if there is an outage
244) Build a product where the home page is a mashup of different websites and the user has to squint at a small portion of the screen
245) Build a product where the forms are so big and large they are never completed in one sitting
246) Build a product that seems to have one form after another to fill on every page.
247) Build a product that shows ads or campaigns that distract the user from their workflows
248) Build a product that makes recommendations even when you want it to stop.
249) Build a product that chronicles every order and makes it creepy to anticipate your next order
250) Build a product that looks simple but when you click the advanced options, it becomes overwhelming.
251) Build a product that makes you think how to query the results
252) Build a product that gives no option to query other than scroll through the results.
253) Build a product that makes you go and forth between pages of search results
254) Build a product that does not let you order the results
255) Build a product that requires you to know the jargon or the domain with little or no warning for consequences.
256) Build a product that has clunky form to create a search criteria
257) Build a product where the forms don’t let you see the entire entry you type
258) Build a product where the forms don’t let you correct your mistakes
259) Build a product that does not let you rename your resources and you have to create more
260) Build a product that does not send out reminders.
No comments:
Post a Comment