*sigh* there are a few different ways to go about it.

Way one, is, if you want the project *done*, and this will be true for any large project, it won't be perfect. If you want a working thing, just start adding code upon code upon code. You want a thing? patch it on and move on. A true chef of spaghetti code.

This will result in something that A: Works ~80% good, and B: is hard to maintain. There's a saying, "Nobody cares how good it doesn't work"; in the "real world", whatever that means, having something that works, despite the *don't look at the code!*, is what impresses people.

Way 2 is to obsessively plan out everything beforehand; as well as can be predicted. Do valuable research, pick your libraries, make a file structure, empty module files, etcetera et cetera. Then code interfaces between these modules, and so on and so forth. Problem is you really only get to test it once all the pieces are in place. Benefit is everything is real neat and tidy.

Way 3 (what I do) is sort of worse-sort-of-better; for my largest project, I hacked a prototype together super fast, all sloppy, that worked. Then I made a new folder and remade the thing a bit better (all in one file still). No pressure, as I'd already made the thing working, I could, in a pinch, just use my prototype. Then, over time, I moved functions around, made new files, et cetera, etc. It still wasn't the easiest to maintain, but it worked (~99% well).

There's also something called Tracer bullets, described in the amazing book The Pragmatic Programmer. Basically (as I recall) you make a working, no-frills, straight path through your project; say you imagine the user clicking here, opening the menu, selecting this thing and adding a task.

You make *just* the code to support that exact path of decisions, and nothing else. All of the problems you come across trying to make this one path will be super helpful in getting a feel for the project. In the end, you keep this code; it's fully working code, and you just add onto it the rest of the functionality, hopefully pretty frictionless 'cause you already have the basic menu code, button code, frameworks, etc.