3 ms·
Call it "refactoring" and you're golden. ;-) For me, it's less about standards than about tools. I don't think software development is slow because of standard
by analog31 11y ago
Call it "refactoring" and you're golden. ;-)
For me, it's less about standards than about tools. I don't think software development is slow because of standards.
I don't use the same tool chain as the developers, so I'm oblivious to their standards. Their code is unreadable to me. I follow what would probably have been considered good practices 15 years ago when programs tended to be smaller. I actually learned good hygiene, but in the context of BASIC and Pascal in the 1980s, not the massive tool chains of today. And my programs probably look like a throwback to that era in terms of their conceptual structure.
I re-write early and often. Transforming a program is a good way to find out if it made sense in the first place.
- danieltillett 11y agoI have always considered refactoring as improving your current code rather than starting from scratch. I like to start over once I have a working approach for two reasons: 1. The original code is by that time I have finished hacking a mess and it is not a good place to start. 2. I can use the original code and the new code to find bugs I missed the first time around. A good percentage of the time I find bugs in my original code that only a clean rewrite exposes.
- analog31 11y agoThat's perfectly valid. In fact I did a re-write of a favorite code, a few weeks ago. It's something a colleague and I are working on, and I explained to him that I no longer trusted the old code because it was such a mess. Also, I try to incorporate new techniques that I've learned when I write new code.