Good hours and bad hours

That is the way I think about coding and programming, generally. Good hours are hours where I know what I’m doing. Bad hours are more numerous, and generally feature lots of frustrating dead-end Googling to try and fix problems I’m having, meaning that I feel like I’m wasting my time to some extent.

We’re in the sharp end of the TechUP course, and I’m spending lots of bad hours trying to work out how to do things that I feel should be straightforward. This has mostly been caused by the laptop-hopping I’ve been doing over the last couple of weeks, as I’m having to keep reinstalling things and dealing with different computers’ idiosyncrasies. It doesn’t feel like time is on my side as a result.

Nevertheless, this current hour is a good hour, because all the problems I’ve been having with my work today have been solved. It’s nice to finish the day with no outstanding issues! It’s also an important part of the learning process, frustrating as it can be sometimes.

Leave a Reply

Your email address will not be published. Required fields are marked *