Category Archives: deepthoughts

discipline and stumbling blocks

Ok so it’s been about a month since starting to blog and when I started my goal was to try and 2 a week of some technical nature. Kind of a way for dumping my technical thoughts of the week into my normal nerdy perkiness.

So my difficulties tonight as I sit at the end of week are really not about technical subjects that I have been pondering this week but rather complete thoughts. Over the last few weeks I have been playing with some iOS development, javascript (AngularJS, Backbone, Ember) as well as my current interest in NodeBots.

Subjects aren’t the lack but the lack this week comes in completion. I can blame the holiday weekend but in all reality I am just in the middle of mental stumbling block. This can be a good thing because I have learned over the years that with personal discipline what usually follows is several weeks worth of great productivity.

Which is really why I am sitting down to write this all out. It’s that personal discipline that so long as I hack through these down periods that I achieve some of my best work.

So tonights blog is not filled with great thought or technical inspiration but what it is filled with is me “hacking” away through the downtime knowing that something promising is about to occur.

Happy Coding.

Sometimes sanity isn’t the best route

I saw the following post on twitter earlier this week:


I have to admit that my first response was of course all the time. Then afterwards it got me thinking about those times that I broke this rule.

Don’t look at me or tell me that you have never patched bad code.

We all have worked somewhere where there was this one class, function or piece of code that we dreaded working on and when we did it was precision strike. You know the drill:

Get in, get out and leave no trace behind that says you were there.

I worked this one job where a large part of what our software did was track the status that certain types of documents could be in. There was myself and a few other programmers that were aware of the process and rules for how these documents changed status and we always hated when customers or program managers wanted to “tweak” those rules.

We often talked about rewriting all that code and in some projects we actually attempted to schedule time for its work. In reality though it was the largest plate of spaghetti most of us had ever seen and each time we opted against it. Usually our excuse for not doing was always the same:

“If it ain’t broke, don’t fix it.”

If you google that phrase you will find hits all over the place about. So which famous engineer do we choose to associate this saying to? Amazingly this quote belongs to a business man by the name of Bert Lance who at the time was working for President Carter.

Please don’t take this to mean that I am supporting this type of thinking all the time. The whole idea of taking things that are “working” and changing them is a business model (disruptive technology) for so many of todays majorly successful companies.

Maybe for fun though I will tweet the following:

One of the quickest ways to break something is to fix it when it ain’t broken.

Later everyone and as usual happy coding!!!   =)