SudoGroup: Little summary about writing good code

WGC_Summary.txt

[&] How to write a good code ?

Terms:
- technical depth
- refactoring
- naming convetion

Simple Topics:
* shortcuts is bad and causes reading problems for long time
* you have to make multiple files for multiple classes/functions (ie. main.cpp + head>
* you should follow the same way the code language community writes
* you MUST write comments, dont write an essay, just a basic clear comment
* can you change your code later ?

Resources:
+ Clean Code: https://smile.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/>
+ VSCode Linting: https://code.visualstudio.com/docs/python/linting

===================================

[&] How to check if your code is good or bad ?

Terms:
- TDD "Test Driven Development"
- test engineers

Simple Topics:
* test each code line first, check its working, then continue building, REPEAT

Resources:
+ Test-Driven Dev: https://www.wikiwand.com/en/Test-driven_development
+ TDD Image1: https://marsner.com/wp-content/uploads/test-driven-development-TDD.png
+ TDD Image2: https://www.cdslab.org/matlab/notes/preliminary-foundations/programming>
+ Test automation Uni: https://testautomationu.applitools.com/
+ How to make your code reviewer fall in love with you: https://mtlynch.io/code-revie>

___________________________________
./Presenter: @sudomaze
./Thanks to all who attended <3