I've just realized that I've been featured for 4 consecutive weeks!
Actively contributing to Rails has been a delightful experience, and I will surely continue to do so.
A special shout-out to Jonathan Hefner and @eileencodes for their swift and thorough reviews!
Après énormément de travail...
Nous y sommes enfin. Je vous laisse lire cet article complet pour voir tout ce que Shobu propose dorénavant, car ça va bien au delà des tournois ! https://t.co/AQgXosvUpy
Damn it feels good to finally merge this one @rosapolis! Opened long ago, in a forgotten time of hand-coding in 2024.
Thanks for unintentionally putting me on blast @jeremysmithco and kicking me into gear on finishing it out a year ago 😆
https://t.co/42frT26HBT
@GregMolnar You're right. I'm actually considering having a local AI because I have a feeling Claude etc. will face outages some day.
Regarding debugging, if you're NEW into "software engineering" you're quite doomed, because this is stack overflow on big steroids. ==> laziness guaranteed
We heard you. And we agree.
In light of recent developments in physical media, GitHub is proud to announce that you can now obtain your public repo on CD-ROM.
Keep it. Lend it to friends. Pass it on to your children.
Your code is physically yours, forever. Until you lose it, let's be real.
Order yours today.
https://t.co/z041pdMH7h
A lot of people want to use AI to cheat, to skimp, to be lazy, to bullshit, to pass off bad thinking as profound.
They think we can't tell. We can tell.
Use LLMs to do what wasn't possible before. To apply relentless attention and care. To turn the 8/10 into the 10/10.
@GregMolnar I did, every patch release I open a review app, and the RAM ( on a sidekiq heroku dyno ) still is x2 than on 3.4, so it's a bummer since i need the least amount of ram possible (with some leeway ) so that i can scale them to parallelize some tiny jobs that requires a bit of ram
Since ChatGPT knows my name is José Valim (it is in the account info), it bias its replies towards Elixir, even when I want impartial discussions.
Memory is disabled too. I may need to rename the account to John Doe.
Been too busy lately to tweet every nice Ruby perf PR as I spot them. So I went through my notes and dumped all the notable ones into a single roundup. Some of these are insane (like 800000x speedup) - enjoy! 🚀
https://t.co/5XIKqbuwrj
#ruby#performance
C10K problem
in 1999 a software engineer named Dan Kegel wrote an article that changed how web servers are built
the question was simple how do you handle 10,000 concurrent connections on one machine
at the time Apache used one thread per connection, each thread needed memory for its stack around 8MB and 10,000 connections meant around 80GB of RAM just for stacks
the system spent more time switching threads than doing real work
servers crashed long before reaching 10k connections
this became known as the C10K problem
There's a disturbing trend of developers I've known for years now suddenly being unable to discuss even basic aspects of software development. They have become so dependent on LLMs, they can't even describe how to design a system anymore. Feels like losing friends to dementia. 😢
@UltraLinx@brian_lovin Could you make a tweet ( or video ) in a month or so about if going from 6K down to 5K has become an issue for your work. Or is going from 60hz to 120hz worth it more than the 6K resolution.
Cheers