Marc Morente @ethnerom

Yes. AI agents work best with clean code. That is a given. Either you know how to do it, or you will suffer (and pay way way more tokens than you should for suboptimal results, and you will think it's a matter of changing LLMs) Full explanation on Clean Code for AI: akitaonrails.com/en/2026/04/20/…

Uncle Bob Martin @unclebobmartin

2 days ago

@poteto Messy code slows agents down, just like it slows humans down. I've seen agents struggle over maintaining messy code, where every change they make breaks something else they hadn't anticipated. They can thrash for some time trying to deal with it. So I think all the same

19 24 354 47K 124

@dhh I prefer hunk.dev for the diffs

Experience gives perspective. Programming is not dead, and never will be. It's late September 2026. Sometime in September 1976, just after I entered college, I wrote and ran my first serious program. I have now been a programmer for literally 50 years. And man, I have seen it *all*. Punched cards to glass ttys on minicomputers to workstations to the earliest micros. I've written business software, communication programs, development tools, games, language implementations, kernel device drivers, graphics libraries, a few critical pieces of infrastructure, and all manner of odd programs for which there is no taxonomy. Coded in a score of languages some of which are now forgotten. I've run over 70 open-source projects and contributed to at least as many more. Along the way I noticed a few things, and wrote about them, and that made me famous. But I'm not here to write about that today. I'm here to write about what it means to be a programmer and a technologist with the Singularity upon us. I have lost count of the number of times I have been told "programming is over". You kids may think this is a new claim that came into the world with LLMs. Hah! There's been that kind of talk at every step function in the quality of our programming tools. I first heard it when compilers were replacing hand-hacked assembler in the early 1980s, and I wouldn't be a bit surprised if somebody said it earlier when in-memory code replaced plugboards. One constant amidst all this change is that the intentions in a user's head do not magically turn into executable instructions that a computer can run. Another constant is the mindset of the people who specialize in bridging the gap between wish and algorithm. A programmer is a programmer is a programmer - the tools are secondary. "But it's different this time!" some people will say, "AIs are superhuman now!" So? What did you think the optimization stage of a compiler was, chopped liver? We've been relying on tools that exceeded human capabilities all along - we built them precisely because our meatbrains could not otherwise keep up with the demands of the job. It's been a hell of a ride, that 50 years. I've succeeded and failed and succeeded again. Done a lot of work I'm proud of. Built at least a few things that look like they're going to last. None of that goes away because, hypothetically, an AI might have made me faster. The work is never done, even if the tools can talk to us now. Because intentions still have to be communicated; people who specialize in that and develop right mindset to do it still have a major advantage over people who don't. If you're feeling depressed because you spent years or decades developing hand-coding skills that are obsolete now? Buck up. You still have the most important asset - a mind that knows how to think that way. I'm facing the winds of the Singularity with a smile. Because 50 years and I'm still standing - still shipping code that people can use, still learning, still refusing to be paralyzed by the pace of change. The best therapy for your uncertainty? Get to work on something.

There's nothing kind about letting good people live in a fantasy world that no longer exists. You have to tell them, even if it hurts. Because the sooner they accept reality, the sooner they can adapt to the future.

The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.

Periodic sadness reminder that the anthropic subscription still does not permit third party harnesses :(

Your job may be surviving on inertia. Your resentment won’t extend the runway. What do you actually want to do with the intelligence now at your disposal? x.com/i/article/2101…

💥炸了！开源本地版 Laya 响应速度吊打 Jev ，毫秒级决策快到飞起！ 左边 Laya 是本地 421M 开源决策模型，右边 Jev 1.13.0 是云端 API。 同一盘贪吃蛇、同一套 typed decision，30 秒自由跑下来： 🔹Laya：分数 46、长度 52，决策 86.5 次/秒，P50 约 9ms 🔸Jev：分数 1、长度 7，决策 3.2 次/秒，API 往返 317ms M5 Pro 实测中位耗时：本地 15.3ms vs 云端 298.1ms，接近 20 倍 Laya 推理内存大约 1GB，毫秒级决策，不靠网络 而云端 Jev 每一步都在等往返，本地每一步都在当场拍板！ GitHub：github.com/NandhaKishorM/… #开源Jev #Laya #本地部署 #SystemOne #贪吃蛇对战AI #Jev x.com/nft_chen/statu…

SuSu_酥酥👅 @NFT_Chen

3 weeks ago

🔥速码！谁的 Codex 还没装上 Jev 批量必杀技？这波真能起飞 ！ Jev 不写长文、不瞎规划，专门干一件事：选择、分类、打分。Agent 给上下文、自己干活。大规模数据清洗、自循环分类、长程任务里替你拍板，比把 Codex / Claude 当 judge 更便宜、更快、更能并发。 亮点先看： 🔹开源 9 个技能 + 90

keyboard_arrow_left Previous keyboard_arrow_right Next

23 118 643 542K 976

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.

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.

A crucial skill when developing with AI is to know which "bugs" to tackle or ignore. Because AI models will *always* find "bugs". You can run 10 cycles of code reviews, they will still find something. That includes false positives BUT also *a lot* of esoteric, niche issues that will likely never matter for what you're building. For example, I find that Astra loves to find weird pretty made up racing conditions like "if you bulk import emails and after the first 10 records were written, an email address changes, it will silently overwrite it". Stuff like that. Which may never matter for what you're building. If you just let AI review + blindly accept its findings and let it fix those findings, you'll just start adding layers of complexity and turn your codebase into a mess. Don't let that happen. Use your brain, use your understanding of what you're building - don't outsource your thinking.

@FaztTech justfuckinguseneovim.com

New blog post: Farewell, programming. staltz.com/farewell-progr…

I can’t stress enough how little an idea matters compared to the agency of the people executing the idea. I have had the privilege of knowing and sometimes even working with some of the most successful people (by various metrics). The difference between mediocre and excellent work and outcomes is predominantly one of agency. In practice this means: they dont wait for things to happen to them they go out and make things happen for them. They don’t wait for someone else to do something, for someone to teach them, for someone to give them the path, etc. They just go out and find a way to do it. I think the single biggest superpower these people have is the realization/belief that the world around them is completely mutable. Most everything that happens is because a person made it happen. I used to tell people to look around the room you’re sitting in. Look at everything. Every noun. It almost all exists because a person willed it into existence. Nothing is stopping you from doing the same. I see people online all the time dismissing someone else’s success because “I had that idea first” or whatever. I mean… yeah? If so then the difference is… you. So a bit of a self own whenever I hear that. Number one tip: act with agency.

La IA se hace cada día más lista y los niños salen cada día más tontos. ¿Qué podría salir mal? 😅

OpenAI @OpenAI

a month ago

We’re sharing a solution to the Navier-Stokes Millennium Prize Problem, one of the deepest problems at the frontier of mathematics. The proof was produced by a group of agents, using an OpenAI next-generation model significantly more capable than GPT-6 Astra. The problem

6K 20K 120K 75.2M 31K

Before ponytail skill / After ponytail skill It's crazy how much prompt engineering still helps

keyboard_arrow_left Previous keyboard_arrow_right Next

working on a 500LOC module. every change claude makes to it results in a metric ton of footguns. i don't usually get to see the code in this UI, so this like a shitty dark factory way of working. coding is solved.

@jellydn you gotta read (parts of) the code. you gotta be in charge of types and interfaces. you got to refactor mercilessly to unfuck all the vibeslop.

Don't be a Meat Proxy. Have strong opinions about architecture, design, reliability, yet stay open minded and research quickly. Argue with people, reframe with machines, provide actionable comments. And most importantly, take responsibility & ownership of your work. Otherwise LLMs have already successfully replaced you.

Abhi Aiyer @abhiaiyer

2 months ago

113 940 9K 772K 2K