| ▲ | adriand 4 hours ago | |||||||
I think the multitasking problem will become a thing of the past when (or “if”) the models get much faster. I would absolutely love to just work on one thing at a time with a super fast model. In the earlier days when they were slower and their code was worse so you had to review it, I’d watch the model code and just noodle away on guitar while it did its thing, interrupting it from time to time. Now they’re too fast for that to work, but still too slow for it not to be worth it to start a new task. It’s an awkward in-between stage. If Anthropic made fast mode four or five times faster rather than just twice as fast, I’d probably shell out for it sometimes just to be able to single-task productively. | ||||||||
| ▲ | layoric 4 hours ago | parent | next [-] | |||||||
If call centres are anything to go by, it will be penalized to work on a single thing at once. The longer your workplace can resist measurements related to agents, the more sane the workplace will remain IMO, otherwise, it will turn into what happened to call centres around the 2000s. Measure everything down to the second, and introduce expectations that you will need to spend time justifying if you miss them. | ||||||||
| ▲ | flexagoon 3 hours ago | parent | prev | next [-] | |||||||
I main Deepseek Flash and the biggest bottleneck often isn't the model itself, its external stuff like compilation, testing things, making requests, running linters | ||||||||
| ||||||||
| ▲ | kamyarg 3 hours ago | parent | prev [-] | |||||||
The bottleneck is not only the model latency, Although it would help. When you compile an ios app, or wait for some query result, search slack or wait for Github CI to finish, it all introduces significant wait between agent turns. Models getting faster would help but would not eliminate the problem. | ||||||||