|
|
|
|
|
|
by vunderba
2 days ago
|
|
|
None of that is necessary. It’s like people who install Obsidian and then spend weeks obsessing over the “top ten must-have plugins” for the ecosystem instead of just using it as it’s intended: as a tool to take notes. The purpose of a coding LLM is basically to assist with building something. So start with an actual concrete goal: something you want to build. Maybe even take a past project and try to recreate it, but this time using an LLM-augmented workflow. Don’t get bogged down in a bunch of orchestration/MCP/skills/etc. - keep it simple and expand as you go. The best thing you can do is actually use these tools to help you develop an intuitive sense of their strengths and weaknesses. You don’t need to watch videos or tutorials. Grab something a basic agent harness like oh-my-pi [1], throw $30–50 on OpenRouter, and start playing with it. [1] - https://github.com/can1357/oh-my-pi |
|
|