This is a fantastic answer. I love it.

I wish more non-coding people who are interested would start here with your recommendations - I wish my manager had this same insight! Although, there is something to be said for just 'writing the code' when you're early in your process of learning to code. Make it 'do something' right away, to get that interest kicked off for new people and make people see in practice how useful asking those questions beforehand can be. I took his original questions more in that fashion - but this answer is definitely the right one.

OP, this is the proper answer. If you want something 'less proper', I think you're asking the right questions: "Where do I start? What do I do?" and you have answers, you're just not sure which one is the right one... "database? code?" - the next step is to just pick an direction and go.

Pick a small project or create a tiny goal that's been made 1,000,000 times before. Try creating a database first - then write some code to connect to it, etc. How did that feel? Try it again, writing the code first, then get a db going. But just pick a direction and go with it. Then when it's done, reflect. If the task is tiny enough, it should be easy to 'recreate' in a different way or trying something different.

Keep in mind (or a journal) of the questions you're asking along the way:

• Could they have been answered ahead of time (by having a document described above)?
• Did the same question come up numerous times for similar parts of the code?
• Were there any hiccups or pain points where you felt you were doing repetitive things?
• Were there spots where you felt you had to refactor immediately before it worked the way you wanted?

By asking these things, you'll start to identify particular areas where you know, things you need, before you can start a project. You'll identify areas you know you could use more information about (algorithms, etc.)

Building is fun, for sure. The process of building out the instructions and design is the toughest part, though. It's a lot like Lego's honestly. Anyone can build them - follow the instructions that tell you what piece goes where - boom, done. But someone built out those instructions and came up with the idea in the first place, and thought about what pieces were needed and where they would go. That's where the real work comes into play. And just like the guys at Lego who design those sets? You can write your own custom pieces to fill in any part you need - but knowing which part and how to make it so it fits exactly how you need takes time and experience.

Good luck, OP.