It's actually really funny when you're showing a project to somebody, suddenly find a bug, think for a few seconds and then immediately understand the problem and fix it. To others it looks like magic. :>
Great article on why coders need peace and quiet!
In my former work, the most widely-used software (in an organisation of 27,000 staff) was written by rebels and spread virally. This article articulated for me why this might be the case. Having said this, the strength of the wider organisation was ensuring maintenance of the good code into the future to keep it useable. At some point, software tools have to be maintained and succession planning is needed. Backward written specs are better than no specs at all - that way the organisation has articulated what they want the software to do.
Nice article about the programmers view .. Same thing happens with me when my friends irritate me, I fell this that I am unable to reach the problem and so the solution does not come. Thats why I stay away from those people.
exactly how my mind works.
I had always carried with me a fear of becoming a small cog in a big company, because as a programmer, that's all I wouldn't want to happen. This article helped me to better understand why I had that fear, and to reach a better understanding of my future goals.
That's also how I program.
A good insight into the mind of the software engineer. I learned something about my own methods of development, as well as realizing why I get so annoyed by 'other work distractions'.
Good grief, I thought it was only me who had to get the program in my head to be able to 'know' it. I've always worked that way, and recognise all the points raised. Actually seeing it written down makes me realise that it's what I do and why I do and behave the way I do.
Cómo cargar tu programa entero en tu cerebro...
from: Good programmers manage to get a lot done anyway. But often it requires practically an act of rebellion against the organizations that employ them.
I remember doing this in high school back in the early 80's. It was very interesting and did indeed take some concentration.
Good tips :)
From the page: "A good programmer working intensively on his own code can hold it in his mind the way a mathematician holds a problem he's working on."