Hello! I am @andrewt and I have registered this side account so I can kvetch about tech without boring everyone who cares not one jot about it.
like we have a bug in our offline dynamodb stub that could modify objects after returning them, which to be fair was my fault, maybe because i didn't think anyone would get, patch and update the same object in one request (but rollbacks do).
but given the option of fixing it or treating it as an immutable fact of nature and writing a hundred lines of buggy production code to work around it i just can't fathom the mindset that chooses the latter
Jargon proposal: surburban architecture.
Each module of your codebase is analogous to a family household. Obviously they're all completely bonkers internally, but when the other modules are around the good china comes out and they're on their best behaviour.
You need to store the same data in XML and Json for different cache layers? Fine, no problem, behind closed doors you do you, but we do NOT talk about it in front of the Login-Pages, we are a RESPECTABLE module thankyou very much.
ugh, just been pinged by the fifth opsgenie alert in three on-call rotations and all of them are nothing
like i'm not against being on call in principle but some firms use it to patch rush-jobs caused by shit management and we apparently use it to wake devs up for no reason for some kind of uptime theatre?
well it can fuck off
a fantasy world where all the techbro wizards don't know how to do any spells except by summoning this one demon who they've enchanted to conjure up a pocket universe wherein four imps will build a complex system of runes and inscriptions in which a goblin will finally step and say a magic word that the wizard could have said in the first place if they knew what they were fucking doing, anyway i've been installing ruby gems today, how are you
ah what, someone on slack just thanked someone else for their help "restarting the server on the master branch" and now i'm scared that they've definitely done *something* but definitely *haven't* understood what it was they did because that sequence of words doesn't correspond to any real-world activity.
update: our third-party's oauth screen has a 'cancel' button and an 'authorise' button and *they both grant access*
i mean it's not that big an issue because who's pressing 'cancel' — it's like visiting a porn site and pressing the 'no i'm not 18 please take me to yahoo dot com' button — but really how does that happen
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!