3 ms·
On GSD: You do this for long enough without ever cleaning up after yourself, and you're left with a massive, steaming pile of garbage that you have to then sup
by douche 12y ago
On GSD:
You do this for long enough without ever cleaning up after yourself, and you're left with a massive, steaming pile of garbage that you have to then support and maintain. Maybe you're lucky enough to be able to write fire-and-forget code, but in my experience, writing hacky terrible code to ship something just means that I'll have to spend 3-5x time on the phone troubleshooting with a customer, analyzing logfiles and then writing the code the right way in the end, than if I had just done things right to start with.
- vinceguidry 12y agoIt depends on the setting. If you're working in corporate world where the amounts of money flying around dwarf your considerable hourly rate/salary, then what they're paying you for isn't the quality of your code, and what you've written will probably just be thrown out after it's served its purpose. If you're having to maintain your own code long-term, absolutely. But that's not every job. It's good to get a feel for what's required from your boss and to keep in mind that the requirements can change from project to project.
- bane 12y agoThat is absolutely a fair point.