ping

Hot take, if you are unwilling to approve rm you should rethink your workflow, git state, or backups. !!! Note This is meant for normal project work with an agent working in the context of a single project, with directory level access to the project.

I'm regressing back to boomer ai for more plan mode style prompting at home... It does a decent job at ingesting a repo and coming up with plans before I start spending precious tokens.

Not sure if this is simply the flavor of the month, or a shift in gpt5.4 being super subsidized on release and now that we have gpt5.4-mini-fast out they have shifted, but I'm burning through half of my $20 gippity sub in a day with hobby level use. Second week in a row its burning so fast.

Is it just me or are the agents not behaving today?

I wrote code by hand today... I was out of tokens

Ask your agents to prove their work. Include it in the initial prompt, not later.

What's going to happen to all of our software when Anthropic Mythos finds all of the 0 day vulnerabilities? Will everything depending on the bugs break? Will it be possible to fix them cleanly? Will we all get pwnd when the bad actors get access to them before everything is patched? Will LTS Operating Systems Die?

The job of writing code is dying, models are getting better, the average person will have their average features implemented in average ways with no effort by agents, the writing is on the wall. We are still trying to review most of the critical code, this is slowing us down, is it really stopping any bugs or giving us any more familiarity with the product, marginally. The time is now to grease up your UAT, testing, deployment pipelines. Dont let agents delete entire regions. Review your backup and restore strategy, you do have a DR plan right? Things are changing fast, the best of us are still better than the clankers. Most of us have more context than the clankers. Most of us have more intuition of what and where to implement fixes. Context windows and memory will be solved problems. Your DR plan, UAT, testinng and QA environments will not come for free, you need to make them, and deeply integrate them into your processes.

I think I'm starting to understand my role as a platform developer in 2026. * least priveleged access * default deny + explicit allow * understand your blast radius * **GREASED** creds rotate process * PIN EVERYTHING * keep packages up to date * but not too up to date, use dependency cooldowns

Easy anticheat for linux is out. !!! tip look at the date If this were real what would you play first? For me it's `skate .` is really the only thing I care about and I'm fine without it.

Okay so I logged into twitter today, and we are back.... probably not for long, but we are for now. Claude Code source leaked, the tweets are great. [[ thoughts-956 ]], [[ thoughts-958 ]], [[ thoughts-959 ]], Some typescript css text layout with bouncing balls, bubbles, strings, and webcam video to text is blowing up [[ thoughts-957 ]]. This is the tech twitter I remember no sad news how the world is corrupt by the other side.

Social Media is dead, interest media killed it long ago. I no longer feel like I'm connecting to people, creating community, having fun, learning. I feel like I'm being shoveled slop from the slop machine, I'm sure mostly create by well intentioned people just trying to make it in the world, trying to make their mark, trying to make something of themselves. The algos long lost the idea of subs and likes, and transitioned to how long you will pause on a topic. What used to be a series of recognizable faces, names, avatars, each with their own personality that I could come to learn and know who was just trollin, who was serious, is now mostly unrecognizable. Platforms have changed and fractured communities people went separate ways, not all the same ways. No one community is like it used to be, and its hard to find.

Agents suck Get left behind if you don't use them Burn out if you use them too much The software world has been flipped upside down seemingly overnight. Slow at first, then all at once. It started with auto complete, to chat, to, ide integrations, to agents that would f&!^ over your repo more than it would help. Up till this point we are just little bit better and more specific than copy paste from Stack Overflow. Then in Nov 2025 models learned how to effectively use tools and do what you ask of them, sometimes more, sometimes less, but generally for the basic shit most of us make its a net positive with each iteration. Our techniques for managing work need to change. Our expectations need to change. Burnout for a lot of folks is coming.

I saw today in work chat something along the lines of "we need bigger context windows" "compaction times are holding us back". Maybe I'm just blessed with the lack of lord jira, maybe juggle too many projects at once and they are all pretty much done when I get back. Maybe I do more long running specs and spend time making good plans that it does not matter. Anyways the point I'm getting to is that if you think that compaction is your main issue slowing you down, and 10x this if you are a manager thinking this is what is slowing down your team you **need** to look at your workflow. Not because it sucks. Not only because it could be better. Because you are signing yourself and your team up for burnout if you are sitting there watching these things run like waiting for paint to dry and firing more prompts at them as soon as they are done. It feels easy. It feels like you are going fast. Its eating more brainpower than you think, and its not getting you to your destination any faster.

Part of @steveyegge 's gastown/beads is a prompt "Lets land the plane". It's very straightforward forward and what any sane human would probably do before finishing work, except the last part. The "generate a handoff prompt for the next session" was not something I've put much thought into. But now that I juggle 6 sessions at a time and often end up with 20 sessions open because I don't want to close them and loose the last bit of context. This is what I need to keep from crippling my laptop memory from all of these stale sessions hanging around.  Taken from https://ianbull.com/posts/beads

I don't want to review the pr, I dont want to fight the mass of changes clobbered across the codebase. I want to own my platform. With everything changing with agents writing more code than I can imagine in a day work looks different now. I still want to work with real people. I want to collaborate on ideas. I want someone to bounce ideas off with. I want someone else in the war room with me on launch day, or when the whole thing goes down. But I don't them slopping in my sandbox, if someone is going to be stirring the slop in my product I want it to be me. Work is feeling different now. New lines need to be drawn in new directions. Expectations are changing, the way work is completed is changing, and we are all here trying to figure out what this looks like moving forward.

When agents do the work its harder to recognize a dead end.

All we are hearing lately is Agents are the future, something flipped around NOV 2025 with opus 4.5. It turned snake oil into action. It changed programmers will be replaced in 6 months to now. Not all of them, but probably most of us who are not extraordinary. If you fall into the camp of folks not adopting, I got no issues with that. No one is twisting your arm, well maybe your boss or cto is, thats on them. I don't mean to say this is the future as in, get in or get left behind. I mean it as this is where your other engineers probably are, the junior to mid level engineers are here. If you are not trying to meet them where they are how are you going to lead them.