3 ms·
About 20 years ago I was a newly minted CS grad and a new software engineer. I told someone a lot older than me what I do and she said "Oh, that's a great start
by jacobsenscott 6y ago
About 20 years ago I was a newly minted CS grad and a new software engineer. I told someone a lot older than me what I do and she said "Oh, that's a great start!". Which threw me because I wasn't sure what I was supposed to do next. That's what I wanted to do. Today I am a "programmer", because I realized software isn't really engineering. That's still what I want to be doing today, and I still don't know what she thinks I'm supposed to do next.
- DaiPlusPlus 6y ago> because I realized software isn't really engineering Competently writing software will involve applying engineering principles and a project management methodology: things like TDD, design-patterns, your system's architecture - they're all part of software-engineering. Writing software is "programming" in the same way that writing a bestseller novel is "typing" or doing mathematics is putting fancy symbols on paper.
- folkhack 6y agoCouldn't agree more... and to add my own thoughts, why the heck are we so hellbent on dropping the engineering part from software engineering? I get that it is a discipline that allows one to self-learn up the ladder to the title but why the hate? I do just as much highly-complex/critical work as my other engineering friends, so why is what I do not engineering all of a sudden?
- wtracy 6y agoSeveral people who dislike the term "software engineer" have started using "software craftsman" instead.
- DaiPlusPlus 6y agoI am aware of a few people in my social-circle who put "Software artisan" or "Purveyor of artisanal technology experiences" (etc) on their LinkedIn profile - so I believe you.
- Aeolun 6y agoDeal with enough incompetent management, and you might really want to become one to save others from the same.