At CMU, our outdoor season typically started in the beginning of March. March in Pittsburgh is, well, freezing. We were lucky if our home meets weren’t cancelled for having ice or snow on the track. All in all, March was my least favorite month in college. It always felt harder to warm up and hit top speed at these cold meets. I struggled to match my indoor times, which, because of the tighter turns, are typically a second slower for the 200m and even more for the 400m.

What made me slower during March? Was my warmup not thorough enough for the cold weather? Was it fear of injury? Could it be just decreased intensity coming off of indoor championships? I couldn’t find any specific research about sprint performance and temperature. Without a way to gather more data, I was stuck.

That changed last year when I bought a Freelap.

In college, I assumed that success in software engineering came from technical skills—that superstar programmers were those that could write the fastest/best/most code. But after entering the industry, I realized that smart software engineers are a dime a dozen. What sets engineers apart isn’t technical ability but communication skills.

Communication is important because software engineers operate within a team and business. You can’t just build what’s beautiful; you need to build what’s right for your company. If your project is falling behind schedule, you need to be able to communicate what’s blocking you to potentially non-technical teammates. And of course, you need to establish rapport with your coworkers.

No set of tips can make somebody a good communicator—it’s a skill that requires dedicated practice. I’m hoping, however, that the tips I’ve included below can help. I’ve collected them in my years as a software engineer and engineering manager. They’re generally organized by communication medium. Some of these tips apply to organizations and others to individuals, though most apply to both.

First up, some general communication tips:

New years are a time for both reflection and looking forward. I’ve never been good about resolutions—I’d inevitably forget or de-prioritize my resolutions as the year progressed. This was because I’d set my resolutions based on whatever whim I was pursuing at the time.

This year, for the first time, I followed a structured goal-setting process: I started with a set of 25 goals and whittled them down to a single goal across each of four axes of my life. Those domains are fitness, finance, mental, and social.

I designed each goal to be specific, realistic, and falsifiable. Each one also encompasses several goals from my original list as milestones or as indirect results of the root goal.

First up: my fitness goal for 2021!

I thought it’d be fun to take a look at some stats from 2020. Here they are:

Blog

• 23 new blog posts - check them out!
• 10,467 blog views
• 3,029 views on my most-viewed post
• 2 posts with more than 1,000 views (Why Clojure? and Garmin Watch Faces: Custom Fonts)

It’s the end of the year! I’ve had a wonderful time during my two weeks off, and I hope you did too! Here’s what my month looked like: