Then another message popped up. This time with a console.warn() logging level, so I just couldn’t ignore it.
That’s how you know this one’s fake. Most unrealistic part of the whole story.
The amount of times I’ve annoyed bosses about the worrying amount of warnings in projects that are in production, to then be completely shut down about my concerns is … disheartening.
No resolution of tech debt, ONLY DELIVER
Where possible, get things in writing. Even if you have to do most of the writing yourself.
“Dear boss, please confirm that, as discussed this <time>, warnings A, B, C, etc. are not to be considered important and that we’re pushing ahead.” CC everyone on the team and maybe another boss or two if you dare. Wording it better than I have here is undoubtedly possible.
Then you can perhaps stall and work on other things until you get a response one way or the other.
And if that results in shitty boss behaviour or employment jeopardy you have a timestamped e-mail that you can point to as the beginning of the end.
Of course, if you really need the job and can’t put yourself in that situation, instead document things for later. You can fire shots and warn customers on the way out rather than rocking the boat there and then.</time>
I tend to just ignore them and fix shit here and there as the opportunities arise. Whenever there is a lull, I can go and do some good. But sometimes the problems are truly deep and there isn’t much that can be done without a real commitment.
50 Shades Of Node
expired
expired
Both are incomplete, but the article is no longer paywalled
