Kevin is the VP of Engineering at Abnormal Security, overseeing all aspects of growth and execution. In this class, he walks through the steps required to create and support a SaaS product from an engineering perspective, with a particular focus on what aspects to prioritize in the early days of your product. Kevin spent time at eBay and Quantcast prior to becoming an early-stage engineer leader at TellApart, then a Director of Engineering at Twitter.
I think, I think the honest answer is that it really depends on the product and the problem you're solving. There's no one size fits all. I feel like the engineering discipline at its heart is a discipline of trade-offs and we have to use our judgment to realize where on the spectrum of trade-offs is appropriate for this problem.
Kevin W: This product is company the stage, right? you can [00:04:00] never optimize for all three of these things at the same time. You just have to be realistic and honest that you're always trading one-off. If you're building, systems that I've worked in the past, around, advertising technology online, where we can do continuous deployments, almost instantaneously to update mistakes. You have a very different kind of bias, right around speed and quality to contrast that if we were building,the embedded systems of a car or some kind of mission critical system, of course, we'd have a very different kind of sense there of where we want to be on a speed and quality spectrum.
So I really think that it really has to come from taking a really. Honest look at the business and the product and the solution we're trying to build and just adapting over time based off of what makes the most sense for your particular problem. There, there really is no perfect answer for this one.
