drummyfish/less_retarded_wiki
5
1
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity
less_retarded_wiki/programming_tips.md
Miloslav Ciz e5834a1aaf Update
2023-04-22 16:13:38 +02:00

2.4 KiB
Raw Blame History

Programming Tips

This is a place for sharing some practical programming tips.

  • Add by small steps: When adding features/functionality etc. into your code, do it by very small steps and test after each step. Do NOT add multiple things at once. If you add 3 features at once and then find out the program doesn't work, you will have an extremely hard time finding out the bug because it may be in feature 1, feature 2, feature 3 or ANY COMBINATION of them, so you may very well never find the bug. If you instead test after adding each step, you find potential bugs immediately which will make fixing them very quick and easy.
  • No indentation for temporary code: Tiny "workflow" tip: when adding new code, keep it unindented so that you know it's the newly added code and can delete it at any time. Only when you test the added code, indent it correctly to incorporate it as the final code. Of course, this fails in languages where indentation matters (Python cough cough) but similar effects can be achieved e.g. by adding many empty lines in front of/after the temporary code.
  • Comments/preprocessor to quickly hide code: It is a basic trick to comment out lines of code we want to temporarily disable. However preprocessor may work even better, e.g. in C if you want to be switching between two parts of code, instead of constantly commenting one part and uncommenting the other just use #if 0 and #else directives around the two parts. You can switch between them by just changing 0 to 1 and back. This can also disable parts of code that already contain multiline comments (unlike a comment as nested multiline comments aren't allowed).
  • KEEP IT SIMPLE and keep it LRS, do not blindly follow mainstream ways and "workflows" as those are more often than not horrible. For example instead of using some uber bug tracker, you should use a simple plaintext TODO.txt file; instead of using and IDE use vim or something similar. Stay away from OOP, dependencies etc.
  • Don't listen to advice of anyone who does programming for living, he's most definitely accustomed to the worst ways of programming and will try to push you to OOP, bloat, proprietary tech, tranny software, GitHub etc. Listening to advice of such people is like taking advice on whether to take drugs from a drug dealer.
  • TODO: moar