another-dave

39 ms·

1. 481.▲
   by another-dave 10y ago

   I think it's just provided less incentive for developers to handle 'unhappy paths' within their app — there are still plenty of ways that you'd want a webapp to handle unexpected closure (e.g. user accidentally closing a
2. 482.▲
   by another-dave 10y ago

   I know your numbers are only an example, but taken at face value — if 8% of your users have an option set, maybe it's because you've overlooked a user-case that's valuable to them. In that case, having a configurable app that
3. 483.▲
   by another-dave 10y ago

   Sounds quite interesting to see how it will build up and to spot any patterns emerging in the results. Will give it a go over the next while. Cheers for sharing!
4. 484.▲
   by another-dave 11y ago

   > A hundred years ago, they'd be running a milling company, or figuring the best way to get rails installed, etc. Programmers today are also figuring out the best way to get Rails installed! :)
5. 485.▲
   by another-dave 12y ago

   " If you do have password requirements, show them to the user before they try to make a password. " & again as help text when they're logging in. Constantly have to reset passwords on obscure sites because I don't re