I’ve been working on a new release for a game server I operate on the side and, with any new release, comes
opportunities to weep at refactor your older code.
The past ten years or so, be it in an official capacity or consulting, I’ve worked with various organizations to coach
and lead high-performing teams. While I’ve spent most of my career in the technical space, I’ve had the privilege and
honor to work with and help lead some amazing digital product teams the past three years.
Over the past several years, my career and learning path has dove deeper into leadership strategy and product marketing.
As with many organizations, the excitement of machine learning, AI, and rapid prototyping has found a home in our team
as we research, learn, test… and then either succeed or fail… then start all over again! I recently had a chance to
sit down with product team leads from a few different organizations and talk about ideas, trends, and how teams were
keeping up.
As organizations continue to cancel events, many companies are also pushing employees to work remotely. For those of us who have been working remotely for years, this is just another day. However, for those new to remote work and managing remote teams, it can be a huge shift in worker dynamics. For many, employee trust rears its head.
I’ve been working on a project the past few months in asp.net core 2.2 and am in the process of converting various aspects of it over to Blazor (more on that soon). The first step is getting everything converted, in place, to asp.net core 3.0.