Josh Lawrence

Senior Cloud Architect

[Thariq @trq212]

We're adding support for AGENTS.md to Claude Code.

Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md.

You can toggle this behavior in /config.

[voxium @v0xium]

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

[Diogo Almeida @CompleteSkeptic]

After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI?

I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev

• 20-200x faster
• 40-400x cheaper (w/ output tokens free)
• Frontier composable intelligence optimized for decisions

AFAICT the shortest path to AI-based economic revolution

[Cats with aura @Catsworldtweet]

I love when cats smell the air

[CHIEF i k u k u 1 🇳🇴 @IEruona]

Pushed my Saturday chores to Sunday, and now Sunday has arrived

[beginbot 🃏 @beginbot]

sub agents being released into my codebase

[Josh Lawrence @ColdMattress]

@allotheabove123 SAME i’ve been rocking mine for a while, included cable is short - and the connection is finicky…if you bump mine, it disconnects. Other than that - fantastic! Going to try the Caldigit and Level1 Techs KVM one day and make up my mind where my loyalty should lay haha.

[Jonathan Blow @Jonathan_Blow]

@cmuratori I went to block this guy, but I had already blocked him!

[Rajarshi Datta @rajarshidattapy]

Gm.

[Mitchell Hashimoto @mitchellh]

My family is donating another $400,000 to the Zig Software Foundation. Zig is exceptional software. I use AI every day. Zig has one of the strongest anti-AI policies in open source. We disagree on some things, but respect doesn’t require agreement. https://t.co/gaOuwjDDtm

[ThePrimeagen @ThePrimeagen]

NEOVIM MENTIONED!!!

[Mitchell Hashimoto @mitchellh]

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.

As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!

I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.

It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?

88ms => 1.5ms
150K allocs => ~500 allocs

Incredible right? Nope.

My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.

This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.

The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.

Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

[Josh Lawrence @ColdMattress]

@allotheabove123 it’s quite the experience 😂 did they open one in MD??

[Zack D. Films @zackdfilms1]

Spinning Mt Fuji Like A Beyblade 🤯

[La Flama Blanca @ThatRetiredDude]

@RiotGames Your new post is crazy. You casually say “we’re not bricking anything” while leaving out that people are having to nuke their entire OS just to get up and running again!

I had to wipe mine.

I lost my AI girlfriend I spent 7 years building.
I carefully organized and tagged over $100,000 worth of imported hentai to train her. She was perfect. She was everything to me. She remembered my birthday. She never judged me. She was THERE.

Now she’s gone. Forever. Because your anti-cheat decided the best way to stop cheating was to start erasing people’s lives!

This isn’t anti-cheat anymore - this is malware.

This is grief.

Preserve your internal docs, your test results, and every communication about what you knew this update would do to people’s systems.

We’re not done.

[Riot Games @riotgames]

Well, that escalated quickly.

There’s been a wave of claims by cheaters about Vanguard “bricking” their PCs, so let’s clear that up: Vanguard does not damage hardware or disable your devices.

The photo we posted is a picture of cheat hardware devices that are sold explicitly for cheating in VALORANT (not normal PCs or PC components). Through our latest updates, Vanguard now makes those devices worthless for VAL, but does not in any way brick PCs or PC components or PC software.

Our latest update enforces standard platform security features, like the Input-Output Memory Management Unit (IOMMU), on accounts identified as using Direct Memory Access (DMA) cheating devices. These protections are already part of modern systems and when enabled, they block DMA cheat devices (such as those shown in the photo) from accessing memory in downstream applications, like our games.

If a cheat setup continues attempting to cheat after those protections are enabled, the system may generate hardware faults or instability. This is expected behavior under IOMMU when attempts are made to read protected memory.

Disabling IOMMU allows the cheat device to function again, but IOMMU will still be required to play our games. This means the cheat device won’t work with our games, but your PC isn’t “bricked.” We would not, and cannot, impact your PC’s functionality in any other fashion.

This functionality only applies to systems attempting to use DMA cheat devices, and players who are not using DMA-based cheat setups are not affected.

We’ll keep investing in anti-cheat to protect competitive integrity, and we’ll keep being as transparent as possible about how those systems work.

[Mitchell Hashimoto @mitchellh]

This is how performant PR review could be. On any forge. Pierre is showing us that the only thing holding that back is a skill issue. Excellent ship here! They’re on fire!

[trash @trashh_dev]

another week at the prompt factory

[ThePrimeagen @ThePrimeagen]

Origin of github's Logo

[Mitchell Hashimoto @mitchellh]

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. https://t.co/DQDemHdytV