Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "why brew?"
-
Summary: Burnout, and everything's broken.
I don't feel like doing a damn thing today. I look at the code and cringe. I look at Slack and think "ugh. i can't." Mental capitals are even too much work.
(I've started reading "Zen and the Art of Motorcycle Maintenance" to try and combat burnout. I'll write a rant/story about it here if I find it helpful. but all I want to do today is drink tea and read.)
But onto the story:
Heroku is deprecating support for and will automatically upgrade any old verisons of Postgres running on its platform after August something (like five days from now).
I performed the upgrade to PG10 on Sunday (and late into the night), provisioning a new follower, blah blah blah.
However, the version of Rails we're using (4.2.x) doesn't support PG10 sequences, so I manually added in support via a monkeypatch. I did this on our QA servers first, obviously, and everything worked as expected. After half a day of no issues, I did the same on production, and again: everything worked as expected.
But today? I keep hearing about new things that are broken. One specific type of alert doesn't work for one specific person (wat). Can't send [redacted] at all. Can't update merchants! Yet there are magically no errors logged.
That last one (well, two) are just great; let me explain: when there's an error concerning merchants, the error gets caught, isn't logged or recorded anywhere so it just disappears, and the rescue block triggers a json response instead and happily exits. This is for an internal admin tool, so returning a user-friendly error is kinda stupid anyway, but masking what actually happened? fuck that dev with an obelisk made from spikes and solidified pain. That json response is also lovely: it's a 200 OK returning {status: 1, data: "[generic message containing incorrect IT jargon]"}. Doesn't even say "error" anywhere. Bloody everything about this pattern is absolutely wrong. Even the friggin' text.
Fucking hell. I want to pipe the entire codebase into shred and walk out the door.
But I digress. So many things are broken, my motivation is wanning to a sliver, and I have a conference call today where I'll undoubtedly be asked why everything is on smoking and/or on fire, and my huge and overly productive week last week will ofc mean nothing by contrast.
Ugh.
`shred ~/dev/work -zfu -n 32 &; ./brew tea --hot && wine ~/takeabreak.exe`rant zen and the art of motorcycle maintenance postgres heroku ship's sinking and the fixer's all fixed out burnout21 -
I'm a DevOps engineer. It's my job to understand why this type of shit is broken, and when I finally figure it out, I get so mad at bullish players like AWS.
It's simple. Install Python3 from apt.
`apt-get update && apt-get install -y python3-dev`
I've done this thousands of times, and it just works.
Docker? Yup.
AWS AMI? Yup.
Automation? Nope.
WTF? Let's waste 2.5 hours and figure out why this morning.
In docker: `apt-cache policy python3-dev` shows us:
python3-dev:
http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
But in AWS instance, we see we're reading from "http://us-east-1.ec2.archive.ubuntu.com/... focal/main" instead!
Ah, but why does it fail? AWS is just using a mirror, right? Not quite.
When the automation script is running, it's beating AWS to the apt mirror update! My instance, running on AWS is trying to access the same archive.ubuntu.com that the Docker container tried to use. "python3-dev" was not a candidate for installation! WTF Amazon? Shouldn't that just work, even if I'm not using your mirror?
So I try again, and again, and again. It works, on average, 1 out of every 5 times. I'm assuming this means we're seeing some strange shit configuration between EC2 racks where some are configured to redirect archive.ubuntu.com to the ec2 mirror, and others are configured to block. I haven't dug this far into the issue yet, because by the time I can SSH into the machine after automation, the apt list has already received it's blessed update from EC2.
Now I have to build a graceful delay into my automation while I wait for AWS to mangle, I mean "fix up" my apt sources list to their whim.
After completely blowing my allotted time on this task, I just shipped a "sleep" statement in my code. I feel so dirty. I'm going to go brew some more coffee to be okay with my life. Then figure out a proper wait statement.7 -
I started working in a company where they use scala/akka stack, that requires a huge amount of hw resources to compile and debug, so my boss bought me a new laptop: a MacBook Pro. I came from a Dell with Linux Fedora, and now:
FUCK YOU APPLE YOUR COMPUTERS ARE SO SHITTY
JUST EXPLAIN ME WHY THE FUCKING KEYBOARD IS SO A PIECE OF SHIT WITH THE FUCKING COMMAND KEY
FUCK YOU COMMAND KEY
FUCK YOU MAC OS WITH YOUR SHITTY POLICIES YOU CAN'T INSTALL THIS PROGRAM BECAUSE YOU HAVE TO ENABLE UNKNOWN RESOURCES
FUCK YOU BREW AND BREW CASK WHAT THE FUCK OF TWO SHOULD I USE
FUCK THE STUPID TOUCHBAR I WANT THE FUCKING ESC, DELETE, F1, F2 AND SO ON
FUCK YOU APPLE YOUR MAC IS FRAGILE AS FUCK I CAN'T THROW THAT FROM THE FIFTH FLOOR OF MY BUILDING LIKE A THINKPAD
FUCK YOU SAFARI THAT YOU DON'T REFRESH THE PAGE WITH F5
I have a small gif for you just to explain how much shitty is Mac OS17 -
Dependencies suck.
I wanted a ruby gem and needed an older version of ruby to run it. Fine, what's the best way to get multiple ruby versions on one system, apparently rvm.
Now I want rvm.
I can't have rvm without getting gnupg first though.
Before I can get gnupg I need brew.
Now I have brew setting my computer on fire compiling god knows what so it can get gnupg so I can get rvm so I can get the ruby version I want to get the gem I want!
It's been running for quite a while...
This isn't the first or last time that the convenience of packages and versions leads to a maze like trail of prerequisites you need to follow.
I'm sure there's some tool that would've helped with my problem, but the problem shouldn't be this bad to begin with!
I understand why it happens but it still sucks and it's a lot of wasted time.
Frankly I'm expecting some people will have gotten so used to this kind of insanity that they won't get why I'm renting about it, oh well, it made me feel better and gave me something to do while brew is melting my machine.3 -
I'm pissed
Why the fuck do I need to install brew to have AWS' SAM CLI? Couldn't you provide me with an install script or an apt package? Now I have to install linuxbrew (never used it) and pollute my os with crap I'll never use just to have this fucking cli so I can create a fucking lambda function project on intellij idea.
Oh, I can install it with pip. Well yes but actually no. They fucking deprecated the pip package and just gave me a link with instructions on how to install it with brew.
Aaaaaaaaaaaaaa
I was praising AWS for their good docs yesterday, now I'm pissed at those lazy fucks >:(11 -
Running brew install PHP
I soon get that brew is installing python and compiling its sources.
WHY?3 -
Is this feature where brew breaks dependencies at random whenever you run it a reason why people love macOS?1
-
are you guys facing some issues with some websites ? like google devrant etc not workiny in browser and bing is working spotify is working brew is working.
any clue why so??????