This is a long overdue post, and I'm going to expedite it because otherwise I'll never post it. There...
Edit: less clickbaity title (*ok, it was 105 lines) We started to use Intercom the classic way: we...
Being a small team means that we have to wear many hats. One hour I'm looking a...
This is the second post in our series about pragmatic goal-tracking. While this...
This article is part of a series about pragmatic goal-tracking that we're publi...
Last week I stumbled upon the following question on IndieHackers: "Is it possib...
We're building a continuous feedback platform to bring the benefits of CI/CD to the way we work.
Simplicity is something we talk a lot, but how do you measure it?
What are best practices for persisting positions when using drag & drop?
A week ago I wrote about being less focused on hours in the office. Here's how we're helping switch to a trust-based culture at Squadlytics.
There are many blessings in being a remote team, but one that I like particularly is that you can't check over your shoulder to see who's in the office.
When you get a great idea, the next thing is to start building your MVP. But you should ship a "Hello World" to production instead of coding features.
No one gets excited at the idea of having another set of credentials to manage. Being safe is the story, and having a password is the feature.
Styled components are great for React, but do they work with RN?
One thing that has always been a PITA for me is using HTTPS for local development
Technical debt is something that is highly visible to the team, but we often have a hard time understanding the tradeoffs we make on the user experience.
Share your feedback about developer productivity.
I feel like my beloved Macbook Pro purchased in 2015 will give up sooner or later and I'm starting to...
At its essence, a program is a set of binary decisions, true or false. But in reality, building information systems is rarely about being right or wrong.
We rely on tracking sales at the end of the funnel while hoping that productivity stays the same. And it's only after customers have started to leave us that we look back at the way we work, to understand what went wrong.
How to convince your organization to invest in your release cycle.
Hello! I'm bootstrapping Squadlytics, a platform to help measure and improve product development (kin...
The pace of your dev cycle is the pulse of your team. A slow release heartbeat will be painful for your project regardless of the causes.
Technical debt is an inherent part of software development. You can't prevent it from happening but there are ways to make it easier to handle.