4 ms·
I never use tools either. By choice. I want to "touch" every line of code as intimately as possible. I want to immerse myself in it, to feel it, smell it, to
by edw519 19y ago
I never use tools either. By choice. I want to "touch" every line of code as intimately as possible. I want to immerse myself in it, to feel it, smell it, touch it, and taste it. I want as much of my code as possible to become part of my brain's firmware, much like Woz did when he designed the Apple II.
I have a personal rule that no variable name can be completely contained within another variable name (e.g. $Cust and $CustName must become $CustNbr and $CustName). This is the perfect application for a tool. Yet I never wrote it. I WANT to painstakingly walk through every line of code looking for this. I WANT it to hurt. I want to train my inner hacker to do things right the first time. What better way than to suffer the consequences?
We train our mind, our bodies, even our spirits. Why not also train our inner hacker? A few extra minutes per day is well worth it.
- nostrademons 19y agoI've found that I rarely know the right name for a variable until I've written a significant amount of code that depends on that variable. Refactoring's a must for me, because otherwise what the code says would have little relationship to what it does. I don't think this is due to a lack of foresight or planning (I do pencil & paper design notes before I start coding); it's more that in the process of coding, I discover abstractions and common code that that aren't apparent until the code's actually written.