
Dog walker / Ruby polisher / Go viber / GraphQL @GitHub
🛴
Joined April 2009
- Tweets531
- Following1.3K
- Followers173
- Likes491
I never could commit to a single technology and domain. Not great for career, but the vindication I feel now.
ALL HAIL THE GENERALIST.
I think I realized something exciting. Writing business software has effectively become harness (factory) engineering. Making sure the agents get the business context. Maybe going back to business software is possible 🥸
I just looked like a fool at work for leaning a bit too much into AI. Nothing too bad, but embarrassing regardless.
Good reflection moment :)
Model auto pickers needs to be solved quickly. Now I am lazy and spend $25 in tokens on git pull rebase and fixing some conflicts.
Not everything is an existential crisis GPT
Erwin Kroon retweeted
Merz has called for the systematic review of all EU legislation.
That's over 140,000 regulations.
Knowing the EU, that will take over 140,000 days.
So, I made bettereu.com where Grok 4.1 will review every document since 1958 -> 2025.
I think that CLIs for agents should have GraphQL interfaces. Gives them all the possibility to get as much information as they need.
GPT 5.4 on xhigh thinking is wild. Seems like it is questioning everything, its like seeing my own brain work in useless cycles when I try to buy a bread at the bakery but I don't feel like talking to people.
I ported npmjs.com/package/normalize-… to Rust for $2.40 in premium requests. Used autopilot in Copilot CLI with an initial prompt and spamming "How do we know we are feature complete?" after
I am not sure this is impressive or not, but it is cool. Result at crates.io/crates/url-normali…
If you use VSCode and @opencode you might like npmjs.com/package/@ekroon/op… for Copilot instructions support.
Erwin Kroon retweeted
We have 160 helpful Ruby and Rails devs in this Discord.
While it is nice to be this cozy, we welcome anyone to join and talk tech.
discord.com/invite/qfnMkxbBu…
I think we should rename tweet to twfkat
Because The Website Formally Known As Twitter.
We can further shorten it to twat.
So I presented on Sorbet type checking for Ruby some time ago. Not the best presentation, I am sorry.
However, at some point I remarked that the syntax for generics makes my eyes bleed.
I forgot about Typescript: read some code with generics and it’s flooding, so bad.
Can someone explain to me why to use const vs let in JavaScript / Typescript ?
It’s a thing that I let the linter fix for me and only means: this reference stays the same, but mutation still can happen.
Seems more an annoyance than something of value.
I am considering to rewrite Sorbet in Rust because I really really don’t feel like writing C++ and I want to contribute to it.
I hope it stays with consideration 🤪







