A lot of you have a lot of faith in people reviewing PRs. I know a few Sr. developers, that if shit was too busy, would skim it and say 'fuck it, it will be QAs problem. If you put this in the correct sub-system in file that would only be executed once a month, for example a maintenance class, It would be really hard to notice something is wrong if it didn’t cause issues seen immediately. Maybe this is the story of an intern that added something that also fucked up boolean comparisons in a subsystem used once a month. Where there is a 2 week lag between the execution and operations noticing something wrong.
I spent a couple of years doing contract work in a team that built the APIs that ran behind a fairly complex site; they understood that I was helping build the site, but really didn’t get that I had nothing at all to do with the UI or content, and yes thank you for your suggestions about the layout but that’s not something that I can “just go fix it” because a) change control is a thing and b) that part of the site is maintained by an entirely different team, from a different company, and I don’t have access to their source code
I don’t understand, isn’t it what is required for junior positions these days, every manager would tell you that they also required soft skills. His wish won’t even land him a job.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.