3 ms·
> Write aesthetic, simple code This is incredibly “draw the rest of the owl”. If it was easy to do that we would all do that. Step one to become a good develo
by SanderNL 3y ago
> Write aesthetic, simple code
This is incredibly “draw the rest of the owl”. If it was easy to do that we would all do that.
Step one to become a good developer: be a skilled developer.
Thanks for that. Also, overlapping skill is less useful than you make it out to be. They also all have arms and eyes. That’s not what sets them apart. Engineers of some standing all follow these very basic guidelines. That does not an 1% engineer make. In fact, there is no definition of this fabled one percent engineer. At least not in this article so I cannot be sure what this is about.
The fact this article starts out with referencing big companies and leading positions - AKA status and power - also signals that these people he regards so highly are at least also talented politicians and/or entrepreneurs.
- bryancoxwell 3y ago> This is incredibly "draw the rest of the owl". The post isn’t meant to be a tutorial on becoming a top engineer though.
- jabradoodle 3y agoKind of besides the point, "be good at X" is a trait; not a habit.
- perihelions 3y agoFor people not familiar with the metaphor, this is the context: https://i.imgur.com/rCr9A.png https://i.imgur.com/rCr9A.png ("How to draw an owl")
- dkarl 3y agoTo get better at writing code, stick to this rule: Never submit a first draft. Always make your code better before you submit it. If you can see the difference between ugly, complex code and aesthetic, simple code, and you're willing to spend extra time to go over your code and make it better, you'll develop the skills to write it better in the first place. This won't teach you taste (years of maintenance and exposure to other people's code will do that) but it will teach you the skill of living up to a style.