• 0 Posts
  • 8 Comments
Joined 2 years ago
cake
Cake day: December 25th, 2023

help-circle



  • I find most bad codebases exist because of a culture that isn’t focused on quality, and I’m not talking about bug counts or code coverage. Clean codebases stay clean by being proactive about keeping them clean. This should include meticulous peer reviews, establishing design patterns, enforcing best practices, and taking initiative to leave things better than you found them (we used to call that boy scouting).

    If your teams PR comments only contain LGTM, and the average time spent reviewing them is 5 minutes, your team isn’t focused on quality. If a PR contains more files than an average person can keep in their mental context window, it won’t get the attention it needs to be properly reviewed. If there is no accountability to keep a clean codebase, you’ll end up with 2 hours of work taking 5 days to complete.





  • In the mid 10s, I worked as the engineering director for a consultancy. My boss would openly brag about being able to hire women for a fraction of the cost of a man. I was so offended by this that I created a partnership with a coding academy for at-risk and underrepresented individuals just a few blocks away from our office. I made it my mission to hire as many women junior engineers as I could, just so that I could train them up and find them better paying jobs elsewhere.

    Women engineers are out there, and I hope I’ve made the dating pool just a little bigger for you.