After listening to about a dozen first-hand accounts, I’ve published what I know so far about the RubyGems takeover.
| site | https://dentarg.net |
| alternative | https://ruby.social/@dentarg |
| github | https://github.com/dentarg |
| https://twitter.com/dentarg_ |
| site | https://dentarg.net |
| alternative | https://ruby.social/@dentarg |
| github | https://github.com/dentarg |
| https://twitter.com/dentarg_ |
After listening to about a dozen first-hand accounts, I’ve published what I know so far about the RubyGems takeover.
EuRuKo 2025 – Back to the roots!
This year, we’re returning to a single-track, two-day format – just like the early days of EuRuKo! Expect focused discussions, deep technical dives, and an intimate community experience.
🎤 Thinking about submitting to the CFP? Go for it! EuRuKo is by the community, for the community, and even if you're not a regular speaker, your insights matter. Don’t hesitate!
⏳ CFP closes on April 10, 2025, 23:59 UTC – Submit now!
🔗 https://www.papercall.io/euruko-2025
Any experienced programmer worth their salt will tell you that •producing• code — learning syntax, finding examples, combining them, adding behaviors, adding complexity — is the •easy• part of programming.
The hard part: “How can it break? How will it surprise us? How will it change? Does it •really• accomplish our goal? What •is• our goal? Are we all even imagining the same goal? Do we understand each other? Will the next person to work on this understand it? Should we even build this?”
The effect of AI is to reduce the cost of •generating code• by a factor of X at the cost of increasing the cost of •thinking about the problem• by a factor of Y.
And yes, Y>1. A thing non-developers do not understand about code is that coding a solution is a deep way of understanding a problem — and conversely, using code that’s dropped in your lap greatly increases the amount of problem that must be understood.
3/