work rant
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...
re: work rant
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...