Licensed civil engineer turned full stack developer building accessible, responsive web applications. I also review code in Frontend Mentor and participate in collaborative projects.
Personally, I don't want to use AI-generated code entirely especially if I don't understand what the code is all about. I don't like adding a line of code that I can't explain myself (I feel like I'm just lying to myself and I hate liers). But I always take advantage of the super advanced search feature of AI whenever I have questions and I kinda liked that. But I still have to double check it myself for best practices and officials docs just to be sure. My process is slow but I 100% assure you, it is genuine learning.
For my workflow, I always have a "discussion" first with the AI so that context building is not forced such as creating TASKS.md or SPEC.md. The point is to be conversational and that naturally builds up what I want to do with my project. Sometimes the AI gives good points, some bad ones, it's like taking tradeoffs one after another in a meeting.
Once I have the features listed, I move forward to building them one by one, and the pattern revolves again. I get to learn and upskill slowly but consistently. It worked for me and at the same time it boosted my communication skills, so two birds with one stone.
I'm a frontend developer who loves turning curious ideas into products and sharing the journey behind them. I write about React, AI, product thinking, and everything I learn while building.
Lovely explanation, Elmar. I'm truly honoured to have read such a beautiful comment. The way you have explained your workflow and how you are using AI to your own advantages shows how good of a developer you are.
Rome wasn't built in a day. Your progress feels the same, it's slow and burning but ultimately it is providing you the utmost features and making you a better developer by doing everything in your hands and taking the control from AI and just using it as an observer to help you find mistakes and get better. Congrats on killing two birds with one stone, being a better developer and getting good at communication. This shows how dedicated you are to this field. I hope and pray for your success even more. Hope you become the best of the best.
Licensed civil engineer turned full stack developer building accessible, responsive web applications. I also review code in Frontend Mentor and participate in collaborative projects.
Personally, I don't want to use AI-generated code entirely especially if I don't understand what the code is all about. I don't like adding a line of code that I can't explain myself (I feel like I'm just lying to myself and I hate liers). But I always take advantage of the super advanced search feature of AI whenever I have questions and I kinda liked that. But I still have to double check it myself for best practices and officials docs just to be sure. My process is slow but I 100% assure you, it is genuine learning.
For my workflow, I always have a "discussion" first with the AI so that context building is not forced such as creating
TASKS.mdorSPEC.md. The point is to be conversational and that naturally builds up what I want to do with my project. Sometimes the AI gives good points, some bad ones, it's like taking tradeoffs one after another in a meeting.Once I have the features listed, I move forward to building them one by one, and the pattern revolves again. I get to learn and upskill slowly but consistently. It worked for me and at the same time it boosted my communication skills, so two birds with one stone.
Lovely explanation, Elmar. I'm truly honoured to have read such a beautiful comment. The way you have explained your workflow and how you are using AI to your own advantages shows how good of a developer you are.
Rome wasn't built in a day. Your progress feels the same, it's slow and burning but ultimately it is providing you the utmost features and making you a better developer by doing everything in your hands and taking the control from AI and just using it as an observer to help you find mistakes and get better. Congrats on killing two birds with one stone, being a better developer and getting good at communication. This shows how dedicated you are to this field. I hope and pray for your success even more. Hope you become the best of the best.
Thank you @konark_13. It really means a lot.