3 ms·
I'd prefer the software on the plane I'm flying on to be engineered. Arts and crafts are fine for your new facebook app, but please engineer the stuff that keep
by noonespecial 17y ago
I'd prefer the software on the plane I'm flying on to be engineered. Arts and crafts are fine for your new facebook app, but please engineer the stuff that keeps me alive.
- bcl 17y agoExactly. I think Jeff is forgetting, or ignoring, that there are different realms of software development. I think too often he generalizes the 'web app' experience to cover the whole industry. I know that in my work as an embedded developer that the fast iteration and feedback loop doesn't work too well with physical products with no easy upgrade system. That being said, I do think he has a good point with desktop and webapps where you can quickly get and act on feedback from the customers.
- rubinelli 17y agoFrom the article: "What DeMarco seems to be saying -- and, at least, what I am definitely saying -- is that control is ultimately illusory on software development projects. If you want to move your project forward, the only reliable way to do that is to cultivate a deep sense of software craftsmanship and professionalism around it." He isn't talking about fast iterations. He is talking about feeling responsibility about what you are delivering, instead of using procedures as a crutch. I know I would rather fly in a plane that had its sowftware written by developers that cared about their work than by "engineers" that don't think about their work because they expect the code review and a couple of QA cycles to catch all the bugs.
- bcl 17y agoGood point. There needs to be a balance of both, I just think Jeff leans too far toward the 'soft' side of things sometimes.
- a-priori 17y agoOh, rest assured it is. Software engineering is alive and well in fields that demand up-front reliability -- avionics, medical equipment, reactor control systems, and so on. In university, I did a co-op job with a civil avionics shop where I learned all about DO-178B, the standard by which avionics software is certified. DO-178B Level A-certified is top-quality and highly reliable. I feel safe flying on planes after working in that industry. It's a rigourous process, and software that emerges from it basically never fails. But it's an expensive and slow process to develop software this way, and it's prone to failure from any number of reasons. Requirements and technology change, and must be known up-front. Capital can run dry. It's only worthwhile developing software this way when absolutely necessary, when half-working software is dangerous and could kill someone.
- derefr 17y agoI agree completely; however, this is where Engineering should start and stop. If the heartbeat of the software isn't tied inextricably to the heartbeat of real people, don't call the people that work on it Engineers, and don't expect them to do any Engineering. On the other hand, start giving the people that write the plane firmware those neat iron rings[1]. [1] http://en.wikipedia.org/wiki/Iron_Ring http://en.wikipedia.org/wiki/Iron_Ring (It's a Canadian thing.)
- noonespecial 17y ago[1] http://en.wikipedia.org/wiki/Iron_Ring http://en.wikipedia.org/wiki/Iron_Ring (It's a Canadian thing.) That's one of the coolest things I've heard in quite some time. Perhaps software engineers in the US should wear some visible reminder of "Microsoft Bob"?
- assemble 17y agoWe call it the Engineer's Ring in the US ;) http://en.wikipedia.org/wiki/Engineer%27s_Ring http://en.wikipedia.org/wiki/Engineer%27s_Ring http://en.wikipedia.org/wiki/Order_of_the_Engineer http://en.wikipedia.org/wiki/Order_of_the_Engineer