🧑‍💻 Niels

@mokkenstorm.dev

🌱 level 32 carbon-based lifeform 🔧 tinkering my way into the ATmosphere 🇪🇺 eurosky netizen, practically dutch 🏳️‍🌈 they/he | queer | vegan | polyam ☀️ solar/punk adjacent 💼 open to work (fp/ts/php/devops or esoteric shit) "we were born to inherit the stars"

If you’ve never done a multi day music festival I would highly recommend it. By day 3 any semblance of normalcy has been dissolved and it’s just a recharged soul, connections for life and endless hedonism

burning spare fable tokens on "hey I have these invoices / tax returns / mortgage things please help?" and seeing the little automated browser mouse pointer click through the Dreaded Administration Forms truly makes me feel like we are in the future

Here's my two minute explainer of atproto: it is in essence a water cycle. - Clouds hold water. - They precipitate water over mountains. - Water funnels down mountains into rivers. - Rivers branch off into lakes. - Water evaporates back into clouds, the cycle repeats.

A diagram of a water cycle.

>someone asks me to review their build failure >ask them if it's their PR's fault or CI's fault >they don't understand >pull out illustrated diagram explaining what is their PR's fault and what is CI's fault >they laugh and say "it's good code ma'am" >i review the build failure >PR's fault

> I asked a few AI researchers whether they could name any other real-world software that scales so poorly. None of them could think of any. these ai researchers have clearly never heard of Ruby on Rails

# Your polycule should be eventually consistent. Classic solutions are gossip protocols but we all know the downsides there. Informal data leaks, miscommunication, and heartbreak. Instead use CRDTs with signed messages. Or go all the way and use Fully Homomorphic Encryption! Everyone wins!