Let’s get one thing straight: knowing how to code doesn’t make you a software engineer. It’s a harsh truth, but one that’s become painfully clear o...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
At one point, I wasn't sure if I was a programmer or a software engineer. I had only a vague notion of what it meant to be a software engineer.
Then I read Software Engineering at Google. Which is an excellent book — and available to read online, for free.
Now say with confidence: I am a software engineer.
That book is definitely a great recommendation. Thank you for sharing it in the comments.
Wow! Thanks for this recomendation!
Holy smokes, free? What a gem! Thank you so much for sharing, this is a gamer changer.
Might even buy the hardcopy to feel more like a software engineer :D.
All very true.
Number 3, is vital for me, I won't let anyone in my team get away with not understanding the actual business problem we are solving. I would add, the economic impact of it too, both on costs at my business and in the customer.
This article reminds me of when I was a junior software engineer, and I told my manager that the company pays me to write code. She corrected me and said the company pays me to provide solutions. That always stuck with me.
Thanks, great key points in the article!
I aim to become more of an engineer, but feel I’m pretty stuck at the programmer step;
I love to code, and really enjoy learning.
But somehow I always feel kind of one step behind every time my seniors are discussing how to move forward in a current project.
If the seniors in your team make you feel that way, they're probably afraid of their own position and you may be better than you think. A good senior empowers you. A bad senior belittles you, because they're afraid you'll replace them.
Be a software architect like me. Know how to name functions. Use the right Comments, set up the structure of the program. Do all these things right is already hard enough. A lot of software engineers don't know enough about abstraction, etc.
Thank you for this insightful article on the difference between programming and software engineering. Your points about the importance of system design and problem-solving skills resonate strongly with me. I'm committed to upskilling myself beyond just writing code, focusing on areas like software design principles, system architecture, business acumen, and collaboration skills. Your advice aligns perfectly with my goals of transitioning from a programmer to a full-fledged software engineer.
Thanks for the great article! Reading through it has definitely made me to reevaluate my self whether I'm an engineer or just a programmer. There are points mentioned I never thought that it should be taken when doing a software engineering work.
Insightful thank you
Wow, I didnot know the difference. Thank you so much. 🔥
I am a computer scientist
Good article!
Thanks to your post, I can now say with confidence: I am a software engineer. I am also in college, so that must also add something lol.
Thank you , informative
Awesome, thanks for sharing.
The distinction between being a programmer and a software engineer lies in approach and scope. While programmers focus on writing code, software engineers tackle the bigger picture—designing systems, ensuring scalability, and solving real-world problems effectively. Building this mindset can elevate your career and expand your opportunities. For those managing complex logs and data during software development, tools like FluentBit can streamline log processing and enhance efficiency.