Wobbly One Of Myriads @wobblewuffess@awoo.space

Still rambling... the day I broke down before my vacation I was oncall.

Senior SRE asshat made an undiscussed change to our Pagerduty settings at 11pm the night before which caused me to get paged by bullshit from 3am-5am and then like every two hours that day.. because of a bug in pagerduty's API... which was why we had disabled the thing he turned back on without asking or talking to anyone about... there was even a jira ticket and open ticket with PD about it.

Well... I still have a job after all the shit last week and surprisingly, the Director of ProductOps backed me up and supported my desire to get the fuck away from my current team because we are clearly not compatible.

Now if only I could get back the week of vacation I spent a nervous wreck expecting to get fired because I failed to complete a project before said pto and broke own in tears are 13 hours of struggling on the last day before my pto because Senior SRE made me feel completely incompetent at my job and dismissed all the work I had done up to that point because the Azure DevOps Pipeline to actually deploy the code and create the infrastructure wasn't done and I got completely stuck and he was no help at fucking all at solving the piece I was stuck on.

So when I filled out my weekly gut check to my boss I explained the situation, my feelings and why I was struggling and my boss went right for the "I don't think you are passionate about what we are doing. It is not vector calculus* but it takes practice and dedicated -scientific- mind to do it well and I do not feel you are putting in the -work-(outside of work to keep up)." and some bullshit about how various undocumented pre-reqs were not completed by my coworkers but being marked as completed is "Just part of the job" (despite this being the 4th Azure DevOps Project we have setup and onboarded an engineering team onto in the last 3 months but no one but me thought to write a fucking checklist and document the process to get everything working but me.. after I went through all the bullshit lost time troubleshooting shit to find some basic setup tasks and permissions were not done by the person who said they did it all and handled the last 3..)

He also took some not so subtle jabs at my ADHD and how he felt after two weeks the accommodations the team made weren't working despite the effort I was putting into them (a 5 minute sync up meeting with Senior SRE in the afternoon.. and me spending 30-40 minutes most days writing a work journal and direct linking code commits, tickets and documentation related to the work I did that day)

Finally ending in offer to talk with the director about transferring me to another team.

I am kinda rambling to get this off my chest.

Anyway.. yesterday I had a zoom call with him... and the Director of our org and the director completely backed me up.

Upside.. I am definitely moving to another team, probably on the tooling and internal services side of the house.

All of that side of the business is in AWS. YAY. I mean I hate Amazon... a lot.. but Azure is so frustrating to work in and shit is often buggy, undocumented or old docs don't match new API and stuff. Or recommend things like "Then put the access key in plain text in your pipeline yaml" because doing it properly is a huge pain the ass.

Downside: Unless there is someone that immediately wants to transfer to the AzureOps team it will probably take 45-60 days to go through HR and get a new req for me to move into. Nobody sane would want to be on call for the Janus project (Which Azure Ops is responsible for) and I suspect whisper networks would have not nice things to say about my manager since basically all of the Janus Ops team quit... and I'll be the second person put under him to request a transfer.. the other was from my old team after we got absorbed by the Azure Ops team.

Fucking exhausted and tired of him making random ass changes outside of working hours. I know he came from a startup... but fuck.

FFff... Senior SRE made some changes to our PD last night around 11pm local for him to alert off of tags...

I got woken up at 3:45 but 4 "Sev 1" alerts paging that were all... in the WARNING category and not supposed to page...

FFFFFF I want to defenestrate our senior SRE right now.

So my coworker wrote a template to handle all the steps of a terraform deploy process (lint, validate, plan... wait for PR before allowing apply) for Azure DevOps Pipelines (which is the tooling we are required to use) so I reused his template, calling it correctly with variables replaced and whatever there are some minor permissions issues I need to fix.

