[nicbou]

Write longer scripts. You will very quickly repeat the mistakes for which we have architectured solutions. Then you can make informed searches to solve those problems.

You can also look at how simple applications are organized, or look at application templates to see where everything is.

You can also read about common software development patterns as they are answers to those common problems.

I don't have a specific book to recommend. I found that stumbling through worked a lot better for me. Write something simple and useful, and rewrite it often. It's very easy to keep improving upon something that you actively use on a daily basis.

[hankerito]

Thanks! The idea of templates is great, i think!

Also just pushing ahead is just what I need to do and later refactor. I always tend to stop, when I feel something I am about to do should be done better, but don't really know how.

[nicbou]

Once it's finished, you'll want to make changes to it. Over time, you will see what makes changes easier or harder. Then the literature on patterns will really click.

If you read about patterns too early, they don't "click", but rather become something you overprescribe without really thinking why. We call it design patternitis.

I have overengineered far more code than I have hacked together. Now I'm a bit more cautious about it.

Templates are a good middle ground. They give you a good mold for your application, and inform you about best practices that you might not think about.

Just don't sweat it too much. If software solves problems, it does its job.