@GergelyOrosz: I’m leaving this here: but this is what an ignorant take looks like. As devs some of us (now me included) have the habi…
Summary
Gergely Orosz criticizes the developer tendency to trivialize difficult migrations while being sensitive to similar trivializations, citing a five-year estimate for migrating Enzyme to React Testing Library.
View Cached Full Text
Cached at: 08/22/26, 09:27 AM
I’m leaving this here: but this is what an ignorant take looks like.
As devs some of us (now me included) have the habit of trivializing tough migrations of others (“how hard can it be”) but being upset when someone does the same to ours.
This is a brutal migration by hand
Gergely Orosz (@GergelyOrosz): Rofl that both OpenAI and Asana management believed that it would take FIVE years to migrate Enzyme to React Testing Library. What amusing BS!
I imagine it went like this:
Manager: “How long will it take? Give me SOMETHING”
Dev (annoyed): “FIVE YEARS OK?? Now leave me alone.”
Similar Articles
@GergelyOrosz: While impressive, for 99% of companies, justifying a one-off $150K+ spend on a single migration is just not realistic. …
Gergely Orosz comments on the impracticality of a one-off $150K+ migration cost for most companies, referencing the Bun rewrite in Rust.
@GergelyOrosz: If you've been in tech for some time, this should be obvious: Every single "success story" about a rewrite/migration et…
A tech commentator notes that success stories about rewrites and migrations published by companies are half-truths, omitting negatives and internal incentives, and warns that copying them without understanding context leads to disappointment.
@kentcdodds: You can definitely hate performance optimizations based on the amount of data your dealing with
Kent C. Dodds criticizes unnecessary performance optimizations in React, such as using virtualized lists for layouts that the browser can handle trivially.
@mattpocockuk: Anyone who says engineering skills don't matter, show them this
A developer shares a personal journey of 8 months of research with no results, nearly quitting twice, before discovering a path to a universal 2x performance improvement for all modern JavaScript parsers, which took another 4 months to build.
@GergelyOrosz: This post about a QA at Adobe leaving tech after Adobe let him go is go is going viral. The reality is that manual QA h…
Gergely Orosz discusses a viral post about a QA engineer laid off from Adobe after 25 years, reflecting on the long-term decline of manual QA roles in the tech industry.