alittletooraph2

Either become a platform or get swallowed up by one (e.g. Cursor acquiring Graphite to become more of a platform). Trying to prove out that your code review agent is marginally better than others when the capability is being included in every single solution is a losing strategy. They can just give the capability away for free. Also, the idea that code review will scale dramatically in importance as more code is written by agents is not new.

lol no they're not

ngl that felt like reading a lot of fluff

"If the founder/CEO and best engineers at Windsurf don't believe in that product/company, why should you?"

^ Any company that competes with them could say that and it would create some pause.

I know it'll probably get better over time but it's pretty awful compared to what you can do with v0 right now.

you know how the endorsements work right? some comms intern writes a quote, emails it to someone at the other companies for the go ahead/approval, and that's how you get dozens of companies all spouting BS that kinda sounds the same.

agents are just the rebranded version of automated workflows and sometimes its an LLM doing the validation

I tried to make Studio Ghibli inspired images using presumably their new models. It was ass.

This feels like an MWAA issue but I understand how that often gets conflated with it being an Airflow issue.

Temporal’s great! That being said, there is something about being able to orchestrate LLMs and agents using what many already use to orchestrate their data workflows because there’s already proven out reliability, scalability, observability, etc. I’m sure there are boundary conditions for really advanced agentic workflows though…

i worked at MongoDB for nearly 10 years... when the heck did they have booth babes at conferences?

b/c you don't want the management or learning curve overhead of a separate database for vectors than the one you're already using for transactions or metadata