Clean Code Guidelines

3min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Each project that you're starting probably should get some kind of a number one through 10 of how Strict the clean code guidelines need to be for this this repo. I would get balanced because like at a certain point Your developers are just going to stop caring because there's way too much overhead to get something done. But naming things is an art a special if you have a system for it How and where is css defined what patterns for class names? And so we also have code rules right we have those repo rules in your code Rules can mostly be solved by formatting and linters and HintersThose types of things right basicformat tools that that can take care of a ton of issues prett

In this Hasty Treat, Scott and Wes talk about the difference between sloppy code and clean code, how to establish rules for your code base, and how to enforce your rules.

Sentry - Sponsor

If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up.

Show Notes