This is a continuation of the earlier posts to enumerate funny aspects of software engineering practice:

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  

261. Build a product that gives all resources on lease forcing users to come back.  

262. Build a product that does not release reclaim resources when the users have marked it for delete forcing them to take the steps themselves  

263. Build a product that does not give the user to delete resources in bulk 

264. Build a product that makes it onerous on the user to click through confirmations 

265. Build a product that let’s hackers hijack user sessions 

266. Build a product that is purportedly safe only to find the maker violating privacy laws 

267. Build a product where the competition drives product features 

268. Build a product where the release timeline is primarily motivated by competitors  

269. Build a product where massive parallelizing of feature development implies human resources find their activities randomized throughout the week  

270. Build a product where the end users trust the product only to be told by hackers and researchers that it is not good enough