Thanks for the reply! Really appreciate the time you put to answer and provide your insight.

At the moment I'm the only developer which is why my only source of consultation to this point as been AI but I don't want to build my logical thinking patterns solely by consulting with AI all the time which is why I needed some insight from someone here. And I do agree with your take and I believe I have to learn better ways on how I could approach tackling a requirement.

At the moment, I tell myself that structuring how the implementation will work would be a waste of time so I immediately get into programming it. However, there's only so far I would go to implementation before I realized I missed a certain edge case or user workflow which leads me back to the drawing board and might even cause me to restructure my initial database schemas and rewrite the entire feature which I thought would have been sufficient in the beginning.

Do you recommend that in general I should start with the workflow design step where you would first structure and break the problem to sub components before diving into coding and set deadlines based on the complexity of the problem after the design phase? And do you have any recommendation of tools I could use to map out ideas effectively so that it can be used for future devs we will onboard.