|
|
|
|
|
by mythz
185 days ago
|
|
I like learning, I like programming, primarily because it lets me create whatever App I want. I'm continually choosing the most productive languages, IDEs and tooling that lets me be the most productive. I view AI in the same regard, where it lets me achieve whatever I want to create, but much faster. Sure if you want to learn programming languages for programming sake, then yeah don't Vibe Code (i.e. text prompting AI to code), use AI as a knowledgeable companion that's readily on hand to help you whenever you get stuck. But if your goal is to create Software that achieves your objectives then you're doing yourself a disservice if you're not using AI to its maximum potential. Given my time on this earth is finite, I'm in the camp of using AI to be as productive as possible. But that's still not everything yet, I'm not using it for backend code as I need to verify every change. But more than happy to Vibe code UIs (after I spend time laying down a foundation to make it intuitive where new components/pages go and API integration). Other than that I'll use AI where I can (UIs, automation & deployment scripts, etc), I've even switched over to using React/Next.js for new Apps because AI is more proficient with it. Even old Apps that I wouldn't normally touch because it used legacy tech that's deprecated, I'll just rewrite the entire UI in React/Next.js to get it to a place where I can use text prompts to add new features. It took about ~20mins for Claude Code to get the initial rewrite implemented (using the old code base as a guide) then a few hours over that to walk through every feature and prompt it to add features it missed or fix broken functionality [1]. I ended up spending more time migrating it from AWS/ECS/RDS to Hetzner w/ automated backups - then the actual rewrite. [1] https://react-templates.net/docs/vibe-coding/rewrite-legacy-... |
|