This is another post my work asked me to opine on. I’m a big fan of developers that aren’t focused totally on making software – folks who make their own tools to solve their problems. However, it’s definitely possible to get yourself into a real pickle where you can build yourself into a corner you don’t have the time and skills to get yourself out of.
Pitfalls of the Ops Developer is about how to recognize when your group wants to transition from home-grown solutions to something more standard. It’s HARD to know and it’s hard to anticipate when you are about to hit one of those inflection points. As always, there’s a ton left out, but I love hearing from folks about their stories around the topic. I was just talking to a client in London and they brought this one up as being helpful and describing exactly the place where they are right now. Soooo… I thought I’d share it with you!
But wait, there's more
This work by MattK is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
One thought on “Pitfalls of the Ops Developer”