Sprints are stupid. Just use a prioritized list and take breaks
I don’t like sprints. You shouldn’t be sprinting when trying to deliver something. Instead, you should be prioritizing things and doing them one at a time.
Sometimes I write about coding, startups, or other adventures.
I don’t like sprints. You shouldn’t be sprinting when trying to deliver something. Instead, you should be prioritizing things and doing them one at a time.
Recently, I’ve decided to go all in on two things, Typescript and GraphQL, after spending most of my coding career building RESTful APIs and avoiding types using languages like Python, Ruby, PHP (before type hints), and plain old Javascript. So, why the change?
If you’re building a delivery team (Product + Engineering) there are two metrics that you should always be aware of to assess the health of your cycles. You also don’t need to track these metrics. Especially at an early-stage startup. You should be able to know these metrics intuitively.
Starting a new project can be equal parts fun and terrifying. Over the last year, I’ve been building Wellen and I wanted to talk about some of these key decisions that I’ve made with our tech stack and how they’ve played out so far.
My name is Nate. I’m an engineer currently working as a member of the founding team at Wellen -- a startup in the health-tech space. I’ve always been a bit squirrely about sharing stuff on the internet, but lately, I’ve been in the mood to start writing things down somewhere.