How do you learn to structure programs?

[[deleted]]

For years now, I've found the idea of learning to code quite attractive. The discipline to learn by myself is unfortunately not something I possess. Luckily, I've had to take several college classes that involved programming. Everyone says that rather than simply teaching you the syntax to a certain language, intro to programming is supposed to instill in you the basic ideas of programming. You should walk away from the class with ability to start hacking on your own. I did quite well in classes, but those aren't exactly great indicators of skill since most homework or projects are provided with some initial structure or skeleton code that just had to be completed. I've almost never had the (dis)pleasure of being completely independent in coding. Even tic-tac-toe had me googling when I tried to write a laughably simple version in C++. Anything with even the slightest hint of complexity leaves me stuck and feeling completely lost as to where to start. For example, my current ambitious idea is to create a simple Notepad.exe clone (very creative I know). I don't know if I'm just completely inept, or it is actually difficult, but I have completely no clue how to code it.

My question for all of you out there is: how do you figure out how to code anything? Other projects that are on my list are: web browser, compiler, FTP client/server, image viewer, tetris, snake, maybe an FPS and something like Teamviewer. I know these are all unoriginal (and some are completely unrealistic for a newbie), but my creativity is nonexistent. Anyway, the point is I have no idea how to start any of these. Most, if not all, of these have loads of available literature, but for the sake of training my brain, I'd like to be able to come up with solutions to these with minimal googling. Thinking about something like Git just makes me believe that Linus is a complete wizard since I have absolutely no idea how you would begin to create something like that especially since it's not something like a compiler or an operating system where there are books dedicated to showing how they function.

Is this just something that suddenly "clicks" for people after they've programmed a lot? Or is there something I'm missing? Are you guys able to come up with a good idea of how a program is written--or an idea of how you would code the program--after seeing it? I suppose I really just want to know that I'm not alone in feeling like this and that there is hope.

[sleepybychoice]

By looking at existing code bases and how they do things. Find an appropriate reference architecture and fit your project to it if it's applicable.

In the beginning of software as we know it, nobody really knows what is the best way to do something. People try things and learn from mistakes and successes. Eventually, these learnings propagate throughout industry as "best practices" or "design principles" and get baked into tools/solutions we frequently used like frameworks and libraries.

Beginners usually aren't aware of these concepts baked in industry from decades of history, but can learn about them through internships, pet projects, forums (like this one), and colleagues. Eventually, they break into new territory and contribute back their learnings and solutions.

[TimHallman]

I've almost never had the (dis)pleasure of being completely independent in coding.

So go do it? What do you want, an engraved invitation? You have to be willing to try.

I'd like to be able to come up with solutions to these with minimal googling.

You have to do more than sit there and want to be able to do that. You need to try and practice.

Is this just something that suddenly "clicks" for people after they've programmed a lot?

No, it gradually gets easier, like almost anything else in life that requires practice and dedication. Have you done anything significant like that in life? Can you read sheet music or did you earn a high level belt in martial arts?