What Should the Software Industry be Known For?
I was talking with my friend Marc today. He’s a mechanical engineer (and a damn good one) and we were talking about work. He said something that kind of surprised me:
“Sometimes I wish mechanical engineering companies were more like software companies.”
All through school, and even in the workplace, I’ve heard software engineering compared to traditional engineering.
“You don’t build half a bridge, then change your mind about how it’s going to look.”
“It’s a green-field project.”
“Well, the way they estimate construction projects is like this…”
I’ve always thought other engineering disciplines had all these lessons we could learn in software, given that building software wasn’t recognized as engineering until about 1960*. It’s never once occurred to me that what we do in software could help the guys building cars, or skyscrapers, or in Marc’s case, bomb suits.
This begs the question:
What do we want other industries to say about software engineering?
If you could teach one lesson you’ve learned in software to another discipline, what would it be? What would be the top, absolutely most-important anecdote you could recite? Or inscribe on a statue of a programming icon?
Marc said it was how people are managed. The offices, the lax environment, the 20% time.
I think it’s how we integrate teams. I love working closely with designers, and I bet other engineering fields could really benefit from the software designer/developer relationship, and how it has evolved over the past decade.
What should the software industry be known for?