Estimating, like anything in software development, is a skill. And it's HARD.

Estimates are invaluable for us to project plan.

I think misunderstanding what's in an estimate is a big reason so many devs hate estimating.

I see teams choose to forgo estimates when they find them challenging and don't see value in them. But there's a ton of value in team estimates!

Estimating is HARD but it's a skill that you can hone like any other, such as coding or professional communication.

To successfully modernize your legacy technical systems, you have to start by modernizing the human systems that support them.

Technical debt in software projects is unavoidable. It’s the cost of doing business. The key to maintaining a healthy codebase is proactive debt management.

Legacy code bases get a bad rap, but they are fun puzzles to solve. What should you look for when inheriting a legacy code base, what can you learn from a code review, and how should that affect your recommendations and estimates?

Legacy code bases get a bad rap, but they are fun puzzles to solve. What should you look for when inheriting a legacy code base, what can you learn from a code review, and how should that affect your recommendations and estimates?

Being a hair stylist is like being a personal consultant for each client that sits in your chair. My mom owns a successful hair salon in my hometown. A lot of what I know about being a good consultant comes from watching my mom and the other stylists.