Random machine crashes, network partitions, disconnections, delays, package reordering? In large enough distributed systems, they’re bound to happen. In a mission-critical system like Base we need to ensure they don’t affect our users. Here’s how we do it
First, I'll say that an average developer has no clue about how to use Git to collaborate. Then, I'll blame it on Git tutorials. Finally, I'll share my experiences to help you get past the basics and become the developer every team needs. Sounds good? Let's start.
This time, I want to focus mostly on the technical aspect. I will, however, touch on how we work and what the mindset of every single Base team member is because these things actually have a big impact on how fast you grow.
My first 100 days as a member of Base Lab have passed real fast. Over this period I have made detailed notes on what I did and how I felt each day. It has been an interesting experiment that, as it turns out, has provided some good material for a blog post.
People kept asking us: “why are you guys building yet another CRM?” It’s a valid question as there are many solutions available in this space. The great majority of them however, suffer from very low user adoption, which makes companies using them know very little of what’s really happening with their businesses and significantly limits their growth.