[secondbreakfast]

Daily process goals are a wonderful life skill.

You can improve your writing skills by writing every day. I recommend it.

But the best way to become an elite programmer is to understand complexity: when it’s okay and when it will kill you. The best way to understand complexity is to have ownership of projects that grow in size. You’ll watch the database queries start to buckle or the abstractions hamper readability or the singleton grow grossly in scope.

Build things, publish them, and work on them over longer periods of time. Share them with friends. Learn from the brittle parts of the code.

[iobt92]

I like your point on complexity; from that statement alone I am far from it yet. The layers of abstraction which I have had to deal with so far can be said to be merely surface-level. This is a goal I'm still trying to consciously work on as well (being able to handle complex projects). I guess for someone who is a newbie like myself I may be jumping the gun too early by finding myself veering towards systems which I may not understand e.g. operating systems, compilers.

[secondbreakfast]

There is no jumping the gun! Go for it.