TL; DR:
- Better code does not guarantee efficiency
- Review loops need stopping conditions
- Scope control still belongs to you
- YouTube would not let me schedule a stream so... no stream 😦
GPT-5.6 Sol Impressed Me -- Then It Wouldn't Stop
One of the weirdest parts of using a stronger coding model is that the failures can start looking useful.
I had been using the Opus models pretty heavily, especially because the large context window was genuinely impressive. Then I switched back to a GPT model with GPT-5.6 Sol, and my first reaction was basically: holy crap, this thing is good.
I have written before about how different models can change the shape of a Copilot workflow. This was one of the clearest examples I have felt in practice. Sol was not just producing code I liked. It was noticing things around the requested work that other models had missed.
That sounds great, right?
This content is only available for members.
Become a Member
Or subscribe to the free Dev Leader Weekly newsletter for C#, .NET, and software engineering content every Saturday.