Building What You Don't Understand: How to Supercharge System Design with LLMs
Hey, folks! It's been a few weeks since I posted on LinkedIn because I've been coding—a lot. Basically, I've been exploring niche technical domains I don’t understand and designing and programming applications in languages I've never used before. It's been an intoxicating experience. I feel like there isn’t anything I can’t build now. I want to share how I've been pairing with an LLM to improve my coding skills. So, my apologies in advance, greater LinkedIn; here comes another LLM article.
If you haven't tried it yet, I highly recommend pairing with an LLM. Code completion from comments is fantastic, but having an LLM-powered chatbot that understands your entire project and can debate architecture and write perfect code for you is a game-changer. I'm eagerly awaiting Co-pilot X, which promises to be even better.
If you're a programmer at any level, I urge you to challenge yourself by building something simple in a language you've never used before. It's a great way to learn and expand your skills.
Here's how I've been pairing with ChatGPT to write code:
Recommended by LinkedIn
The code that ChatGPT produces is impressive, with minimal errors or omissions. It may miss a few small items, but I rarely have VSCode flag any problems with the code. Depending on how complex the project is, you may run into issues with the generated code, but in the rare case of minor issues, such as missing imports or dependencies, they are usually easily resolved with minor adjustments. Once you run the program, you may find some errors, but feeding those errors back into the chat thread helps ChatGPT gain a better understanding of what you’re building, and if you continue to pair with it, then ChatGPT can continue to help.
I am excited about Copilot X but ecstatic if ChatGPT turns into a platform play. A competitive ecosystem of ChatGPT-powered developer tools will supercharge the cognitive abilities of programmers. If you code, I urge you to pick something interesting you don’t understand and get out and build!
CIO at Evergreen Nephrology
1yIntellectual property discussions are going to get interesting.