|
|
|
|
|
by bob1029
1493 days ago
|
|
> They don’t actually mind proprietary languages. They want products that work, and products that work together. Modularity and flexibility are useful to the extent that they’re means to those ends. This is why we are a pure Microsoft shop today. Between Visual Studio, GitHub and .NET/C#, we have been able to construct a stable, long-term B2B product stack with a very small team. If we had selected a more diverse tech stack, it is almost certain that we would have failed. I know this because we tried microservices, simply on top of a pure Microsoft stack, and it almost killed us. I cannot imagine the depths of hell we would be in if we had tried to mix & match different tech on top of that horrible idea. Are we taking some risk that we are missing out on some amazing new tech that Microsoft would frown upon? Absolutely. But, we know what works for us, the roadmaps are clear, and our customers are happy (they love that we only have ~1 vendor). The things that Microsoft does not like, we just invent in-house. Fortunately, there isn't a lot of stuff we disagree on these days. |
|
Microservices, on the other hand, are an effective way to burn engineering resources on something that feels like productive work but delivers no business value. I wouldn't infer much about the merits of tech stacks based on that experience.