My manager started a company and I was his first employee, he literally started it because he wanted to make use of my talent.

So one day I finished my project on Friday and took in advance Monday and Tuesday off. Went back Wednesday to find my manager angry like "you didn't finish your project, you costed us money with our client company (a big ass famous one) I am putting you on probation and you could probably get fired if you don't get yourself together" and he said that my colleague had to do my whole work that I supposedly didn't do.
So I went to the code and checked. And I found that what my colleague did was re write my code in a different structure and pretended like he did everything and did do anything.
Got passed off so I wrote an email to my manager with the commits and links to them and their builds and made sure it's well explained, and titled the email "resignation letter" with me expressing at the end how angry I am and informing about my resignation.
Later on he replied saying it was a misunderstanding and there was lack of communication and he could give me I raise.
I insisted.
One week later I got hired by the client company and suddenly I was sitting on the other side of the meeting table. And it felt so damn good.

On Friday I deployed to a life site without going through code review or any testing whatsoever. I am now known around the office as 'Billy the Kid'.

I recently joined this big MNC after shutting down my own startup. I was trying to automate their build process properly. They were currently using grunt and I favor gulp, so I offered to replace the build process with gulp and manage it properly.
I was almost done with it in development environment and QA was being done for production.
In the meantime I was trying to fix some random bug in a chrome extension backend. I pushed some minor changes to production which was not going to affect the main site. That was in the afternoon.
This Friday my senior rushed to me. It was like he ran six floors to reach me. He asked, did you push the new build system to production, I refused. He then went to the computer nearby and opened the code.
It was Friday and I was about to leave. But being a good developer, I asked what's the problem. He told me that one complete module is down and the developers responsible for them left for the day already and are unreachable.
I worked on that module multiple times last month, so I offered my help. He agreed and we get to work.
The problem was in the Angular front end. So we immediately knew that the build process is screwed. I accidentally kept the gulp process open for anyone, so I immediately rebuilt using grunt and deployed again, but to no success.
Then I carefully analyzed all the commits to the module to find out that I was the one who pushed the change last. That was the chrome extention. I quickly reverted the changes and deployed and the module was live again. The senior asked, how did you do that? I told the truth.
He was surprised that how come that change affect the complete site too. We identified it after an hour. It was the grunt task which includes all the files from that particular module, including chrome extension in the build process.
He mailed the QA team to put Gulp in increased priority and approved the more structural changes, including more scrutiny before deployment and backup builds.
The module was down for more than 5 hours and we got to know only after the client used it for their own process. I was supposed to be fired for this. But instead everyone appreciated my efforts to fix things.
I guess I am in a good company 😉

Emergency change request on a Friday, guy who completes change leaves early, 29 minutes later alerts start going off. Fml.

The current project I'm working with had 3 devs including myself until Jan 1st. Now we're only two, because our lead/manager started to work in other projects and trusted us.

Since that happened, my first PR/Commit of the year was in Jan 5, and it's still open, without any kind of review or comment, as well as my other five (eight in about a day) PRs, while he's making commits directly into develop/main branch, causing conflicts everywhere on what I did...

I'm leaving on friday because the contract is ending.

Good luck I guess.

I'm still a junior myself, but some fundamentals I've told my coworkers:
* Commit more, regret less
* Yes, you can remove a commit, if something goes wrong.
* No, I'll not explain again how to undo a commit you pushed typo to you feature branch. Feel the shame of pushing "Fix typo" commits
* ask, if you are stuck or unsure.
* don't do deployments at 5pm Friday. 6pm results in less crashes in production for some reason /s
* Don't be like me. Go to sleep at appropriate times

My Friday night (12.30 AM) coding session commits..... Time to stop.