▲ | bonzini 2 days ago | |||||||||||||||||||||||||
The techniques he has in the post are mostly "model your problem as a data flow graph and follow it". If you skip the modeling part and rely on something that you don't control being good enough, that's faith not engineering. | ||||||||||||||||||||||||||
▲ | ilaksh 2 days ago | parent [-] | |||||||||||||||||||||||||
I didn't say to skip any kind of problem modeling. I just didn't emphasize it. The goal _should_ be to avoid doing traditional software engineering or create a system that requires typical engineering to maintain. Agents with leading edge LLMs allow smart users to have flexible systems that they can evolve by modifying instructions and tools. This requires less technical skill than visual programming. If you are only taking advantage of the LLM to handle a few wrinkles or a little bit of natural language mapping then you aren't really taking advantage of what they can do. Of course you can build systems with rigid workflows and sprinkling of LLM integration, but for most use cases it's probably not the right default mindset for mid-2025. Like I said, I was originally following that approach a little ways back. But things change. Your viewpoint is about a year out of date. | ||||||||||||||||||||||||||
|