Programming, chess and football. Trying to be curious about everything, which sometimes leads to watching stupid stuff on yt at 3am. Polish retweets included.
> Open X
> Ralph Loop" all over TL
> 7K stars
> look inside
> while loop over a todo list
> there's a meme coin about it?
> it got rug pulled?
> scroll
> muted acc
> scroll
> muted acc
> scroll
> SWE jobs automated in 12 months
> scroll
> "Here are 100 Claude Code subagents"
> scroll
> LLM hate post
> scroll
> screenshot with 10 claude codes open
> "if you aren't doing this, youre ngmi"
😃
Chinese scientists have developed,
The best shortest-path algorithm in 41 years!
A team from Tsinghua University has broken Dijkstra's "sorting barrier" - the first improvement since 1984.
Just use for a world-map 🤯
Paper - https://t.co/0AhR5O7vl4
https://t.co/a9KMVRuYGx
All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay.
I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it.
Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence.
Two of the most common OSS business models:
- Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...)
- Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary
Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more.
The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't.
Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing.
Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly.
The final irony: OSS trained the models now killing it. We built our own replacement.
My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.
i'm sure ozempic is great but have you tried:
- never snacking
- never eating out
- avoiding 95% of every grocery store, only buying produce
- pre-portioned meals
- 90 minutes of exercise daily
- walking after every meal
- 10k steps daily
- raw veggies to start each meal
- 7+ hours sleep each night
- done eating at 2pm each day
- berries as dessert
- only whole foods, no processed anything
- strength training 3+ times each week
- minimizing stress levels
have you tried all that? all we have to do is all those things and the weight just falls right off, i don't understand why we need an easier option
Just saw a software devloper coding in a cafe
-NO Cursor
-NO Windsurf
-NO DeepSeek
-NO ChatGPT
-No Google
He just sat there typing code manually in vim on his rusty Thinkpad and reading man pages on Arch Linux
What a psychopath 🫣
I wish more library/framework docs had a section for “Stuff we don’t do well”.
Example: “Tailwind works best with a component abstraction. Without components, Tailwind leads to a lot of duplicated class declarations.”
Tell me when I *shouldn’t* use your library too.
Clerk has been down with 500 errors for 20 minutes, meaning nobody is able to login or signup
Really makes you think again if you want to outsource auth 😁
This is Nitro, a text editor I’ve been working on. It’s written in C++, it’s super fast and lightweight. The package is currently only 6MB. The idea is that everything should come as a plugin. Alpha version releases in ~20 days and in these 20 days I’ll be sharing screenshots and info every single day.