News for hackers. Stuff that matters.
Re:Ask HN: Top rules as a good-developer to stay on top of y... by mbrock on Thursday September 22, 2016 @04:50AM (#12555478)
Don't you think the emphasis on repetitive practice makes more sense for skills that are based on bodily coordination?

I think getting better at programming has more to do with learning patterns, thinking carefully, and hard-won experience.

Re:Ask HN: Top rules as a good-developer to stay on top of y... by falcolas on Thursday September 22, 2016 @09:34AM (#12556685)
You're missing feedback. If you don't get regular feedback, all the thinking and patterns in the world aren't going to help you learn.

Feedback does not need to be external; it can be driven by the requirements you set forth for yourself. "I want to learn to build in low memory environments," leads to "This backend must never use more than 1MB of memory." "I want to figure out how to optimize programs," leads to "This backend must respond to every request in under 50ms." "I want to know everything about my current programming language," leads to "Obfuscate Hello World!"

Create a feedback loop and write simple programs, each time with different criteria. "I can only use functions," or "This must be as fast as possible," or "this must be as slow as possible (without using sleeps)"... the possibilities are many, and the time required is small for each exercise.

They make for great 20^H^H1% projects or "I need to step away from my current program" tasks.

Re:Ask HN: Top rules as a good-developer to stay on top of y... by mbrock on Thursday September 22, 2016 @09:53AM (#12556804)
Well, I thought of feedback as part of "hard-won experience", but yeah.