Sure, do. Make a good automated suite and keep it sanitary. TDD if you can.
If your company has no testers because they fired all of them, pad your estimates so you can do real automation of the "sad path" stuff too.
Hiding your mistakes
Okay, this is pure soft skills.
Learn when to talk and when to shut up.
Learn how much to say.
Learn who receives news and how much detail s/he can absorb.
Learn who is going to blamestorm you to death the second they hear bad news.
Or, just read the first chapter in Pragmatic Programmer on "Give options, don't make lame excuses."
Fighting the Development Process
Nuance: Understand the way the wind is blowing, so to speak, but don't be a sycophant. Lots of shops use crappy, ill-designed, badly-implemented development processes. Don't accept them out of hand.
Insist on doing better, but in small ways. Enact the "Think globally, act locally." How can your team be better? How can you influence the whole org to be better?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Maybe put a different spin on some of these:
Test your stuff
Sure, do. Make a good automated suite and keep it sanitary. TDD if you can.
If your company has no testers because they fired all of them, pad your estimates so you can do real automation of the "sad path" stuff too.
Hiding your mistakes
Okay, this is pure soft skills.
Or, just read the first chapter in Pragmatic Programmer on "Give options, don't make lame excuses."
Fighting the Development Process
Nuance: Understand the way the wind is blowing, so to speak, but don't be a sycophant. Lots of shops use crappy, ill-designed, badly-implemented development processes. Don't accept them out of hand.
Insist on doing better, but in small ways. Enact the "Think globally, act locally." How can your team be better? How can you influence the whole org to be better?