Category: Coding Philosophy

I was recently interviewed by Chris of the DQMH podcast about what we are doing here at SAS Workshops, and more importantly why.

Being a successful software engineer requires balancing both the theoretical and practical side of writing software.

As engineers we pride ourselves on problem solving. That’s what we do. However I find the use of the word problem to be somewhat problematic (pun intended).

Part of being a successful developer is not only mastering your particular skills but having some knowledge of the surrounding pieces.

We often get caught up in labeling things as right or wrong. Instead we should be asking ourselves, is this working? is it producing the results we desire?

We talk a lot about scalability. We all know it is something we should strive for in our code, but what exactly does scalability mean?

It is often easier to ignore problems than address them directly. We create the illusion that things are fine. The end of that illusion isn’t pretty.

Where do you find yourself getting distracted? What are you really avoiding?