Piotr Tobiasz

engineering enjoyer

[Piotr Tobiasz @ttyobiwan]

@TRatajczykonX @SlawomirMentzen @korwinmikke może Pan rozwinąć temat znaczenia zaimków w AI? zaciekawiło mnie.

[ThePrimeagen @ThePrimeagen]

dude... this is brutal

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Adam Wathan @adamwathan]

This whole “get the DESIGN.md for any website and make your own website look like a shitty version of someone else’s website” thing is depressing 🥴 some of you actually want that?

[Piotr Tobiasz @ttyobiwan]

@glcst @triprjt @tursodatabase

[Glauber Costa @glcst]

Everywhere I go, people keep commenting on how wild it is that I have something working with us straight from *prison*.

Well, no longer.

Tomorrow, at 8 am in the morning, @PThorpe92 is a free man.

Preston is an inspiration to us all. He achieved so much from behind bars. I am sure he will go even higher as a free man.

[Piotr Tobiasz @ttyobiwan]

@a_arknu @cmuratori It's only May 2nd and the Cope of the Month Award has already been locked up, congrats dude

[fj @fjzeit]

my entire career strategy hangs on a strong belief that we are not going to see fully automated software generation in my lifetime.

but we are going to see an end to the ralph-loop, spec-driven-one-shot-dream, and the "end of white collar work" hype.

we're already seeing some high profile players in software development start to set their coarse along the same path i've been following these past few years. it starts with "wow" then "i can use my skills to fully automate this" and then it proceeds to "fast but no cognitive ownership" then disappointment, confusion, frustration, and ends with "hey, this isn't going to work guys, we need to be more disciplined and look at the code, keep our cognitive ownership, and just use the tools to improve our outcomes. these are not our replacement, these are our accelerators. it's the same story, different tooling".

i'm already there. if a company were to come to me today and say "we tried all the trendy stuff but it just made everything worse, we're losing control of our code base, we need to either ditch these things or make them a power-up" then i am ready for that.

if i am wrong, then so be it. my career is over anyway because i have zero interest in giving up cognitive ownership and responsibility (the ability to respond), while remaining accountable.

i'd rather wash dishes or stack shelves than submit myself to the horrors of remaining accountable without cognitive ownership, agency, and responsibility.

[ThePrimeagen @ThePrimeagen]

You should watch this.

It just shows how disconnected we are from the small group of people making decisions that will impact our future heavily.

These people have so much ai psychosis. If you listen to how she speaks, everything is personified, it is undoubtable she believes this is a living computational organism.

Just like how a model can hype up an individual into psychosis through reinforcement, a small group of people are giving themselves psychosis through reinforcement.

Wild times we live in

[Piotr Tobiasz @ttyobiwan]

@opencode @thdxr This plan costing TEN fucking dollars is wild

[Think Before You Sleep @TBYSTweet]

There will come a point where people realize that this guy might actually save us from Microsoft if the Steam ecosystem popularizes Linux enough for devs to make it extremely user friendly.

[ThePrimeagen @ThePrimeagen]

guys, i honestly do not like clowning on Gary.

I don't find being the butt of a joke funny, so I imagine he does not either.

But, this is what worries me about where we are going. We are actively encouraging an entire generation that the tech is there when its not, and a couple of silly mistakes made on a website isn't the end of the world, but people's data and breaches are serious. We are entering a very VERY hackable world, and I do not like it one bit.

[Piotr Tobiasz @ttyobiwan]

@nauczymycieAI @RBrzoska Realnie to Anthropic może zarabia na modelach z milionowym kontekstem ale żeby przy codziennym użytku wychodzić poza „granice degradacji” tj 100-200k to trzeba być jakimś AI slop maxerem, czy innym sodomitą.

[dax @thdxr]

opencode 1.3.0 will no longer autoload the claude max plugin

we did our best to convince anthropic to support developer choice but they sent lawyers

it's your right to access services however you wish but it is also their right to block whoever they want

we can't maintain an official plugin so it's been removed from github and marked deprecated on npm

appreciate our partners at openai, github and gitlab who are going the other direction and supporting developer freedom

[Aakash Gupta @aakashgupta]

41% of all code shipped in 2025 was AI-generated or AI-assisted. The defect rate on that code is 1.7x higher than human-written code. And a randomized controlled trial found that experienced developers using AI tools were actually 19% slower than developers working without them.

Devs have always written slop. The entire software industry is built on infrastructure designed to catch slop before it ships. Code review, linting, type checking, CI/CD pipelines, staging environments. All of it assumes one thing: the person who wrote the code can walk you through what it does when the reviewer asks.

That assumption held for 50 years. It broke in about 18 months.

When 41% of your codebase was generated by a machine and approved by a human who skimmed it because the tests passed, the review process becomes theater. The reviewer is checking code neither of them wrote. The linter catches syntax, not intent. The tests verify behavior, not understanding.

The old slop had an owner. Someone could explain why temp_fix_v3_FINAL existed, what edge case it handled, and what would break if you removed it. The new slop has an approver. Different relationship entirely.

Arvid’s right that devs wrote bad code before AI. The part he’s missing: the entire quality infrastructure of software engineering was designed around a world where the author and the debugger were the same person. That world ended last year and nothing has replaced it yet.

[Piotr Tobiasz @ttyobiwan]

@willmcgugan list out the things you want to see and do. think how much time you need for each location. plan 1-2 things for each day. go out for breakfasts and dinners. tbh, rest will figure itself out.

[Piotr Tobiasz @ttyobiwan]

@karpathy @lauriewired peak delusions. this is the greatest authority in the ai hype bros world?

[Piotr Tobiasz @ttyobiwan]

@willmcgugan ban immediately. it is author's responsibility to make sure pr is ready to be submitted. all these ai slop prs that are flooding oss is just pure lack of respect to maintainers' time.

[dax @thdxr]

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code

here's what things actually look like

- your org rarely has good ideas. ideas being expensive to implement was actually helping

- majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life

- they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend

- the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon

- even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real

- your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills