blog

For the past several months, I’ve been slowly migrating more projects to languages and frameworks that fit better in Visual Studio Code (VSC) vs. Visual Studio. The transition has gone quite smoothly. The add-on support of VSC is excellent and, so far, the performance is hands above Visual Studio (no more coffee breaks while the app starts and loads a project).

Between Slack, Skype, Zoom, Discord, Facebook, and whatever other chats I have loaded on my desktop, a good, comfortable mic is important.

I love when my team shares cool ideas, hacks, and optimizations. It shows they have passion for what we’re doing and see the job more than just an inbox/outbox gig–and the team is made better by the innovation and contributions of each individual member.

Now that the initial configuration is taken care of (see part 1), the real interesting stuff awaits in part 2.

As we run screaming into the new year, it’s the time of year that most companies are double-checking their roadmaps: comparing it to last year’s Q4 data, seeing what worked and what didn’t, and adjusting course accordingly (see my article about pivots vs. features).