Session 4 - Crap Code

In this session we're going to address "quality issues", or, in more direct terms: root out the crap code.

It goes without saying that having a formalized process for reviewing any code is critical. You can trust AI to do a lot, but you and your team must maintain control and not let the machines take over!

What you're about to do is take a basic first step, and see if you can mitigate any concerns that your lead or boss might have when reviewing the code.

Things like:

• Documenting things according to company policy.
• Proper error handling.
• The addition of "mandatory" things like an .editorconfig and a well-written README.

You might have additional requirements at your company, and as always, feel free to experiment as we go along.