5 ms·
There is a reason why people make a distinction between "Programming" and "Software Engineering". Programming is just the act of writing code. All you have to d
by imtringued 7y ago
There is a reason why people make a distinction between "Programming" and "Software Engineering". Programming is just the act of writing code. All you have to do is learn a programming language and you are set.
"Software Engineering" encompasses everything else on top of programming. You need knowledge of these things: build systems (Make/Gradle), filesystems, networking (IP/TCP/HTTP), Data formats (JSON/XML), Databases(SQL/KV), software architecture, layout/styling, documentation (both reading and writing). This list is just scratching the surface but we can agree that all of these things are critical to build applications.
These topics clearly aren't exclusive to "Programming" and knowing them doesn't mean you are a "Programmer". You could also be a sysadmin that is managing a large cluster for multiple applications. But if you are a Software Engineer and not just a mere "Programmer" you know that your job is much much more difficult than merely the "Programmer" part.
- amelius 7y agoBut what to do if you have a CS degree with knowledge of all the things you mentioned and perhaps more, but people keep calling you "programmer"?
- duggan 7y agoAs long as I'm paid a software engineering salary to develop software, I could be called a clown for all the difference it makes. If you're programming, you're a programmer. Or a coder. Or a software developer. Or a software engineer. There is no consensus on the distinction between any of these things. Just lots of people with opinions because it's easy to have an opinion on.
- notabee 7y agoTitles are both a bikeshed and something that can have significant impact on salary, unfortunately. As long as non-technical recruiters are hiring based on buzzwords, it matters.
- varjag 7y agoA science degree is not an engineering degree, and one is not practicing science in their hot startup. So, fair enough.
- jaxx75 7y agoIs software engineering a real engineering discipline, though? I have a hard time saying yes when "software engineers" make mistakes that are well documented, no certification is necessary, and it isn't a legal definition.
- commandlinefan 7y ago> Is software engineering a real engineering discipline, though? Maybe it isn't yet, but I hope that there will come a day in my lifetime that it is.
- glouwbug 7y agohttps://en.wikipedia.org/wiki/List_of_data_breaches https://en.wikipedia.org/wiki/List_of_data_breaches With such a list, one would hope software engineering becomes a protected title
- Mirioron 7y agoBut will that really help though? It'll just be another mechanism for signaling, but that doesn't mean it will improve the situation, because the technology moves so fast that it's virtually impossible for the certification to be relevant, unless you mandate that software engineers get a certificate every year in some arbitrary newest technologies. Engineering is a field where we understand the fundamentals. Changes from year to year or even decade to decade aren't going to uproot half of the things you know about it. In software that can very much be the case.
- notabee 7y agoGoodhart's Law applies, so you can't have a set-and-forget certification process. It can be a dynamic process. And just perhaps, we should disincentivize trying to launch new technologies when the institutional knowledge is not there yet. I wonder how many of those security compromises come from bad tradeoffs trying to "keep up with the Joneses" instead of addressing technical debt and knowledge gaps?
- CaptArmchair 7y agoI think the label "software engineer" carries as much or as little meaning as "sailor" in a naval context. A "sailor" could be a captain, cook, look-out, marconist, machinist, steward,... anyone who's enlisted on a ship doing a set of tasks to keep things going. Is a technical writer a software engineer then? I would say so, yes. Why? Because they are involved in an intrinsic part of the entire process of building and maintaining a piece of software. The problem with "software engineer" as you frame them, is that you also raise the bar to an incredibly high to attain level as things stand today. Why? Because of how the field has kept on compounding ever more complexity over the past decades. It's extremely hard for mere mortals to memorize a a vast and ever changing corpus of knowledge and experience, be able to dive deeply in any codebase and understand all the parts while also have time left to write detailed, readable and understandable technical documentation. Case in point: Virtually everyone has a gazillion tabs open with an equal number of googled StackExchange posts. To keep up with the analogy: I don't think the radio-operator will act as a navigator; and neither does the navigator know the fine details of how the innards of a radio look like. Hence why you most software engineers are specialists in their trade. And often, specialists in a small fraction of the entire knowledge domain. Regardless, software engineers are without a shred of doubt programmers. Programming is exactly that: feeding a Von Neumann machine a list of instructions in order to "make it do" something. No more, no less. It doesn't matter what your role is in that process - defining the problem, working on an instruction set, typing the instruction set into the machine, documenting the instruction set, verifying the output,... - you're basically a programmer. The primary reason why we call ourselves "software engineers", really only is because Margret Hamilton - thé Margaret Hamilton of the Apollo AGC computer - came up with the label in order to legitimize the work she and her team did at NASA: https://en.wikipedia.org/wiki/History_of_software_engineering https://en.wikipedia.org/wiki/History_of_software_engineerin... In fact, the rise of complexity has caused a "software crisis "in the late '60s to '80s. And it was named as such: a "software crisis": https://en.wikipedia.org/wiki/Software_crisis https://en.wikipedia.org/wiki/Software_crisis All that is old becomes new again. The more I read about the history of our discipline, the more I'm convinced that we are just chasing our own tails over and over again. Arguing over who is a "programmer" and who is a "software engineer" is - ultimately - basically arguing over semantics and marketing. At the end of the day, the world doesn't care how the pie was made. They simply want to be able to fly safe, watch TV and file their taxes efficiently.
- dnautics 7y agoI wouldn't even call that a software engineer. That's a dev. A software engineer can promise an sla and understand what factors go into that sla and what constraints, when violated, lead to the sla being out of compliance. This is analogous to, for example, a civil engineer certifying a bridge for a certain load with a safety factor.