News for hackers. Stuff that matters.
Re:Productive Programming by astine on Tuesday August 31, 2010 @01:04PM (#1650054)
"2. Simple Algorithms. Yes! I love this example:

  * EnterOrders 08/31/10 edw519
  *
  return();
I now have a working programming - Woo hoo! You say you want more features? No problem. Let's start enhancing it."

There is nothing like simply getting a "Hello World" up and running as a simple sanity check and starting point.

Re:Productive Programming by cabacon on Tuesday August 31, 2010 @01:13PM (#1650082)
I like the game programming story about the black triangle to illustrate this point: http://rampantgames.com/blog/2004/10/black-triangle.html
Re:Productive Programming by techbio on Tuesday August 31, 2010 @04:02PM (#1650694)
This are called Tracer Bullets in the book "The Pragmatic Programmer" by Andrew Hunt and Dave Thomas. They advocate:

Users get to see something early on.

Developers build a structure to work in.

You have an integration platform.

You have something to demonstrate.

You have a better feel for progress.

As a solo founder I need working code, that I can put out of mind, while I produce more.

Re:Productive Programming by prodigal_erik on Tuesday August 31, 2010 @04:13PM (#1650735)
I've always heard "tracer bullet" as a request to a production system that selectively gets much more detailed logging or diagnostic output than usual.
Re:Productive Programming by aaronbrethorst on Tuesday August 31, 2010 @07:26PM (#1651228)
Which is to say you haven't read The Pragmatic Programmer? I highly, highly recommend it. I bought my first copy about 8 years ago, and pull it off the shelf once a year or so to freshen up. I always learn something new every time I do.
Re:Productive Programming by tjpick on Tuesday August 31, 2010 @04:25PM (#1650771)
I know this as top-down programming.