Writing computer software sometimes goes a little something like this:
- Brainstorm
- Believe that writing software is easy
- Design
- Change the design
- Bang your head against the wall
- Wish you hadn't banged your head against the wall... ouch...
- Change the design... again...
- Write some senseless code
- Wake up the next morning and delete the senseless code
- Write gibberish on a whiteboard
- Erase the whiteboard
- Realize that your gibberish was actually somewhat important
- Finally get a design together
- Write some senseless code
- COMPLETELY SCRAP THE DESIGN AND THE CRAPPY CODE!
- Draft a decent design
- Write bad code
- Realize the code sucks
- Fall asleep on your keyboard
- Wake up at 3 AM and realize you did nothing except type 2000 pages of the letter L.
- Bang your head against your pillow... ahh... better than the wall. Commence sleeping.
- Hide underground and crank out some code
- Attempt to compile code
- Add include statements and the semicolons you forgot. Attempt to compile code... round 2
- Begin talking to the compiler. Say things like, "Oh, quit complaining!", "Shut up!". Try compiling again.
- Ask the compiler questions like, "What the hell is wrong?", "Why have you forsaken me?"
- Repeat steps 25 and 26 for many hours
- Run the program
- Experience a segmentation fault or some unexpected error
- Write about your experience on your blog
- Find a dark corner and cry
Comments