Wobbly One Of Myriads @wobblewuffess@awoo.space

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....

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...

So I'm once again the only west coast member of an east coast team and have to put up with things like "Ideally I'd like to have you around from 10am-4pm EST for collaboration because your quality and velocity of work is very good when you are collaborating with the team."

Me: "I have trouble being functional at the once a week 8am local (PST) meeting to sync up with Euro devs."

Also... like.. you squished me onto a team with the one other survivor from a 6 person SRE team and hired one senior SRE (my team was 4 people + 2 dedicated SWE for our product that we collaborated heavily with) and both of us were the junior members of our teams.. oh and I guess there is the one contractor from the contracting firm but money to keep him ran out so he is gone.

So 3 people + manager... and taking on the work of formerly 12 people with 2 separate managers... and we on-boarding new products to support... by stuffing in the janky other product infrastructure because 2 people from other project out vote me (Manager and other junior SRE)

While my old product and the other product share some technologies (Azure Kubernetes stacks and terraform...) other product is all managed by Flux and had a massive project (mostly done by contractors to update it to the latest Flux)

We passed up on trying Flux as a CI/CD solution because it had a lot of problems with playing nice with the proper way to build Terraform stuff and while that is "fixed" it is still kinda janky.

I'm off on a tangent...

Apparently we have upset a neighbor who was enough of an asshat to stick this to my car window (leaving a bunch of residue) with heavy masking tape.
Reader's note: Property manager supposedly pays for yard care, tenants are not responsible according to our lease.

If they had put this on the door to the house I'd be less upset.. aside from the tone and general ass hattery of the letter.. but it also made one of our roommates feel unsafe.

Look.. I just want to fucking be a dragon in my solar powered wilderness cave and like run/build your infrastructure from remote with a fat fiber line and eat tasty veggies from my personal vertical garden with my kobolds >.>;

Is that too much to ask?

I guess the other part of this... is I don't eat/drink/breath/LIVE DevOps/SRE stuff.

Like outside of work, I want to do -other- things and so many fucking people in the space are like "Oh yeah in my free time I run a mini-kube cluster and build all this random shit to play around with it. But I don't actually -do- anything with it.. it is mostly just following some greenfield deployment doc and building it to have done it but isn't it cool?"

I'm like... why? yes the experience was probably useful.. but was it fun? Was it relaxing? Did you actually -do- anything with it when you were done?

/ramble

Like I do this stuff because I stumbled into it, it pays well enough for myself and my partners to exist and I'm clever/smart enough to be competent at it and that isn't enough for a lot of my peers, I guess?

Why is that there seem to be only two different types of Orgs in Ops/DevOps spaces?

Traditional fucking man-space mix of fresh meat techbro college grads tempered by married, cishet with kids/older Ops guys but it is all fucking guys..

And...

LGBTQ+ Rainbow of intimidating super smart ex-googlers/FANG folks with SWE backgrounds that are crazy technical and experienced while usually being groundbreakers/public figures in the field?

I get why the second sort of Org would form... but there is like no in between. That seems like a huge problem.. and fuck I don't know, I feel like I don't have a space to actually exist outside of putting on nerd camouflage, being super vague about my life outside of work because I can't related to my coworkers and if I did rely my life experiences even the most socially liberal cishet coworkers would be like "that is fucking wild"

At the same time... I'm really fucking tired of being -Deadname- at work when outside of like work and things that require a Real ID, I am not.

Maybe I'm just babbling because... being remote for the last year let me experiment with dyeing my hair and painting my nails and I'm so fucking done with western man office culture.

30 hours after pzifer shot 2... I slept through 15 hours of those 30.

Mostly just really tired.. everything takes a lot of effort/energy.

Fffffffff... yes lets totally move all the source of truth for all our terraform infrastructure for -my- project, the one I worked on for the last 2 years into Azure DevOps (from BitBucket) without consulting the Engineering Team using it.. cause reasons.. I'm sure that will go over well.
Yes we'd like to build of AzDevOps Pipelines to automate the deployments (if we can get that shit working at all because arggghhhhhhh jank) instead of having people grab the terraform from SC and run terraform plan/apply locally on their personal machine... but we don't need to lift and shift 40+ repos into fucking Azure DevOps to make that work... especially when we as a company are probably ditching bitbucket and moving to Github in the next like 6 months... with new security requirements for where code source of truths can live.

But this is the 3rd time someone on my new team has asked if we should move the entire code base to Azure DevOps.. not to mention we'd need to refactor numerous terraform modules because you can't variable-ize "source" for a module

If there is something I really don't like about the new team it is that they seem to be intent on creating additional work when it is not needed if for no other reason than to do something "new".

It is super frustrating.