3 ms·
If you ask me both titles are outdated. If you google around you get pages like this: https://www.electronicproducts.com/Education/Career/Software_engineer_vs
by dangus 6y ago
If you ask me both titles are outdated.
If you google around you get pages like this:
https://www.electronicproducts.com/Education/Career/Software_engineer_vs_computer_programmer_what_s_the_difference.aspx https://www.electronicproducts.com/Education/Career/Software...
> Computer programmers receive specifications from software engineers and turn the program design into written instruction codes that the computers will follow.
In 2020, this is a load of baloney.
It sounds like it was like a term to distinguish senior and junior developers.
A modern developer is concerned with the whole process start to finish, and owns the maintenance and design of the software. A senior developer will know more about how to architect a complex application but otherwise the role is the same.
I wouldn’t worry about it. I’ve worked at companies that have called me a DevOps Engineer, SRE, Linux Systems Engineer, and these were all identical roles. Titles are just about ignorable, it’s more important to look at what skills are needed, what the day to day job looks like, and of course, compensation.
- keaq 6y agoThank you for your response. From my perspective a programmer is just able to write code, i.e. turn the business requirements into instructions. A software engineer is rather able to design/architect a system, let it be a single web page or a container cluster. Then the question is how people learn "how to architect a complex application"?
- dangus 6y agoIt’s hard for me to explain why I don’t like that distinction. Once you can write code you can architect a system. There’s nothing stopping you. The information is out there. Perhaps the real question is whether your company trusts you enough to make something from scratch. Or whether your solution is good enough to handle large amounts of customers, traffic, or usage. People learn to do so with a combination of experience and just general learning (documentation, tutorials, references, talks, conferences, etc) over time. I think a modern company would simply call both roles “software developer” and apply different levels of seniority (e.g. junior, senior, staff, or they could use numerical levels).