A Quote by Bob Frankston
Early Apple machines - don't know how to answer what it was like since there were so few tools. Just had to keep debugging by isolating a problem, looking at memory in the limited debugging (weaker than the DOS DEBUG and no symbols) patch and retry and then re-program, download and try again. And again.
Related Quotes
The process of debugging, going an correcting the program and then looking at the behavior, and then correcting it again, and finally iteratively getting it to a working program, is in fact, very close to learning about learning.
I do as much debugging as possible on the Mac, but I occasionally must debug problems in the PC world, which is significantly slower.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
One of the headaches of high-tech test programmes is having to debug the test arrangements before you can start debugging the things you're trying to test.
The stressful thing about being an actor is, like, you have to kind of audition again and again and again, you know? You go in one time, and you go in again for a director and then again for producers and then again and again and again.
I had the misfortune of getting what skateboarders call hippers. It's when you fall on your hip again and again and again, just the same spot. It turns into like a blue purple bruise and it's just torture because I had to keep on doing the same move, going around in the pool again.
Since I was a small child, I'd believed we were inherently perfect, and that we had to keep coming back again and again until we recognized our innate perfection.
But is it such a bad thing to live like this for just a little while? Just for a few months of one's life, is it so awful to travel through time with no greater ambition than to find the next lovely meal? Or to learn how to speak a language for no higher purpose than that it pleases your ear to hear it? Or to nap in a garden, in a patch of sunlight, in the middle of the day, right next to your favourite fountain? And then to do it again the next day?
The hardest part of the software task is arriving at a complete and consistent specification, and much of the essence of building a program is in fact the debugging of the specification.
I keep bumping into that silly quotation attributed to me that says 640K of memory is enough. There's never a citation; the quotation just floats like a rumor, repeated again and again.
When you stop for months and you come back, you try everything, and I worked so hard to get back but then you do it again and again and again. You disappoint yourself and other people at the club, the manager, everybody. You don't know how to get it right.
Since then, I have just read and read - but, that said, I suppose there is a raft of writers to whom I return again and again, not so much because I want to write like them, even if I were capable of it, but simply for a sort of stylistic shot in the arm.
Back when the Bible was written, then edited, then rewritten, then rewritten, then re-edited, then translated from dead languages, then re-translated, then edited, then rewritten, then given to kings for them to take their favorite parts, then rewritten, then re-rewritten, then translated again, then given to the pope for him to approve, then rewritten, then edited again, the re-re-re-re-rewritten again...all based on stories that were told orally 30 to 90 years AFTER they happened.. to people who didnt know how to write... so...
If I fail, I try again, and again, and again. If YOU fail, are you going to try again? The human spirit can handle much worse than we realize. It matters HOW you are going to FINISH. Are you going to finish strong?
I've never written anything that I haven't wanted to write again. I want to, and still am, writing 'A Few Good Men' again. I didn't know what I was doing then, and I'm still trying to get it right. I would write 'The Social Network' again if they would let me, I'd write 'Moneyball' again. I would write 'The West Wing' again.
Rushing to optimize before the bottlenecks are known may be the only error to have ruined more designs than feature creep. From tortured code to incomprehensible data layouts, the results of obsessing about speed or memory or disk usage at the expense of transparency and simplicity are everywhere. They spawn innumerable bugs and cost millions of man-hours - often, just to get marginal gains in the use of some resource much less expensive than debugging time
Related Authors
Alistair Cockburn Quotes
American
Software developer
Brad Templeton Quotes
Canadian
Software developer
Dan Bricklin Quotes
American
Software developer
Jeff Atwood Quotes
American
Software developer
Mark Russinovich Quotes
American
Software developer
Ray Ozzie Quotes
American
Software developer
Richard Garriott Quotes
American
Software developer
Steve Yegge Quotes
American
Software developer
Tom Preston-Werner Quotes
American
Software developer
