datatub

Hot take: we should not be using AI to be more productive; we should use it to produce more polished work.

@thdxr x.com/datatub/status…

i really don't care about using AI to ship more stuff it's really hard to come up with stuff worth shipping i want to ship the same amount of stuff with higher quality both in product and code

@mischavdburg You don't have time to take projects because you're too busy writing YAMLs? jk

3 years ago everyone told me Kubernetes was a waste of time. Now I turn down $200/hour freelance projects because I don't have time. Glad I ignored them.

@valigo I even think they are training on private repos. For the first time after GitHub appeared I'm thinking about hosting my own private Git.

They still believe in opensource licenses... People launder GPLd code at scale these days, and you can't do anything about it. If you don't want your code to be tampered with - close it. As soon as you show it - it's not yours anymore, unless you have millions on lawyers.

@kevinroose @sama social media scheduler

@sama What’s the app?

I am very excited about AI, but to go off-script for a minute: I built an app with Codex last week. It was very fun. Then I started asking it for ideas for new features and at least a couple of them were better than I was thinking of. I felt a little useless and it was sad.

@jarredsumner support for .vue files

what large features should I run claude in a loop to try adding to bun constraints: - must have a large test suite with positive & negative tests that verify it works - must have strong evidence of being something people want & would use bun for

@jarredsumner x.com/datatub/status…

Guess the next parser we're adding to Bun

@Grady_Booch Wrong abstractions are not foreign either in the software engineering.

The rise of AI programming agents is changing the nature of software development in the same way as did the introduction of compilers in the time of Grave Hopper. I’ll say it again: the entire history of software engineering is one of rising levels of abstraction.

@MarcJSchmidt I fully support this mindset, but what gives you confidence the AI companies (Github/Microsoft in this case) will not use your closed-source code for training and still make it easy for LLMs to generate the stuff you implemented?

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.

@wesbos AI slop everywhere

What the HECK is going on with tech? In the last week: Multiple cloud outages, x DMs totally broken, antigravity doesn't work, my watch is showing me 15 year old cal events, mac OS is a mess, email is spammed to hell and every nerd on here is talking like new AI is the second coming

@arvidkahl Yeah, my corporate job

As a founder, do you have time for hobbies?

@trashh_dev It's the only scalable option. And Posts are CRD's.

going to start a blog. should i use kubernetes?

@iamakulov I'm not sure if you are shooting for the same thing (looking forward for that article), but funny enough, for a content rich site, I just started experimenting with using normal links because of the bfcache issues with all these SPA frameworks. github.com/remix-run/reac…

feels so good to be writing something again huh

@ilovemy__house Apparently I was searching for this tweet

Why am I scrolling. What am I searching for

@bunjavascript Please provide somewhere in the env var the ID of the worker / thread so it can be leveraged to connect to the particular resource that code / test (e.g. db instance). Rails uses this to great success #parallel-testing-with-processes" target="_blank" rel="nofollow noopener">guides.rubyonrails.org/testing.html#p…

In the next version of Bun `test.concurrent` in bun:test starts the next test without waiting for others to finish

Nice read and a reminder to be more sloppy when developing new features evanhahn.com/how-i-build-so…

bro will replace AI

@GergelyOrosz Are you sure this story is legit? It's likely a marketing stunt or something stupid like that.

One takeaway from the Soham story (dev from India with likely a fake CV hired to 10+ AI startups in Silicon Valley, working parallel for many): Demand for AI Engineers (devs who built real-world AI applications) who worked at startups FAR outstrips supply Use this if you can

@lekemula Yes, exactly this.

@datatub Part of the problem: overusing metaprogramming just because “that’s how most gems do it”, and yes, especially in Rails. It comes at a cost: poor LSP support, making code harder to navigate, understand and refactor.