Tuesday, November 1, 2011

"Don’t Call Yourself A Programmer, And Other Career Advice" by Patrick McKenzie

What do you think of this blog post?

Don’t Call Yourself A Programmer, And Other Career Advice by Patrick McKenzie

A small snippet: "If there was one course I could add to every engineering education, it wouldn’t involve compilers or gates or time complexity.  It would be Realities Of Your Industry 101, because we don’t teach them and this results in lots of unnecessary pain and suffering."

Do you agree with Patrick's opinion?


  1. I completely agree with the author. In the end of the day we use software to solve real life problems, we use software to add value for the business. But how we can create software without understanding the business ? In order to understand the business we need tools, these tools or knowledge Is acking or weak. I think this kind of knowledge should be given in the form of unversity course with the degree which is widely used to solve real life problems and not for research.
    In fact, the majority (incuding me) didnt really always understand the business. We end up implementing a soution which we dont understand what it aims to solve, it is needless to say how negatively this affects the soution. By the way - this is where "great developrs" Wont nesseraily be helpfull

  2. Of course understanding the business behind a certain requirement helps in developing a better solution. I get your point of referring to your opinion on the "Finding Great Developers" by Joel Spolsky here.