GPT-5.6

For me and (likely) for OP as well it is the opposite. Result is meaningless without the process. I can't take fruits of my labor (whichever labor it can be) to the grave, and if you remove the process of growing and picking said fruits, then where is "you" in that? Did you really "achieved" anything? Or whatever you wished for just magically appeared in front of you with little effort from your side?

Where is the fun of renting a helicopter that would carefully put you onto mountain's summit and pick you up 5 minutes later?

At work, it was able to one shot a dashboard. Of course, my prompts are vague as I'm not exactly sure what I want yet, but it did a better job than I could do as a backend dev forced to work on frontend sometimes.

Usage is also great, it just feels so much more efficient than older models in terms of thinking and time. Cost is barely better though.

It can burn a million tokens in less than a minute, at least at launch where there's likely less load on the servers.

At home, it feels like I'm fighting the AI less while letting it refactor code. I'm glad that I left this 12,000 line vibe coded port of a hand written codebase to future models to refactor. It feels like the model has better judgement than old models that would destroy your codebase so long as it meant accomplishing your prompt.

I'm almost disappointed that it's this good.

It has a tendency to do things without asking, a trait I'd associated more with the Claude Opus & Sonnet models than with Codex & GPT in the past. Specifically I've seen it go and update e.g. README.md files filling it with recenty-biased gibberish that means nothing to the user (e.g. very specific technical notes related to what it was currently working on) or staging and adding design/spec documents that were meant to just be working documents. In general it tends to behave more aggressively with git, if you let it get its hands on it. It has stronger "opinions" on that stuff, that don't always agree with me.

I'm going to have to update my prompts, I think. But I'm not used to this kind of thing in Codex, which in the past has been much more explicit and cautious, and one of the reasons I've preferred it over Claude.

It is very "smart." It also has a tendency to yak-shave things. Producing huge volumes of correctness and regression tests and nitting over e.g. very minor variances.

One thing that is "entertaining" is letting two separate instances review each other's code. They will endlessly find things to nit at.

I am working tirelessly and often long nights, on top of a day job.

My effort has shifted to QA testing, reviewing UI designs, and delegating the agents on the implementation.

I will consider it an achievement if I manage to publish a successful app.

Where is the "me" in that? I am guiding the design of every screen and feature the way I would like it to be.

On top of that I make technical decisions on how it is implemented.

Apart from the loads of QA work I will have to handle the business side as well.

As of now it's hardly as trivial and effortless as some make it out to be.

Yes, I no longer write the code, and sometimes it feels frustrating that any teenager without experience could perhaps build a similarly good app soon.

Overall I'm still happy I can now build much larger and better apps and realistically publish them in my free time, for a chance to make serious money.