Me: *finds severe bug in school-contracted software, emails teacher about who to talk to to get it fixed*
Teacher: "should I report you on grounds of computer misuse and hacking or...?"

thanks fucker, school-contracted company it is.

Got a weird bug report, 6 red bull later i'm a energizer bunny on speed. But have found and fixed a severe underlaying bug. Can't believe noone had noticed for years.

Now i'm afraid to report it to my boss cause it most likely costed us a lot of money over time. And I just got shafted in the pay raise so my loyalty is low.

Working on a feature for about a month, give or take. And the whole way through, I'm feeling worried that what I have is very little in relation to how much time I've spent on it.

Well, guess what? I send the PR, and see all the commits put together -- and ONLY THEN I'm able to realize it's a WAY bigger contribution than in my wildest fucking dreams.

So now I'm thinking shit, I may have gone too far in a few places...

Anyway, the feature is not a 100% done: this is just the first step lmao. But I'm glad to get a break from this, though it was a very cool thing to get to work on, I definitively got severe tunnel vision focusing so much on it. Time to return to smaller bug fixes, let's go!

**ANXIETY INTENSIFIES FOR NO REASON**

Nothing like constantly having to spend 3-5 days of spin up on trying to help another team with their microservices because they have such a severe lack of documentation that I can't just follow a readme to get their projects running. Instead, I have to bug one of their developers to help me get it up and running (because they use non-standard project setups and dependency management), delaying things even more. No matter how much I scream that we need documentation no one makes it a priority.
Did I mention these are microservices written in Golang and I'm a front end developer? And I'm being made to work on back end tasks because we have a crazy high attrition rate and they won't back fill the back end positions.