3 ms·
"Real engineering" does not mean building things. Real engineering means knowing how to model processes - so that when you actually do build something, your mod
by TheOtherHobbes 10y ago
"Real engineering" does not mean building things. Real engineering means knowing how to model processes - so that when you actually do build something, your model gives you a strong signal ahead of time that it's going to do what you want.
Engineering is not libraries or cook books: engineering is math.
Civil engineers model buildings and other structures. Electronic engineers model circuit behaviours. Aerospace engineers model aerodynamics and materials. Traffic engineers model traffic flows.
Stuff only gets built after a model appears to work. This is a good thing, because otherwise we'd be build bridges with rule of thumb and trial and error, and they'd fall down a lot, and kill people.
Knowing the math makes it as easier to model a business case, complete with deadlines, as a process.
Why isn't software engineering like this? It's not impossible to model software. It's just conceptually demanding, and very expensive.
Professional software engineering doesn't look much like vanilla coding. The percentage of developers who can hack it - or could ever hack it - is not large.
So we muddle along as a trade, not an engineering profession, hammering and gluing libraries together.
The pay is still good, hardly anyone gets asked if they know what the ACM is in job interviews, and a lot of customers don't mind that much if a site only works in Safari and not in Chrome. (NB: actual experience I had with my online banking account last week.)
It's true that being asked to estimate how long something will take may be met with a sharp intake of breath. But the reality is that very similar projects have usually been completed many times in other companies already, and the amount of truly unique and original R&D needed for most work need is miniscule.