Keep your Communicator.msi handy

Well that was weird. I had a flaky SATA driver cause a blue screen of death on me a few minutes ago and after the restart Communicator wouldn’t launch. Instead, it was prompting me for the path to a Communicator.msi. Glad I had it on hand because apparently that crash damaged the app somehow. All was well after I pointed at the .msi and it repaired itself. Strange.


Recent content I've written for you—just for you!— to enjoy while you're here.


Quick commentary and links to other sources you'll find interesting. I promise.


Some personal background, links to related projects, and other ways to connect.

Hi there. My name is Tom Pacyk and this is my small home on the web. I love the intersection of design, technology, and communication, which is a combination that led me to a career in sales and marketing roles at places like Zoom and ServiceNow. They're a bit old now, but I also had the opportunity to publish a couple of books along the way.

Portland, Oregon is home for me, my wife Beth, and our three kids, but I'm actually a Midwestern transplant—I grew up in the Chicago suburbs and went to school at Purdue and Illinois. When I find some free time I'm probably going to concerts, rooting for the Portland Timbers, or working on my Sunshine Burn Photography project.