Ask HN: Am I being unreasonable?
Our manager has been tasked with coming up with new "standards", tools and processes for everything.The team has been divided and a new "leadership" team has been formed and the existing developers have been sort of left out, one of the things that really bothers me is the over complexity and artificial constraints being enforced, it's not that I'm not open to change but as I've grown older and experienced (and I have to admit, cynical) whenever I see unnecesary complexity I run away screaming.
Just to give you an example of what I'm talking about: The deployment, provisioning and packaging workflow that these guys have come up with is an absolute nightmare form my point of view, consisting of multiple ansible & gradle scripts, packaging everything as RPM files, convoluted code review processes using crucible, and git branching strategy based on jira tickets, etc, etc this is a standard that must be followed for EVERYTHING, have a simple 3 line bash script? oh you have to write a gradle build file, "tests" and ansible scripts to provision it.
I have to admit I absolutely loath devops but this seems to me like it will be extremely difficult to maintain in the long run, we are also now being forced to use python (we are/were mainly a scala shop) so we cannot leverage existing code as everything we've done before is considered "garbage" or using the more politically correct term, "legacy". What really pisses me off is that we keep getting shut down, and everytime we raise a concern we keep getting told that we are not "real" software engineers and that we must skill up.
Since I am NOT an ansible/devops guy I have to ask before I rage quit:
Am I being unreasonable? am I taking this too personally?.
6 comments
[ 7.4 ms ] story [ 19.8 ms ] threadIt sounds like the culture is shifting in a direction that doesn't fit with the way you'd like to work. Time to move on, simple as that.
It feels like we are being treated like children and stuff like not being "real" software engineers coming from people who have contributed 0 to the existing code base really angers me (I am a very emotional/passionate person though).
It sounds like the incoming team indeed thinks of itself as superior in some respect. That's a dangerous way to think (regardless of whether race is involved), because they won't be able to learn anything if they've already disregarded the thoughts of those that were around before they showed up.
It also sounds like they are a bit more conservative ("convoluted code review processes... based on jira tickets") and perhaps a bit more authoritarian ("standard that must be followed for EVERYTHING").
Those may or may not be traits that the company needs to succeed at this point in time, but you're certainly not required to accept them or agree with all of them.
And you shouldn't be made to feel like a child if you've built the foundation of the product. It is disrespectful.
So you just need to ask yourself whether its worth it to try to work with them or just move on.
Most of it doesn't seem to unreasonable at it's core, just too extreme.