4 ms·
I recently had a conversation with my "technical" manager. He basically told me in no unclear terms that it's "business as usual" and totally expected that you
by hsn915 5y ago
I recently had a conversation with my "technical" manager.
He basically told me in no unclear terms that it's "business as usual" and totally expected that you just fumble around the codebase not really understaning what's going on, write or fix the code while feeling frustrated and demotivated, push changes that are full of obscure bugs, wait for users to run into these bugs and report them, then try to fix them while still not having a clue what's going on in this codebase.
He used the fact that this product "makes money" as a reason that we should not be caring about making the codebase any easier to understand.
How is one supposed to respond to this kind of mentality?
- firebaze 5y agoNot implying this is the case for your situation, but occasionally there's another potential perspective: suppose you're a junior dev, not much experience yet, and you don't really understand the business case at hand. Less experienced technical managers may resort to a similar wording as the one you just mentioned to prevent that dev to refactor something without really having a good idea how it should be in the first place. Again, not saying that's what's going on in your example, but I've seen this more than just once.
- hsn915 5y agoYou don't tell a junior that it's business as usual to push code without understanding what you're doing.
- firebaze 5y agoIf the junior doesn't understand the reason behind the code, and if you're an inexperienced manager, you totally could do that. Sad, but from my own experience this happens. And sometimes it's the least bad way to teach.
- LandR 5y agoLeave.