4 ms·
Almost anybody who associates great programming with things like super keyboarding skills and muscle memory is unfortunately degrading the status of programming
by kamaal 14y ago
Almost anybody who associates great programming with things like super keyboarding skills and muscle memory is unfortunately degrading the status of programming to mere typing.
What is it that is so distracting and pulling you out of your zen when you use a mouse? Seriously you type so fast and code at the speed of thought that a little glitch here is like making a mistake with a Formula 1 car in the Monaco Grand Prix?
Let me tell you how real work happens and how productive people work. I am currently working with a very senior electronics guy in the night for some side projects. Watching him work shows me the path on how we programmers should be working. He will first build the base PCB with all his reusable designs and additional ones reading the documentation I rarely saw him Google anything in the past 15 days. If he has to ever get down to googling its generally to find some data sheet. Once that is done, he gets the components and meticulously builds the entire circuit on the PCB module by module. Every time he builds the module he tests if the inputs and outputs to it are as he designed on the PCB. It took a well whole month with each sitting spanning hours to get the whole PCB working. When he was done, the entire PCB worked like magic. The manufactured one's too. And there wasn't a single problem/bug. It was so spotlessly done. It looked like art work.
Yet the pace at which he solders, or used the CRO or multimeter hardly matters or is even relevant.
And yes, he hardly rushes or goes in a rash break neck speed in doing anything. So here is what I learned. Firstly learn to define the problem correctly, break the problem and establish a clear understanding of inputs and outputs to each module. Read documentation get a clear idea as to what it is done. Spend long hours trying to build/test each module. If possible automate testing(if its software). Spend time integrating.
Go slow, the biggest productivity leaks are not in going slow. Go slow but go steady. The biggest productivity problems are in problem definition, solution clarity, distraction and procrastination. For us programmers, let us be frank. Most of us don't RTFM. We jump to googling and then go down the time sink and end up reading all sorts of articles achieving nothing at the end of the day.
If possible work things out on the paper. Do use stuff like Mind Map for test cases. Learn to work things on the paper and by reading documentation. Learn good debugging tools, sound programming practices etc.
That is what counts guys. Not optimizing the 1 second delay needed to reach the mouse. That's not even relevant in the broad spectrum of things.
- richo 14y agoThat's all true, but I find when the heavens open and the True Path to implementation shines down upon me, being able to get thought onto disk at roughly the speed I think is important, as is knowing my editor well enough to let me manipulate my code in much the same way I'm manipulating the abstract representation I'm thinking about. In this instance I'm talking about vim, but it doesn't matter, being able to operate on code in a context that matches the way you're thinking about it is invaluable in my opinion. That said, I felt this was a bit over the top. While I totally think that this pays dividends, I don't think it enough to write a novella like he has.
- _pmf_ 14y ago> When he was done, the entire PCB worked like magic. The manufactured one's too. And there wasn't a single problem/bug. It was so spotlessly done. It looked like art work. Being bug free is nice, but not really the general case. I agree however that PCBs do need fewer iterations than software to become practically bug free. I am unsure whether, in the general case, this is due to the quality of the people doing PCB design or due to the quality of the PCB design process (and associated tooling). Another point is that in PCB design, there is (from my limited experience) a much stronger correlation between quality of the design and the quality of the implementation than in software projects. I attribute this to the lack of hand-off between the design and implementation stages, i.e. in PCB design the designer of the circuit is usually (not always) also involved in the routing process.
- kamaal 14y ago>>I agree however that PCBs do need fewer iterations than software to become practically bug free. I would say that is the case because making mistakes there is expensive. And yes the process they follow is generally far better than we do.
- eraldcoil 14y agoWell you get to a point where reaching for the mouse does get annoying. And it does happen, when reaching for the mouse distracts you from your "zen" state.
- 14y ago