Building a business is a slugfest to see who gets more customers first. You have to adopt that mindset when writing code. As an old boss told me once: Clean code won't matter if we're dead. You have to shift your mindset from best practices to getting shit done. But you can't go too wild or the tech debt will kill ya.
This talk has been presented at C3 Dev Festival 2024, check out the latest edition of this Tech Conference.
To scale a business, you can either sell more products to more people or sell products at a higher price.
The S-curve refers to the saturation point where customer churn and acquisition balance out, causing growth to plateau.
Business growth provides opportunities for promotions, new engineering challenges, and overall career advancement, avoiding a zero-sum game environment.
Teams should be organized vertically by business domain rather than horizontally by function to avoid dependencies and bottlenecks.
'Owning your destiny' means that a team can take an idea from inception all the way to production, delivering value to users without being blocked by other teams.
Domain expertise allows teams to understand user problems deeply and collaborate effectively with product management to develop optimal solutions.
Code review processes can be sped up by agreeing on the design and solution before writing any code, allowing for quicker checks and faster merges.
The biggest challenge in software engineering is managing complexity, especially avoiding the temptation to create overly generic solutions.
Libraries should only be split off when they are stable and no longer require frequent changes alongside the product, ensuring they serve as proper abstractions.
During rapid growth, you need to scale the business, the team, and the tech.
Comments