[ftwynn]

I've started and stopped a number of times. Mostly I don't have an itch to scratch that pushes me to make anything interesting.

I find myself particularly struggling when language walkthroughs get to libraries and code organization. Follow all the paths and dependencies is really tough for me.

[monk_e_boy]

I'm a coder. But I often do little side projects for things that I just wonder about.

Today I'm wondering how code is made into binary and how that flows through the processor and how the logic moves data to and from memory. I'm not sure how I'm going to code anything to represent that, but that's half the fun.

Last month I was a bit obsessed with organic tentacles and how to make them move using muscles. I coded this in javascript using canvas. Pretty fun. They make lots of interesting patterns.

Before that it was games like cookie clicker and candy box.

Before that it was neurons and AI - again I just coded little fish in javascript, hooked up a neural net, they gained score depending on how close and how much time they spent near food. Then breed them and repeat. Do this for half a day and they get really smart. It's cool how a few arrays and sigmoid functions turn out to be smart. Even though I coded it all, it still amazes me.

I think the thing is to find something that interests you. Maybe code your own blog. Or online text adventure. Or multiplayer pong clone.

Part of your problem is that you are trying to do too much. Libraries, code organisation, etc are all fixes to problems. You need the problem first (while you are learning) so write spaghetti code and it's not until you go 'OMG this is hard to understand' then you need to look up code organisation and only then use the minimum that is needed to improve your situation.