I always find that I learn best by doing, and exploring the codebase myself. But even then, it’s important to know when to ask for guidance instead of not making any progress alone. Finding the balance is crucial 

WeAreAllSatoshi

There is a lot of really great stuff in here. Any engineer should read this, and I bet you’ll find at least one item which you can improve upon 

I haven't read through the whole thing yet but so many good gems in here.

> If you err on the side of writing perfect code, you don’t get any feedback. Things just universally take a long time. You don’t know where you’re spending your time on things that really deserve it, and where you’re wasting time. Feedback mechanisms are essential for learning, and you’re not getting that.

k00b

pbl4eagain

tech

This link was posted by [marcusbuffett](https://news.ycombinator.com/user?id=marcusbuffett) 1 hour ago on [HN](https://news.ycombinator.com/item?id=40829607). It received 65 points and 16 comments.