close

Discovered in

A-Za-z0-9

A-Za-z0-9
1,659 Favs

Find other sites about

Related Sites

  • 6 reviews
  • Reviews of the site
  • Join StumbleUpon or login to add a review! default avatar

  • Rated by SickM on Oct 08, 9:38am

    Because the client doest stop whining that it is taking so long.

  • Reviewed by Windexglow on Aug 05, 8:57pm

    "[5] Procrastination: each time you do [1],[2], [3] (and possibly each of the others) you get side-tracked on the web reading the news or finding out how to do some unrelated feature." Oh uh haha, not doing that one myself here. Nope..

  • Rated by stephenhazel on Jan 24 2009, 9:08am

    Not really sure who David Glance is or what kind of programming he does. For me, it's the problem domain - I just don't have full specs for a full fledged midi sequencer. It takes a LONG time to figure out what the program should DO. Not to mention a lot of experimentation to try out different things. Not to mention debugging. I find most programmers are "surprised" because they haven't fully spec'd a system nor have they figured in the debugging and unit test time. But =I'd= say programming takes a long time because of what you're trying to program - the problem domain. It's usually just not known well enough. It takes time to figure it out, experiment, debug and test. Get used to it - programming is hard - it's supposed to take a long time :) You don't want to rely on a program that's built too fast. It's just not ready yet.

  • Rated by Nataki on Jan 20 2009, 8:03am

    This sounds more like 10 excuses for laziness then legitimate reasons for why programming takes so long.

  • Rated by Josso on Jan 17 2009, 10:35am

    ... but he's missing to tell us how to avoid (some) of those things. :p

  • Rated by Titannick on Jan 16 2009, 8:50am

    But he forgets to state the most important reason of all:Programming is a difficult task in which you need to keep in memory how your current system works, will work, should work etc. It's just not an easy thing to do in the first place.