You want to use Redis as our primary db? Great idea, boss. You think tests violate DRY and you don't want me to write any? Sir, you're a genius.
You want to use Redis as our primary db? Great idea, boss. You think tests violate DRY and you don't want me to write any? Sir, you're a genius.
This is it really. You can't have responsibility without control over the things you are responsible for. People both below you and above you have to accept that. And "real" responsibility comes only from bearing liability for bad outcomes. Even if formal organizational lines prescribe differently, this is where the real boundaries will lie and to the extent there is any discrepancy it will manifest as organizational dysfunction.
I think its a key thing for junior staff who want more autonomy to realize. If you really do want to influence decisions your first step on that pathway should be to pay it forward on commitment and responsibility front. If you don't want to take responsibility its fine, but realize it puts a fundamental limit on your autonomy.
Edit: Maybe there isn't actually.
Woah, you have?? Odd -- software engineers, anyway, are literally paid to think.
I've never heard anything remotely like that, but if I did, I'm sure I'd start looking for a new place to work. That would be a clear sign that I'm not a good fit in that company.
If its just a negative for the business but no impact on me I'll point out the issues but wont go any further than that.
The problem is some leadership truly wants to touch the hot stove, and eventually if you keep saying "don't touch the hot stove".. you're the "doesn't let me touch the stove guy".
So sometimes you have to let people touch the hot stove.. as a treat.
Failure is a great tool for learning. How bad will these foot injuries be, given that we'll probably only have two chances to _really_ learn something?
Also, besides being the one to suffer the implementation of a terrible decision, you will most certainly be blamed for when things eventually blow up farther down the line.
Outside of the tech hot areas, OP’s advice is the only one that will get you a salary.
Meh, personal attack and you know nothing about me.
And the situation where you have to put up with a totalitarian boss because there are no other jobs in your area is so incredibly specific to whatever location you had in mind as an example—you still shouldn’t give it out as general career advice. Saying yes to everything is objectively terrible advice if you want to start a company or work in one where you make great, innovative, and highly valuable products, because that kind of output requires _thinking_ and disagreement occurs when free thought is allowed.
Which just happened again.
For someone who values free thinking and disagreement, you are having a lot of difficulty handling both at the moment.
My approach is to explain first, and do it my way anyway in case of hard disagreement. If boss disagrees with that what’s he gonna do? Do the job himself? Maybe he’s the boss but I’m in charge of the code base and architecture.
The right boss will keep their ego in check and ask: “what do you think? Do have any reservations?” It is also desirable to argue about something: back and forth “but what about this”.
But you will need to find boss and place like that. Not very common
Plus I get to see the downsides of another crappy approach and in the end I learn even more than doing things tHe RiGhT wAy.