Ken Halbert

I've been working with JavaScript, my favorite programming language, for my entire career - to build native apps (with PhoneGap), web back-ends and back-end services (with Node), and websites/JavaScript SPAs (of course). On the front-end, I have experience working with both React and Angular, though most of my work in recent years has been in the React/Webpack/Babel ecosystem.

C# is the language I started my career with and was my bread-and-butter for years. Over the course of my career I've built many business-to-business, business-to-consumer, and internal applications using the Microsoft stack (ASP.NET MVC, ASP.NET Web API, Entity Framework, etc), and more recently I've been spending most of my time building microservices with .NET Core in AWS.

I've been working with React since 2015. It's my go-to JavaScript framework for new projects, both professional and personal, unless some specific factor (e.g. team composition & skillset) makes Angular a better choice.

I've spent much of my career working in AWS - mostly with EC2, RDS, S3, DynamoDB, API Gateway, CloudFormation, and Lambda. I have a devops mentality, and I'm not content hyper-focusing on just one part of a system (and yes - the application code is just one part). I like to have a well-thought-out and useful CI/CD pipeline, 100% automated infrastructure and code deployments, reliable and meaningful metrics and alerts, and infrastructure and architecture that is resilient and doesn't keep me up at night (either through stress or because it goes down at 3 AM). It has been my experience that even a small team that's proficient in AWS can accomplish all of this with ease. I also have a lot of experience building serverless applications in AWS with AWS Lambda, API Gateway, DynamoDB, and S3.