Yeah I’m one of the “I only want to write this fucker once so I will make it as solid as I can” types… and my manager + team-lead/principal dev is the “yolo send it” type.
We do not get on well. I’m probably going to switch teams or jobs soon.
I constantly call out juniors who do things like ignore warnings, completely unaware that the warning is going to cause serious tech debt in a few months.
But Ive also unfortunately shrugged after seeing hundreds of warnings because to update this requires me to go through 3 layers of departments and we’re still waiting on these six other blockers.
In my experience it’s the other way around.
Yeah I’m one of the “I only want to write this fucker once so I will make it as solid as I can” types… and my manager + team-lead/principal dev is the “yolo send it” type.
We do not get on well. I’m probably going to switch teams or jobs soon.
Both sides.
I constantly call out juniors who do things like ignore warnings, completely unaware that the warning is going to cause serious tech debt in a few months.
But Ive also unfortunately shrugged after seeing hundreds of warnings because to update this requires me to go through 3 layers of departments and we’re still waiting on these six other blockers.
Pick and choose I guess.
Then things will have to wait until the code is of sufficient quality to be accepted.