gosolozero

First flash model with multimodal support? I think Flash series might be the main focus going forward for them. Tried it out and it’s better than v4 pro

2 articles on how G 5.3 is the best in the top 10? Seems like a bit of astroturfing going on

I’m not sure I get the value over Obsidian, can you explain the static file issue? Only happens at 7K+ individual files? What happens if you always conjoin files?

I think LLMs are actually great at breaking up work into workstreams and tasks. The issue is that tasks do not equal good PR stacks on their own. You’ll need to use feature slices instead (like do backend part -> PR it, etc). LLMs can do that, but you need to harness them into it.

I agree it’s a great step. But the deepseek models also don’t perform to the same level of fable/sol. If we optimize/finetune to deepseek traces, wouldn’t it be suboptimal? What would the benefit be?

I thought Caveman was debunked in the token saving argument? In real sessions it doesn’t really save much longterm and made sessions more forgetful/take longer.

I think we might underestimate the evolution of these tools as AI gets both better and cheaper. The current form factors are like trying to setup a website in early 90s, cumbersome and not user friendly. Coding infra, AI coding UI, etc are not solved problems yet. If things progress, I think there will be a time when a whole app can be developed and deployed with a single prompt. In that kind of world, who can’t write code?

I'm talking from the perspective of working in big tech. Working in a fast paced startup, percentages are definitely different. But alignment/deciding where to spend resources is more important than coding especially the higher you go, the more resources at your disposal (staff+ eng). Junior eng again different percentages.

Interesting prompt to world pipeline. I wonder if there can be more style applied than just the "MMO cartoony" style? Like medieval Witcher or realistic Cyberpunk buildings?

Yes, I resonate with this and the article above.

I think 80% of a SWE's job is to communicate with the XFN partners (either gathering requirements, pushing back, managing up, collaborations, etc) and then plan out the actual coding (gather code pointers, look at past code, plan architecture, talk to the team). The last 10% is the coding. And then the other 10% is the maintenance of that and past code (which honestly should be a lot more but incentives are not aligned well).

It's hard for people to understand jobs they don't do. They imagine we spend 8 hours a day clacking at the keyboard.