Skip to content

Instantly share code, notes, and snippets.

@justinmeiners
Last active May 5, 2023 16:23
Show Gist options
  • Save justinmeiners/be4540f515986d93ee12ac2f1980631a to your computer and use it in GitHub Desktop.
Save justinmeiners/be4540f515986d93ee12ac2f1980631a to your computer and use it in GitHub Desktop.
@JPVenson
Copy link

This is a perfect example of someone who actually reviews its own skills. You Sir are expected to be the top 20% of programmer out here in the world who knows that nether everyone is perfect and nobody will every be.

Everything you said is perfectly valid and this text should be made available to every new Developer.

@ndandoulakis
Copy link

Hi Justin,

Nice article. I really liked the Organize and design systems section.
In my opinion that's the hardest thing in programming. It takes years of work to learn how to design,
therefore it's an advanced skill to acquire, not a basic one.
Probably less than 1% of the programmers know how to do it well (1% because I don't want to say 0.1%).

@aal89
Copy link

aal89 commented Feb 20, 2019

I concur. All three chapters are valid, especially the last one. Mixing and duplicating knowledge throughout the code base leads to spaghetti code. I always question myself what does x mean in this greater y picture and does this represent something logical. Semantic holism is the most important thing when designing.

@woanversace
Copy link

Finally, have someone that describes nature of bug correctly
💯

Debugging is also extremely difficult if you don't understand the language. You may add a line of code because it fixes a bug for reasons you don't understand. Bugs are mysteries that seem to appear organically, like dust on the shelves. The code seems to have a mind of its own.

Love this post!

@gramster
Copy link

s/Fred Books/Fred Brooks/

@justinmeiners
Copy link
Author

@gramster

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment