451–460 of 657 posts
It makes my work suck, sadly. Team dynamics also contributes to that, admittedly. Last year I was working on implementing a pretty big feature in our codebase, it required a lot of focus to get the business logic right and at the same time you had be very creative to make this feasible to run without hogging to much resources. When I was nearly done and worked on catching bugs, team members grew tired of waiting and…
Earlier quoted context omitted.
If you dont take a stand and refuse to clean their mess, aren't you part of the problem? No self respecting proponent of AI enabled development should suggest that the engineers generating the code are still not personally responsible for its quality.
Ultimately that's only an option if you can sustain the impact to your career (not getting promoted, or getting fired). My org (publicly traded, household name, People who disagree at all levels of seniority have been made to leave the organization. Practically speaking, there's no sexy pitch you can make about doing quality grunt work. I've made that mistake virtually every time I've joined a company: I make perform…
> People who disagree at all levels of seniority have been made to leave the organization.
So either they're right (100% AI-generated code soon) and you'll be out of a job or they'll be wrong, but by then the smart people will have been gone for a while. Do you see a third future where next year you'll still have a job and the company will still have a future?
I'm a manager at a large consumer website. My team and I have built a harness that uses headless Claude's (running Opus) to do ticket work, respond to and fix PR comments, and fix CI test failures. Our only interaction with code is writing specs in Jira tickets (which we primarily do via local Claudes) and adding PR comments to GitHub PRs. The speed we can move at is astounding. We're going to finish our backlog next…
When is your website going to be complete? Are you sure those features are what the users need? What happens to the team after everything is done? What happens to the site after the team is gone?
Amen.
- Figuring out the architecture of a project you just came into
- Tracing the root cause of a bug
- Quickly implementing a solution with known architecture
I figured out that above all, what makes or breaks success is context engineering. Keeping your project and session documentation in order, documenting every learning you've made along the way (with the help of AI), asking AI to compose a plan before implementing it, iterating on a plan before it looks good to you. Sometimes I spend several hours on a plan markdown document, iterating on it with AI, before pressing "Build" button and the AI doing it in 10 minutes.
Another important thing is verification harness. Tell the agent how to compile the code, run the tests - that way it's less likely to go off the rails.
Overall, since couple of month ago, I feel like I got rid of the part of programming that I liked the least - swimming in technicalities irrelevant for the overall project's objectives - while keeping what I liked the most - making the actual architectural and business decisions.
I wrote a blog recently about the approach that works for me: https://anatoliikmt.me/posts/2026-03-02-ai-dev-flow/
And this is a tool for context engineering I made specifically to support such a flow: https://ctxlayer.dev/
Earlier quoted context omitted.
I saw somewhere that you guys had All Hands where juniors were prohibited from pushing AI-assisted code due to some reliability thing going on? Was that just a hoax?
https://www.aboutamazon.com/news/company-news/amazon-outage-... About All Hands : > Much of the coverage of the service incidents has focused on a weekly Amazon Stores operations meeting and a planned discussion of recent outages. Reviewing operational incidents is a routine part of these meetings, during which teams discuss root causes with the goal of continuing to improve reliability for customers. This is somethi…
I run a small game studio. I use Cursor to write features that I don’t want to hand code, but wouldn’t ask a teammate to do. Usually that is because describing the idea to a person would take about as much effort and the result would take longer. These are usually internal tools, workflow improvements, and one off features. Anything really central to the game’s code gets human coded. I think the further you are from…
Stack is a monolith SaaS dashboard in Vue / Typescript on the frontend, Node.js on the backend, first built in 2019, with something like 5 different frontend state management technologies. Everyone is senior level.
We use Cursor and Opus 4.6 mainly, and are trying to figure out a more agentic process so we can work on multiple tasks in parallel. Right now we are still mainly prompting.
Earlier quoted context omitted.
The spec needs to be explicit about edge and corner cases.
At some point such a spec converges to the actual code you’d have written.
The majority of code I've written since November 2025 has been created using agents, as opposed to me typing code into a text editor. More than half of that has been done from my iPhone via Claude Code for web (bad name, great software.) I'm enjoying myself so much . Projects I've been thinking about for years are now a couple of hours of hacking around. I'm readjusting my mental model of what's possible as a single…
Are you saying you're learning go because you've freed up time elsewhere or is AI helping?
Earlier quoted context omitted.
That's a nice example, can you explain your 'one shot' setup in some more detail?
I don't have the prompt, but I used codex. I probably wrote a medium sized paragraph explaining the architecture. It scaffolded out the app, and I think I prompted it twice more with some very small bugfixes. That got me to an MVP which I used to build LaTeX pipelines. Since then, I've added a few features out as I've dogfooded it. It's a bit challenging / frustrating to get LLMs to build out a framework/library and…
I think your prompts are 'the source' in a traditional sense, and the result of those prompts is almost like 'object code'. It would be great to have a higher level view of computer source code like the one you are sketching but then to distribute the prompt and the AI (toolchain...) to create the code with and the code itself as just one of many representations. This would also solve some of the copyright issues, as well as possibly some of the longer term maintainability challenges because if you need to make changes to the running system in a while then the tool that got you there may no longer be suitable unless there is a way to ingest all of the code it produced previously and then to suggest surgical strikes instead of wholesale updates.
Thank you for taking the time to write this all out, it is most enlightening. It's a fine line between 'nay sayer' and 'fanboi' and I think you've found the right balance.