I agree with this.

I agree with this. I think sometimes it's hard to keep the balance between the developers who want to 'do things right' but spend far too much time designing a perfect solution, as opposed to many coders who rush to 'get something done' and build systems which quickly become impossible to maintain. I think after about 5-6 years of coding was when I came to the realization that everything you build 'the best way' will become awful coding practice in a few short years. But that writing things at blazing speed just to hack it together and get to work invariably leads to code which is written to work a single way and is a nightmare to maintain. I try to build small, flexible solutions which are as adaptable and maintainable as I can, with the awareness that whatever I build will be looked as as archaic in a few years, but it might still need to be maintained and upgraded. So, slow down a little, think a little, code a little slower, but don't spend 6 months planning the perfect code weapon either.

Posted by silverbax88 on Jun 26, 2014, 8:52 PM

Tags

• reliability (Marketing)

Related issues

• When ads are inevitably folded into the prompts to the AI, I imagine it'll be fun for a bit to prompt the AI to react with disgust to the...
• My Thoughts on the Current State (Especially Quality Issues) and Future Development of Bun
• This is why I build static astro sites now for marketing and blog type pages.
• os: Setenv leads to SIGSEGV with GODEBUG=netdns=cgo, and other uses of cgo
• [L4D2 - Feature Request] 64-bit Builds of Left 4 Dead 2 (for at least Linux and Windows)
• While I think this is a great piece — especially the part about listening — and it's something we engineers all need to take to heart, I ...