Best Practices (Programming)

Write code drunk, edit sober[5]

When coding solutions to problems, overoptimization is your greatest enemy.

  1. Make it work, at all costs. Don't give two shits about it, because if it sucks, you can always delete it all anyway. Make liberal uses of git commits to scaffold your way to a solution, but don't be afraid to just blow it up and start over.
  2. When it works, refactor it. Make it understandable to a human being. Make it as concise as possible, but not too concise. Imagine you are seeing the code for the first time, does it make sense to you?
  3. If necessary, make it fast. Unless you are doing some very crucial code where milliseconds matter, this optimization is not as crucial as you think it is.

Writing Code

Job/Soft Skills

Self Development

References

  1. https://www.reddit.com/r/webdev/comments/kzqmhb/im_in_awe_of_you_all/
  2. https://softwareengineering.stackexchange.com/questions/43151/should-you-sacrifice-code-readability-with-how-efficient-code-is
  3. https://www.infoq.com/articles/no-hotfix-deployment/
  4. https://github.com/cotowali/cotowali/blob/main/docs/development.md
  5. https://www.bitquabit.com/post/learning-writing-and-coding-from-a-con-artist/
  6. https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction

Last modified: 202208021432