3 ms·
The problem with product is that they care about individual features and not features in general. This leads to an inability to see the overlap across product
by yarg 6y ago
The problem with product is that they care about individual features and not features in general.
This leads to an inability to see the overlap across product distinct features that all seem largely the same from a platform perspective.
The goal for platform is to take the overlap and push it down the stack, behind an API - hiding the subset of complexity that product does not need to be exposed to.
Platform gets to hide the dragons, and product gets an API that allows for features to be implemented quickly and cleanly (it also provides improved constraints from a testing perspective).
However, when there's a feature that cannot be implemented against the constraints and features currently imposed and available, things slow down - until platform figures out what new abstractions should be presented to allow for the new feature to be implemented.
It does not matter overly if platforms initial implementation is well implemented or hacked into place - fix it later, but try to do a good job on the abstractions (this will allow for product to cleanly implement the new feature and for the platform side technical debt to be handled later on, without major impact to product).
- deleted 6y ago[deleted]
- hayst4ck 6y ago> This leads to an inability to see the overlap across product distinct features that all seem largely the same from a platform perspective. Bingo! The worst is when a product team circumvents platform or doesn't invest in the overlap, resulting in 2 complex things to maintain, slowing down the organization overall and creating future migration problems. Alternatively they create it, but then platform ends up paying the maintenance cost.