Don’t Get Caught Up in a Code Framework Paradigm

I was originally going to name this article “How It Took Me 8 Hours to Write 2 Minutes of Code”, but somehow I didn’t think that most software engineers would find that terribly compelling, and if there is one thing engineers like to do, it’s to determine what’s most efficient and functional. Since you’re reading this, I guess this was the better idea.

It’s easy to underestimate what it means to be a software engineer. When most people think of a engineering position, they view a stereotypical computer nerd, with half a dozen bottles of Mountain Dew lying empty on their desk, Star Wars figures littered throughout their cube, and quotes from The Princess Bride printed out and taped onto their cube walls. Well, okay I can own that. Sort of.

What software engineers really are however are problem solvers. Every day we show up at our keyboards to bravely stare the unknown right in the face, and solve our client’s problems, even the ones that don’t exist quite yet, with creative and efficient solutions. I wish that “bravery” was a skill more people associated with the job.

What software engineers really are however are problem solvers.

If you are anything like me, it helps to have a sword and shield close at hand when daring greatly, and for me…