AWS has released a developer preview version of the CDK for Go. Considering I haven’t had the chance to use CDK yet, and I spend chunks of my time wrestling CloudFormation, I thought I’d install it in a new project and see why people are singing its praises.
I spend countless hours talking to people in the startup ecosystem. If anyone is willing to have a coffee, schooner or a video call with me to talk about technology, it’s usually an hour well spent. It’s a great way to understand what other people are working on and the challenges in their respective industries. So without further ado, let’s look at some insights I’ve gleaned from conversations I’ve had in the last six months.
Company culture is a hard thing to get right as a so-called “good culture” is entirely subjective. Software culture is even harder as you often have to manage very different personality types on top of the usual things, such as understanding people’s motivations and career goals. In early-stage startups, culture is an evolving organism.
Much has been written about technical debt, how it impacts software projects and businesses, and why it is both a awful thing and a necessary evil if you want to ship something meaningful. In this post, I’m going to look at technical debt in startups and what you can do to mitigate it while still delivering a product your customers want and find useful.
As tech workers, we’re in a privileged position during the current COVID-19 pandemic that we can mostly self-isolate and protect our families and loved ones. My team are remote about 50% of the time, but we always try and be in the office for planning sessions, 1-on-1s, etc. During this period, we’ve had to adapt to being fully-remote. Here are some tips for teams that may be adjusting to working remotely for the first time.