|
|
|
|
|
by dvtrn
2743 days ago
|
|
That's ok, components should be replaceable without having to reinvent the whole thing. A fine, admirable and accurate (IMO) mindset. Things get weird when recruiters find out about these new tools and suddenly we're having that time honored discussion about how 'tech hiring is broken' because the people screening resumes don't realize OpsMop hasn't been out for 4 years and no one has 4 years experience with OpsMop. Everyone scrambles to learn OpsMops-so they can get a job where OpsMop ends up being abandoned and the DevOps team goes back to ansible, other teams start adding it to their tool chains because someone got hired who fiddled with it once and becomes an OpsMop house, a few engineers get very good at it, realize they can probably write a better version, three years later someone's posted "Show HN: OpsBroom" to the front page. Repeat. |
|