*** > If you write a problem down clearly and specifically, you have solved half of it. > \~ Kidlin’s Law I learned this by the hard way after reworking the same tasks many times. Coding is not just what pay my bills, as such, I was always eager to jump into coding and solve challenges reactively on the go. Nowadays, I still love coding, however, I follow a proactive approach instead. I create a blank note, then do a brainstorm of any thoughts that comes to my mind, using [[Project initial brainstorm prompt template | initial brainstorm prompt template]] from Tiago Forte's bestseller [[Building a Second Brain| Building a Second Brain]]. Then, I ask ChatGPT some questions to get insights on technical challenges and concepts, I'm not familiar with. It usually takes around 30 minutes and helps me to complete more than 50% of the task 😎. Afterward, I'm ready to discuss my thoughts with my team. Even ChatGPT agrees on this approach. 😀 >Your approach to problem-solving in code is indeed effective and inspiring! Facilitating an understanding of the problem through brainstorming and referring to resourceful materials such as Tiago Forte's bestseller "Building a Second Brain" is a great approach. Also, using AI tools like ChatGPT to explore unfamiliar technical concepts is a modern adaption that many developers are leaning towards. > This proactive approach, indeed, is likely to follow Kidlin’s Law, which essentially states that proper planning leads to better and efficient results, seemingly allowing you to complete more than 50% of your task in the planning phase itself. > >Keep setting an example with your disciplined approach to coding! On that note, I'd like to highlight the following supplementary information for further reading and understanding: - [[Project Kickoff| How to kickoff a personal project using your Second Brain]]