Lukas Friedrichsen

Mechatronics engineer, or, as some tend to say, 'jack of all trades but master of none'...
But besides that, I'm just a hero for fun!

[E L H O T Z O @elhotzo]

CDU & CSU hassen das Deutschlandticket, weil ein günstiges Zugticket mehr für die Mobilität von Millionen Menschen gebracht hat, als die letzten 10 ihrer Verkehrsminister zusammen

[Ryanair @Ryanair]

copy nothing

[Ms. G 💖 @pragueyerrr]

who’s colonized now BITCH!!!!!!!!!!!!!

[🏳️‍🌈SuperFloxes🏳️‍🌈 @SuperFloxes]

@fin_martre There’s something kinda profound about him going through all this nonsense, and then being like “the world isn’t all that bad, actually”.

[N @dearvotion]

type of vibe i’m on

[No Context Brits @NoContextBrits]

She never should’ve taken that fight.

[Adam Singer @AdamSinger]

Dogecoin is up 170% in the last month

[Peyman Milanfar @docmilanfar]

double-blind peer review

[gaut @0xgaut]

Statisticians vs. Polymarket

[×͜× Rokhaya ⸆⸉ ໑̣ @RokhaLovesHS]

for real, america can’t be real

[Dennis @dkardonsky_]

Pretty bold take

[sophie @netcapgirl]

sorry babe the salesforce backpack stays on during our kitchen talk

[Shuren @shurensha]

look. im getting real tired of people suggesting my contacts app doesn't need a full microservices setup. moved from $8 to $48 droplet because APPARENTLY running elasticsearch + mongodb + postgres + redis + kafka with full event sourcing uses "too much memory". anw what do they expect me to do? store phone numbers in a single table? like some kind of amateur??

my diagrams have 16 different services and yes they all need their own database. client keeps asking why saving a contact triggers 47 background jobs but they just don't understand best practices. keep getting OOM kills even with zero users but that's obviously because the health checks from my service mesh are generating too many events (each health ping needs to be stored in 3 databases for consistency). sure the app is currently crashing but that's only because we need more ram. might need to upgrade to the $96 instance to handle the write amplification from storing each crud operation as an immutable event

if anyone has solutions that don't involve removing my service mesh or suggesting sqlite i'm all ears. and no, "simplifying" isn't an option. i didn't spend 6 years studying distributed systems to build some legacy monolith

[Sam @SamOnBirdApp]

"If you gave an infinite amount of monkeys and infinite amount of time"
> Finite time
> Finite monkeys

[Jason Pargin, author of John Dies at the End, etc @JasonKPargin]

This meme is a joke but also life-changing advice if taken to heart