TG#17.5: Programmers vs Hardware

December 29, 2008 – 6:15 am

On this short, we discuss an article from CodingHorror and weigh the merits of throwing programmers or hardware at tough problems.

TrackBack URI for this entry is
  1. 3 Responses to “TG#17.5: Programmers vs Hardware”

  2. Great show.

    There are a couple other obvious exceptions to the suggestion.

    #1 It is possible to build an application that performs well initially but then grows out of performance bounds … a table scan in a query may be appropriate early in a database’s life, but less so when it fills up. These sorts of things require regular administrative action. Circumstances could arise that no amount of additional hardware can fix.

    #2 The issue should always be a question of economics. If you’re running a high volume site on many servers, two weeks of a programmer’s time may be pittance compared to adding another 100 servers.

    By tuebit on Dec 29, 2008

  3. I like the Gravatar Tuebit! Ahh the good ol days….

    Anyway, good podcast. We face this situation all the time. I work for a small firm and we have a co-located hosting environment, and we are constantly doing both, adding hardware and making code changes to improve performance.

    What we have found is that at some point, no matter how much $ you spend on hardware some code is so bad that no amount of hardware will help. Not that I wrote any of that code myself 😉

    By ShadesOfGrey on Jan 6, 2009

  1. 1 Trackback(s)

  2. Dec 29, 2008: » Tweak and Geek Podcast #17.5

Post a Comment