3 ms·
This is fairly true, except unicorn level. In a unicorn start-up where things happen extremely fast and your valuation skyrockets, it's more likely the code isn
by magic_hamster 4y ago
This is fairly true, except unicorn level. In a unicorn start-up where things happen extremely fast and your valuation skyrockets, it's more likely the code isn't exactly beautiful and tidy.
I understand where the author comes from. You want to use tools developed in company instead of being cut off when you leave.
- asim 4y agoYea like you're part of this club that has exclusive access to something, you contribute to it, deliver value, see it grow and then it's gone when you leave. It exists within a silo and for the better part of a decade that's really irked me but I haven't quite figured out how to solve for that problem beyond doing it in a shared open source repo and a shared platform. I think the issue is it's bigger than any one person and you have to find a way to sell thousands of people on the idea. My starting point was code and now I wonder could I have approached this differently? Is there another path in which this would actually succeed? I'm still trying to figure it out and it's driving me crazy. Next I'll be writing a protocol no joke https://github.com/micro/network https://github.com/micro/network
- papito 4y agoJust basic due diligence about performance and knowing your storage engine can easily get you to and even at unicorn level. Stack Overflow regularly bragged about how their eight servers and a few MSSQL replicas were basically always in a coma, even at peak hours. That's just good engineering. Microservices themselves solve nothing out of the box.