The latest posts from Sturdy

Hello world! In this newsletter we're sharing some of the biggest updates and new features in Sturdy v1.8, let's get started!

Most software projects are done by teams rather than individuals, so how we integrate work is critical. Collaborating on code is surprisingly challenging because any change made in isolation creates distance between developers. Shipping small and often is probably the most effective strategy for mitigating this. But just how frequently can we ship?

Hello world! In this newsletter we're sharing some of the biggest updates and new features in Sturdy v1.7, let's get started!

Hey everyone! In this week's update I would like to share with you an update to the Sturdy workflow with Draft changes, as well as the release of Sturdy for Linux. Today is also an exciting day for us because we are launching Sturdy on Product Hunt!

We have some really exciting news to share — Sturdy is now open-source! As developers, we love OSS, so to say that we are thrilled about this announcement would be an understatement!

GraphQL has become somewhat of an industry standard for APIs that are designed to be consumed by component-oriented UIs. Meanwhile, GraphQL client libraries have converged on strategies for maintaining a normalized cache of all parts of the graph that has been queried. This article proposes some patterns on how to maximize the utility and maintainability of frontend code using this stack.

Hey! Here’s a summary of all of the latest and greatest features available in the latest version of Sturdy.

Why team output doesn't scale linearly with team size? Teams are no different from a parallel computing systems. As such, they are subject to Amdahl's law, which governs their scalability.

Hey! Here’s a summary of all of the latest and greatest features available in the latest version of Sturdy.

Sturdy changelog. Sturdy now ships with Access Control Lists and a brand new interface, that's faster and more lightweight than ever.

Hey Sturdy-fans! Here's an update with all of the major changes since the last time we hit your inbox.

I feel like collaborating on code today is broken. It is too hard to get started and even after learning all the basic tools and commands there is just too much effort in making contributions as a team. Why is it so hard to give meaningful feedback on each other's code? How come the rest of the stack has evolved, when collaboration hasn't?

Making a new version control system is definitely not for the faint-hearted! It has taken us a lot of work to lay the foundation for the code collaboration platform that we are building.

We’ve been thinking a lot about what it means to work on a team lately. Most often, developers are working on the same codebase, but are not really working together. More often than not the first time a teammate of your sees the code that you have written is when you’re considering the feature to be complete, and you’ve sent it for code review.

Hey everyone! I hope that you’re doing great, and that May is treating you well!

Hey coders! As you’ve noticed, we’re still exploring the fundamentals to the core workflow of Sturdy. This week we’ve made some larger changes to when changes are copied from a workspace to a codebase. Let’s get into it!

Hey everyone! This week we’ve been focusing on how Sturdy can help you if you make a mistake, or change your mind about what you’re building.

The past week has been the culmination of our YC W21 batch, with Demo Day1 on Tuesday! A huge congratulations and thanks to all other companies in the batch!

Hey everyone! We've been working hard on Sturdy for the past few months, and as you might have seen, we've been making quite a lot of changes. I'm super excited about where we're going, and to be able to show of Sturdy and some of it's internals here in this post.