Fragile narrow laggy asynchronous mismatched pipes kill productivity
1–10 of 91 posts
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#2> Sometimes a distributed system is unavoidable, such as if you want extreme availability or computing power, but other times it’s totally avoidable.
But so much of our sales pitch involves these shiny cloud systems.
Who ever sold business by telling the customer: "Your use-case really isn't exciting, and a boring batch-driven process is completely appropriate"?
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#3> Sometimes a distributed system is unavoidable, such as if you want extreme availability or computing power, but other times it’s totally avoidable. But so much of our sales pitch involves these shiny cloud systems. Who ever sold business by telling the customer: "Your use-case really isn't exciting, and a boring batch-driven process is completely appropriate"?
I do it like that, it's always met with excitement like "oh wow, all these other companies were telling us how hard and costly and lengthy it will be, thank you"
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#4> Sometimes a distributed system is unavoidable, such as if you want extreme availability or computing power, but other times it’s totally avoidable. But so much of our sales pitch involves these shiny cloud systems. Who ever sold business by telling the customer: "Your use-case really isn't exciting, and a boring batch-driven process is completely appropriate"?
I do it like that, it's always met with excitement like "oh wow, all these other companies were telling us how hard and costly and lengthy it will be, thank you"
Do you ever have the experience of doing a prototype, and the customer looks at it and says: "Great work. Put it into production"?
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#5Failure is such a fun thing to think about, and it gets handwaved away so often. So many devs, architects, product owners, etc, just focus on happy path, and leave failure unspecced, unhandled, and just hope it never happens. And then boast about 99% uptime, but once you start questioning them you find out they get weekly pages they have to go investigate (and really the system is behaving weirdly a solid 10% of the time, but they don't know what to do about it and it eventually resolves itself, and they don't count "pageable weirdness" in their failure metric).
It's actually one of the things I love about Erlang, and how it's changed my thinking. Think about failures. Or rather; don't. Assume they'll happen, in ways you can't plan for. Instead think about what acceptable degraded behavior looks like, how to best ensure it in the event of failure, and how to automatically recover.
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#6See also Peter Deutsch's "Fallacies of Distributed Computing" list (https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu...).
There's some overlap, but also some new stuff. In particular, "pipes" isn't covered by the Fallacies list and is consistently a pain point and/or issue you always face in some way. Also "asynchronous" isn't covered by the Fallacies list.
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#7Earlier quoted context omitted.
I do it like that, it's always met with excitement like "oh wow, all these other companies were telling us how hard and costly and lengthy it will be, thank you"
Do you ever have the experience of doing a prototype, and the customer looks at it and says: "Great work. Put it into production"?
every. damn. time. i'm a freelancer, so there's not a dev team behind me. the client likes what i made, and wants to start using it. realizing this, i've started spending much more time on the UI/UX (even though i'm not one of those guys) to at least make the tool useable in a dogfooding way.
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#8Funnily, I thought the headline was talking about development process, as that also describes how a lot of places (mis-)handle the flow of what get worked on.
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#9[deleted]
Re: Fragile narrow laggy asynchronous mismatched pipes kill productivity
#10Earlier quoted context omitted.
Do you ever have the experience of doing a prototype, and the customer looks at it and says: "Great work. Put it into production"?
every. damn. time. i'm a freelancer, so there's not a dev team behind me. the client likes what i made, and wants to start using it. realizing this, i've started spending much more time on the UI/UX (even though i'm not one of those guys) to at least make the tool useable in a dogfooding way.
Maybe it's not 100% relevant to your case, and maybe you've already seen it, but just in case:
https://www.joelonsoftware.com/2002/02/13/the-iceberg-secret...