Many users appreciate the reminder that tech rewrite success stories omit key negatives and internal challenges, while some dismiss the stories themselves as pure fabrication.
Based on 3 visible X reactions from 35 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@GergelyOrosz The success always share the positive side of the story and talk about the negative when asked or wants to motivate the youth. Every level to success is a battle. We have to know that so we don't give up.
@GergelyOrosz haven't been in the industry long enough to have seen this play out myself, but it's a good reminder to read case studies with a little skepticism instead of taking them at face value
@GergelyOrosz Half truth is optimistic case. Many of the are just pure BS
If you've been in tech for some time, this should be obvious: Every single "success story" about a rewrite/migration etc published on a company page is half-truth. The positives will all be true! But those posts will not share all or some key negatives (even ones people observed) "real" alternatives considered... and even if they did, they would not contain: The Incentives + Dynamics The internal, often unsaid incentives that help with faster career advancemement, the internal dynamics that are unique to a set of companies. And without understanding all of these, if you copy this "success story" inside your team/company with different incentives and dynamics, you'll be disappointed.
One example I can talk about: thousands of microservices at Uber. On blogs and conference talks, the postives were all shared. What was not shared is how this was not what Uber really wanted but more a ducktape solution... to survive high growth: https://x.com/Pragmatic_Eng/status/2040887534474117249?s=20
@GergelyOrosz The success always share the positive side of the story and talk about the negative when asked or wants to motivate the youth. Every level to success is a battle. We have to know that so we don't give up.
@GergelyOrosz haven't been in the industry long enough to have seen this play out myself, but it's a good reminder to read case studies with a little skepticism instead of taking them at face value
If you've been in tech for some time, this should be obvious: Every single "success story" about a rewrite/migration etc published on a company page is half-truth. The positives will all be true! But those posts will not share all or some key negatives (even ones people observed) "real" alternatives considered... and even if they did, they would not contain: The Incentives + Dynamics The internal, often unsaid incentives that help with faster career advancemement, the internal dynamics that are unique to a set of companies. And without understanding all of these, if you copy this "success story" inside your team/company with different incentives and dynamics, you'll be disappointed.
One example I can talk about: thousands of microservices at Uber. On blogs and conference talks, the postives were all shared. What was not shared is how this was not what Uber really wanted but more a ducktape solution... to survive high growth: https://x.com/Pragmatic_Eng/status/2040887534474117249?s=20
Many users appreciate the reminder that tech rewrite success stories omit key negatives and internal challenges, while some dismiss the stories themselves as pure fabrication.
Based on 3 visible X reactions from 35 accounts; directional sample.
Ask a question below.
Published answers will appear here.