Do your code comments suck? Avoid these 3 Traps!

Hey friend,

As a software engineer, you regularly work on projects with lots of moving pieces. Even if your codebase is small, it grows and grows as features are piled on, and it’s difficult over time to keep track of these of everything that’s going on. Nobody likes working on code that’s confusing & lacking documentation, which is why we’re going to have a nice heart-to-heart on commenting code.

By commenting your code well, you can make a positive impact on the products you work on and earn the respect and gratitude of your teammates for writing software that's easy to read and maintain.

Unfortunately, even the best of us can fall into several traps with comments that make our code puzzling and frustrating to our colleagues (and even our future selves 🤦‍♂️)

Today I want to talk about 3 traps with respect to code comments and what you can do to avoid them. Let’s discuss!

Now before we jump in make sure to grab this free guide ...

You’re probably here because you’ve heard that learning to write computer code is a great way to create solutions to problems that the world has. These skills are valuable and marketable to employers in virtually every industry. Market data consistently ranks software engineering as one of the highest paying and most satisfying career paths, so you may want to pick up coding skills for a few different reasons:

1. Getting on a career path that comfortably provides for you and your family
2. The flexibility that a lot of software engineering jobs have to work remotely all or part of the time.
3. You may want to bolster your existing subject matter expertise with coding skills helping you add more value at your current job, and even get you promoted!

Whatever the reason, it can be tough to know how to get started. The journey to becoming a seasoned coder is full of triumphs and perils and the on-ramp will look different depending on your unique circumstances, which is why I want to brea...