3 ms·
I've spent a couple years working on B2B Enterprise SaaS. So, why do these systems suck? These systems are made in environments that simply are not conducive to
by JMTQp8lwXL 5y ago
I've spent a couple years working on B2B Enterprise SaaS. So, why do these systems suck? These systems are made in environments that simply are not conducive to approach software development in a healthy way. From my experience it's a combo of: bad technical leadership, too many cooks in the kitchen, a lack of knowledge sharing, and a lack of alignment.
Bad technical leadership: Basically, everything's a free-for-all. Teams are unbounded to do whatever they want. You end up with a Frankenstein technology stack. Technical debt grows, nobody does anything about it, and slows down your ability to quickly pivot over time. New execs join and are flabbergasted when they can't fix everything in a quarter due to the lack of adequate process instituted in healthier software organizations.
Too many cooks in the kitchen: The lack of standards means re-implementations of product features numerous times, in different technologies, with no awareness across silos.
Lack of knowledge sharing: often times there's supposed to be cross-cutting features that would impact every microservice (eg: multi-tenancy) and you'll have one microservice team implement support, and another one won't. Inevitably, someone will eventually notice and you end up with a support ticket.
Lack of alignment: One part of Product thinks the multi-tenancy feature really isn't that important, but the other does. They lead their engineers to skip that feature.