2 ms·
>Any change needs to be done from both ends. If the change needs to be done on both ends it is probably an integration problem, which I labelled unkind. The u
by bryanrasmussen 6y ago
>Any change needs to be done from both ends.
If the change needs to be done on both ends it is probably an integration problem, which I labelled unkind.
The use of the words kind/unkind is probably not well-thought out, because kind implies easy, but there is nothing in the description of the term that means it is an easy thing to do.
- Chyzwar 6y agoKind because there is an obvious path forward. Unkind because there is uncertainty over time. In programming there is no objective measures for code quality, cost of maintenance or even productivity of individuals. I would argue that programming is fundamentally unkind. You can only learn a small fraction of stack and operate on assumptions. It is very hard to learn from other people's experiences as it is hard to quantify complexity. If someone is preaching for microservices you can only understand tradeoffs by having a specific knowledge/experience. That why we have people still using PHP for new projects because they are so entrenched in their local maximum.