3 ms·
I consider software development an engineering discipline. In my weird, crazy world, engineering is all about discipline (sound of a riding crop slapping a lea
by ChrisMarshallNY 5y ago
I consider software development an engineering discipline.
In my weird, crazy world, engineering is all about discipline (sound of a riding crop slapping a leather-clad thigh), and follow-through. It's a lot less about slide rules and differential equations.
I believe that the Romans that built aqueducts (often using coerced labor -otherwise known as "slaves") were engineers. They had a lousy numbering system, no concept of trig (although a few had heard of Pythagorus), and not even a slide rule; yet they were able to build massive, well-designed structures that still stand, to this day, nearly three millenia later.
I can't use some Web sites that are just over a year old, because their components went belly-up.
But I also consider software development to be a craft. That's really my approach.
When I write software, I make a personal level of investment into the outcome. The project must complete. Even when I'm working with a test harness, on a project that is nothing more than an experimental platform, I treat it as if it were a shipping product, that I plan to display in the store window. In fact, I often revisit truncated experimental efforts, in order to scrounge snippets. Since they are already "ship" quality, those snippets tend to be quite useful.
A basic habit of mine, is that all of my code "ships," even when it doesn't. That's a craftsman attitude. Getting the project to "ship" state is an engineering effort.
But that's just me. YMMV.
- deregulateMed 5y agoYou can't be both a craft and engineering. I think the issue is misunderstanding what it means for something to be engineered. There is a correct answer. (Especially because you can always optimize for cost or a different quality metric)
- ChrisMarshallNY 5y agoI see things differently. I believe that they can both coexist. I think that the prior art is centuries old.
- jbluepolarbear 5y agoYou are so wrong. Software is both a craft and engineering. All software fits your definition of cost and quality optimization. It is a craft in that a software engineer isn’t taught how to write the software you want, they’ve built a toolbox from crafting different types of solutions because their existing tools didn’t fit.
- deregulateMed 5y agoThe optimization is complete in engineering. In programming optimization is optional and unless you are doing safety critical C or assembly, it's not truly optimized.
- jbluepolarbear 5y agoWat?
- hwayne 5y agoMany mechanical and electrical engineers see their work as craft.
- deregulateMed 5y agoLots of engineers suck, and they often don't actually do engineering.
- ChrisMarshallNY 5y agoI started as an EE (actually, as an electronic technician). I never came up through the "traditional" CS tree. As a result, I regularly see the insides of many snotty noses. It was the main reason that I stopped looking for work in the field; but I was shipping stuff from my very first project[0]. My entire career has consisted of architecting and implementing shipping solutions. Meh. Whatever creams your Twinkie. I'm not losing much sleep over it, but it is annoying. [0] https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf (Downloads a PDF)