3 ms·
Being able to see edge cases and bugs before they happen will kill your productivity. I think the hardest part is to ignore those and deliver. If no one uses th
by z3t4 10y ago
Being able to see edge cases and bugs before they happen will kill your productivity. I think the hardest part is to ignore those and deliver. If no one uses the software, then no harm done, and if the software get popular you will hopefully get funds to pay back the tech debt.
- ph0rque 10y agoI think that knowing the most common edge case(s) will cause 80% of the bugs means you can solve (or design around) the most common issues and move on.
- laythea 10y agoDepends what kind of software you write. Wouldn't want to get into an aircraft that has software written to those standards.
- z3t4 10y agoIt would be great if programmers got more responsibility with increased skill and experience. But that is often not the case. There are very few jobs for highly skilled and experienced programmers and hackers.
- laythea 10y agoAgreed, as I said - depends on what you write. It's a shame that so much of the industry actually devalues the very thing that got us into this in the first place (presumably not just money, but some love of engineering quality software), degrading the job to be nothing more than "hacking" together something, just to deliver. It's not just delivering that is important (it is off course), but what is delivered, and if a company's non-techs don't realize and appreciate this, it's a slippery road.