@ciengalon@sflorimm it was clear by late Feb that gpt-5.3-codex was a more reliable coding agent than opus.
the type of shortcuts opus 4.5/4.6 took were just infuriating. haven't touched it since then.
whatever it is that you are doing, not the day to day stuff but the multi-decade north star, never forget why you chose that path because everything else is secondary
planning to start sharing long-form articles of what i am learning. draft now; artcle coming soon.
i used to be obsessed with TDD before coding agents forced everyone to start writing tests
recently discovered an effective way to TDD model-facing code (non-deterministic etc).
Sol seems proactive in a way I haven't seen with the prior models.
When there is enough information to change course, it's fast and doesn't waste time.
Judgement is not perfect but baby steps
the biggest difference between gpt 5.5 and gpt 5.6 sol seems to be that the latter is more strategic and really good and creating tools and infra for achieving the final goals
Working on a project that takes an input through 8 model calls, each taking the output of the previous (after some transformations)
Accidentally landed on one-model-call "harness" that allows to run experiments on one step and getting stable results before integrating into the whole pipeline
Coding agents are so good with this setup that the quality and pace of work became ~3X all of a sudden
Not sure if it applies to all projects but it's a big unlock where applicable
@mattzcarey@RhysSullivan@zeeg maybe a clearer framing is
"with MCP, as a business, you don't own or see the full 'question to answer ' user journey. In essence, you have been disintermediated from your own users/customers."
that's the part I'm unsure everyone understands and the full implications