Thats gfy. The article is not about specific models if not about how the way to work is changing, from coding to mostly review llm code, dev cycles being reduced, expectations being higher and burn out due problem switching and multitasking. Which for me is something i was realizing since some time ago, but the author put it in to words. Im not 100% about what he said, but i mostly feel the same. The solution im experimenting with is basically to know when to stop, go out, touch grass