> Now, the competitive edge is back on, except this time, its about how to use LLMs. Contrary to popular belief, LLMs take skill to use, not everyone can vibe c

> Now, the competitive edge is back on, except this time, its about how to use LLMs. Contrary to popular belief, LLMs take skill to use, not everyone can vibe code services into production. Prompt engineering is very real. To get LLMs output good quality code you have to guide them quite a bit. If you don't have a set of personal prompts you use to get LLMs to do stuff, you are behind. I dunno man/woman/etc, it seems much more like a context management problem than a prompt issue. Like even with the best prompt in the world, LLMs just make stuff up if they don't have access to better information (tools, RAG etc). I wouldn't say that I have great prompting skills, but I'm pretty handy with context management and that seems to be working. LLMs are so weird though, like I asked Claude Code to tell me about code in a directory, and it did what I asked for but seemed to get less and less interested as the results went on (rather like a human might). And then it gave me some recommendations/overview that were just garbage, so it's really tricky to know how to debug this stuff and make them better. Whatevs, my org just want us to use it so I guess I'll just build some stuff and we can figure out how to make it actually good later. (/end rant).