[gregbarbosa]

Reading the article, and seeing where the author is coming from, and I honestly don't see it in the way that he describes.

An engineer (one in the classic sense), and a software engineer (someone who engineers code and bits to create software) can both be explained as "I find solutions to otherwise complicated issues others cannot while encompassing outside and unforeseen circumstances". Now, that phrase there can be applied to a thousand other careers and jobs.

But I think we use the term software engineer because we haven't quite come up with a "perfect" term to describe what is being done when code is being written.

Writing software is not easy for all people. Just like writing a paper is not. Understanding logic, flows, and cross-compatibility takes experience, time and understanding.

That said, I don't think the term software engineer is completely incorrect, but I also don't believe it is the best one to use either. I see it as we will either find a better term for what we mean when we say 'software engineer', or just end up using that generic term because it is understandable enough to describe an umbrella definition.