Skip to main content

Headaches

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

Comments

Post a Comment

Popular posts from this blog

Wedding Prediction - October, 2013

Carla and I are planning on getting married sometime in October next year.  We need to pick a date, and that decision may  involve some science and mathematics.  :) For example, we want the weather to be nice.  To be more precise, we'd like the high temperature for the wedding day to be between 60 and 80 degrees Fahrenheit.  Obviously, we have both lived in Ohio our entire lives, and we have a pretty good idea of what the weather will be like.  We both hypothesised that October was a "hit or miss" sort of month; it could be cold, or it could be nice. But, for me, a simple hypothesis was not enough; I really wanted to know the probabilities of decent weather based on historical weather data.  Many websites on the Internet (i.e. almanac.com) charge you to review historical weather data, but Carla and I discovered a cool page on cleveland.com that provided exactly what we wanted.  I loaded the historical temperature data from 1903 to 2011 f...
2 comments
Read more

Web Browsers You Should Support

As a web developer, generally speaking, you should consider supporting the following browsers (at the time of this writing): Chrome (latest) - the browser that sets the bar for the others; you should be using it and supporting it Internet Explorer 9+ - the browser that finally caught up with the times a bit; basically, a Chrome wannabe.  I still say that IE sucks... even if it really doesn't anymore.  Yes... I'm sour about IE8 and below. Internet Explorer 8 - the old, sad browser that we sadly still have to support for a while.  CSS 3 is not well-supported here, so we use projects like CSS3 PIE or whatever.  By the way... IE8 sucks.  I can't wait until this comes off of the list. Firefox (latest) - the browser that was once awesome and has sadly suffered recently because it's slower than Chrome... but hey, lots of people still use it. Safari (latest) - Watch out for Safari as more iPhones, iPads, Macs, and more overly-priced Apple products flood the ...
Post a Comment
Read more

Computer Clocks Cause More Issues

Two nights ago, a leap second was added to system clocks running Linux, causing much-undesired havoc. On July 1st at 12:00 AM UTC, both of my Amazon EC2 instances fired an alarm indicating high CPU usage. I investigated to find that it was MySQL that was eating all of the CPU. I logged in and ran SHOW PROCESSLIST to find that no queries were running (these servers don't get hit much after business hours). I stopped MySQL, CPU utilization dropped back down to 1-3% (as normal). I restarted MySQL, and it started eating a lot of CPU again. Then, I restarted the server (shutdown -r now), and the problem went away. Both servers had the exact same problem (running Ubuntu 12.04 LTS). In my particular case, MySQL began eating CPU, even after being restarted.  It was a livelock. The only relevant item I saw in the syslog was: Jun 30 23:59:59 hostname kernel: [14152976.187987] Clock: inserting leap second 23:59:60 UTC Oh yeah... leap seconds.  Those are super impor...
Post a Comment
Read more