On: Software eats software development

[chaz]

In these situations, I believe there are two types people:

A: "Wow, things are really messed up. I'm out of here." B: "Wow, things are really messed up. There's opportunity everywhere."

Either can be right, depending on the person and situation.

[beat → chaz]

I'm a B, for sure. I'm trying to create new tools to deal with the "things are really messed up" problem... in part because I can create a working business and get myself out of the enterprise, and in part because I genuinely want to make this industry better. What I like about what I'm building is that it changes the human/computer ratio in debugging and problem-solving for complex systems.

Have computers do what computers do well, so people can do what people do well. That's the core of my approach to building software. A big part of the reason enterprise development sucks is because debugging is so manual. Automate parts vulnerable to automation, and engineers won't just be more efficient - they'll be happier.

[nikatwork → chaz]

At a megacorp, as a developer, you have as much chance of changing the culture as you have of stopping a hurricane with a fart.

[derefr → chaz]

There are two Bs, though: one sees opportunity to sell change. The other sees opportunity to perform arbitrage against the inefficiencies.

[pcurve → chaz]

Actually A and B are same person. Just two different phases.

[nigelsampson → chaz]

That age old saying, "Change you job, or change your job."

[CmonDev → chaz]

Opportunity to fix other people's mess at the expense of your health (since you are not likely to get dedicated time for refactoring) and have a "thank you", while CEO gets an oversized bonus?

[dominotw → chaz]

ok coach.