But no... because he can't look at the pipeline.yaml and read it in place to figure out what it is doing (because it calls templates in another repo) he wants me to write a new pipeline from scratch... that doesn't use the templates >.> but also "doesn't want copy pasted work or to duplicate work we've already done"

WHICH fucking one is it?

Sigh... someone needs to tell our senior SRE to NOT FUCKING WORK ON WEEKENDS!

Monday rolled around after our 8am sync up with overseas devs he yanked me in a private call because he completely rewrote our Terraform best practices over the weekend and would like me to rewrite the 4 modules and deployments I spent all of last week working on to conform to his new standards before I go on vacation for a week... in 2 days.

@mawr I saw those things everywhere growing up.. as planters and organizers. I never knew what they were!

Monday Morning.. 3.75 hours of sleep.

Senior SRE has completely replaced Flux2 with ArgoCD on the k8s cluster we were going to hand off to a dev team today in a fit of manic rage last night....

This monday is starting out greaaaat. Not that I mind Argo.. I like it.

IFUCKINGHATEFLUXSOMUCH

I've spent the last two weeks working to get a helm package sorted for a new product dev environment. Today everything was done and it appeared to work

Coworker that built and set up Flux some how configured it to update image tag but not pull the image.

so for almost every way of checking if the changes were being pushed to the k8s cluster and if helm was updating the build image on the surface it was working.

But really it was keeping the same image and changing ALL OF THE FUCKING TAGS TO THE NEW BUILD TAG

I hate this..

Been working on a thing all week and it works, it is down and deployed. Merge all the helm package bits into branch because branch per environment (seems weird to me but whatever)

Senior SRE starts commenting a ton on the Jenkins file... which he wrote and my coworker fucked around with is solely for testing because this is project fork of a thing from that team but we kept the code in the same repo for some reason.
so it has to actually work and shit for PR to be merged.

I don't know shit about jenkins files, I didn't touch it, or write it or do anything with it... but now instead of having a chill friday afternoon of working on some personal development goal training stuff... I'm the one who has to -Fix- this thing because I'm the one who put in the final PR.

So it is clearly my fault... blame and commits aside. But also because both of them are on East Coast time.

And they did not mean had the helm package and chart been tested but they are on the east coast and done for the day... sigh.

If you use some weird word short hand for a process that nobody else knows and it sounds exactly like some other actual process with a tool used.. I hate you.

"Have you done a manual helm deployment to test this?" - comment on a helm release package for Flux2 Helm Controller API

Uh no.. because this is stuff to make Flux understand how to run the Helm API.

The helm package and charts were tested before I started this....

Me wasting a day trying to figure out what the hell they meant....

@Soreth That was similar to my experience but add like serious fatigue around the 24 hour mark that lasted for two days.

Second shot was less bad.. aside from sleeping like 15 hours the day of the shot. Just really heavy fatigue and lots of unplanned naps.

So this morning after presenting a big overhaul that I've been working collaborative with other junior team member on to my old project's engineering team and it going well I get asked to work on Flux thing for new product we are onboarding.

I don't know a lot about flux but it is mostly just yaml bullshitting and I can work backwards from other working examples, especially since bits of it are going to be reused from Other project.

I ask junior coworker if he has any docs for the stuff for this and naming conventions etc he says no.

After a couple of hours I have the basic stuff done for this helm release thing and post up a PR for review. With a comment about how "Since the globals aren't done I don't know the name spaces we are using or service accounts etc, will update them when done."

Other junior coworker has been working on the base globals since last week... complains about how all my values/names/etc are wrong.... then suddenly opens a new branch and commits a huge bunch of shit with about half the base and globals done. With the things I needed... so now I have to go back and re do a bunch of fucking work... and of course the tickets weren't tagged with any sort of depends on...

Like maybe... if that stuff wasn't done.. Senior SRE shouldn't have assigned me the ticket that depended on it? I don't know... fuck.

so far new team is super shitty at ticket scoping. Like at best they put a name in the ticket and a short blurb of what counts as success...