3 ms·
I think we agree in some regards, although I think we see differently the crux of the problem. Someone (forget who) once made the comment about hating being a
by kenjackson 16y ago
I think we agree in some regards, although I think we see differently the crux of the problem.
Someone (forget who) once made the comment about hating being a developer at MTV because MTV wasn't a software company, so devs were always second class citizens. I think this is the case in the enterprise often.
The job of the enterprise generally isn't to make software. Software is there to support the business. Unfortunately, many developers don't act as if this is the case, and often seem to act as if the businesses end goal is to get this particular application working.
I'd propose that the best thing enterprise developers can do to help their prospects of being a "second 90% dev" their whole career is to show they understand the business and how they can bring value to it.
I knew an architect at Walmart who talked about how their philosophy changed and really focused on showing how Walmart IT need not be a cost center, but rather can be an actual profit/loss. This apparently drove more innovation, more interesting work, but also brought a lot more accountability.
I think that's the right model. Not just "Devs, go pick your favorite toys and run amok", but to have the devs say, "we're a tangible part of the business and we can account for our spend in the bottom-line". With that, I think good things come with it.