[jasey]

Even though I've been programming/developing software for 10+ years, number 4 is still relevant to me also.

What I've found is taking on the attitude of "make it work, then make it right" works well for me.

With anything moderately complex and new, you are never going to fully understand everything and get it right the first time. The best strategy is just hack something together until it "works", then constantly be revising and refactoring from there. Instead of spending hours architecting, reading and planning just jump in and start coding.

Or else you just end up in analysis paralysis or over engineering.

I'm working on a project which uses Golang, swift (ios) and Postgresql which are all new technologies for me. I haven't read a single book on any of them, I just jumped straight in and started developing. And bit by bit, line by line I have made good measurable progress.

"Plan to throw one away" applies here also - http://c2.com/cgi/wiki?PlanToThrowOneAway