A Quote by Kent Beck

I'm not a great programmer; I'm just a good programmer with great habits. — © Kent Beck
I'm not a great programmer; I'm just a good programmer with great habits.
I think that's the responsibility of the CEO and the CEOs below me: to make sure that we're constantly putting people in places where they have the opportunity to develop into those careers but also having a rewards and recognition system that allows a great programmer to stay as a great programmer.
Testing proves a programmer’s failure. Debugging is the programmer’s vindication.
Because of the nature of Moore's law, anything that an extremely clever graphics programmer can do at one point can be replicated by a merely competent programmer some number of years later.
The programmer, who needs clarity, who must talk all day to a machine that demands declarations, hunkers down into a low-grade annoyance. It is here that the stereotype of the programmer, sitting in a dim room, growling from behind Coke cans, has its origins. The disorder of the desk, the floor; the yellow Post-It notes everywhere; the whiteboards covered with scrawl: all this is the outward manifestation of the messiness of human thought. The messiness cannot go into the program; it piles up around the programmer.
When we take the position that it is not only the programmer's responsibility to produce a correct program but also to demonstrate its correctness in a convincing manner, then the above remarks have a profound influence on the programmer's activity: the object he has to produce must be usefully structured.
It is a real service to humanity and the world to be a good programmer, particularly if you design great products. You make is easier for everybody, everybody has less headaches.
Before 'Dilbert,' I tried to become a computer programmer. In the early days of computing, I bought this big, heavy, portable computer for my house. I spent two years nights and weekends trying to write games that I thought I would sell. Turns out I'm not that good a programmer, so that was two years that didn't work out.
Finding a programmer to work with if you don't already know one will be a challenge. Merely judging if a programmer is exceptional vs. competent will be very hard if you are not one yourself. When you do find someone, work together informally for a while to test your compatibility.
You become a serious programmer by going through a stage where you are fully aware of the degree to which you know the specification, meaning both the explicit and the tacit specification of your language and of your problem. "Hey, it works most of the time" is the very antithesis of a serious programmer, and certain languages can only support code like that.
Writing was a way to get away from my life as a programmer, so I wanted to write about other things, but of course nobody wanted to publish another story about a family, unless it was extraordinary. When I began writing about my life as a programmer, however, people were interested.
When we look at these historical women and what they've gone through, it's shocking to recognize some of our own experiences in theirs. When you look at someone like Ada Lovelace who is the first computer programmer, during her lifetime doctors said that was really sick because she was trying to use a masculine kind of brain that she didn't have. Today, her legacy of being the first programmer is stil disputed.
People sometimes ask me what I did when I was hired at HAL. The answer is that I was a programmer. And an engineer. And a designer. And I marketed our games. I also ordered food. And I helped clean up. And, it was all great fun.
Low-level programming is good for the programmer's soul.
It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.
It would've been amazing [to work as programmer]. You're good at numbers, you're good with people, you like to wear shorts in the summertime.
The best way to prepare [to be a programmer] is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems.
This site uses cookies to ensure you get the best experience. More info...
Got it!