I now remember one of the reasons why most people probably wouldn't like programming.  There are many periods of time where you have nothing really visible to show as progress.  This can be really bad when you have a boss that doesn't understand how programming works. 

When I started the Mac port, I made (well XCode really made it) a little app that just created a small window that did nothing except you could move it around, resize it, and close it.  I then spent the next couple weeks adding in Depths of Peril code and all I saw was lots of errors and warnings from the compiler and then lots of startup crashes mostly because none of the mac specific code was programmed yet. 

But finally I fixed all of the errors, warnings, and crashes and I now had a small window that you could move around, resize, and close. :)  So from a visible standpoint after 2 weeks I was exactly back where I started.  Now in reality I had made a ton of progress, there just wasn't any visible feedback to back that up.  This is probably even frustrating for many programmers, but you pretty much have to get used to it.

Of course, the opposite thing happened once I got through those 2 weeks.  It seemed like every couple hours I had another system on the Mac running: mouse, keyboard, graphics, sound, etc.  This part is always the fun part, but you can't get there if you can't get through that first hard part.

Comments