2021-11-08: https://shopify.engineering/high-performance-hydrogen-powere... ("The future of commerce is dynamic, contextual, and personalized. Hydrogen is a React-based framework for building custom and creative storefronts powered by Shopify’s platform and APIs.")
2025-01-13: https://shopify.engineering/five-years-of-react-native-at-sh... ("React Native has come a long way in the last 5 years and a lot of limitations that led people to not adopt it simply don’t exist anymore. If you haven’t tried using RN in a while, now would be a good time to revisit it.")
2026-09-10: https://shopify.engineering/back-to-native ("React Native was working well for us, and it remains an excellent framework. But since then, coding models have gotten dramatically better, and for our apps and our team, building the same feature in Swift and Kotlin no longer carries the cost it used to.")
Seems a lot like the meme of the new designers pushing a redesign to justify their existence.
To be less dismissive it seems an industry wide problem that big splashy projects get rewarded while the silent “Snow Leopard” mind numbingly obvious just up your quality and fix bugs and UX issues work goes unnoticed.
here is a random example to showcase how this can make sense (I'm not too familiar with the actual stacks in questions):
- stack A needs lots of tedious, not-quite boilerplate not-quite-copy-paste work whenever you implement something, but reduces cross-OS bugs, UX and accessibility issues down the line. Lots of dev frustration, slows down iteration (when humans actually have to do this).
- stack B has awesome DX and affords smooth operation of the design/UX/dev teams, very fast. More issues down the line, though. May be worth it if unaided humans need to work on it.
This is pretty cool, and one thing would really help out a layman like me would be maybe a summary/top-line-conclusions that you found as part of your reverse engineering at the beginning of the post.
Reminds me of artists, how do artists stand out when photography can do better capture of reality (and easier, and cheaper, etc.) than artists can. Artists had to re-invent (or re-discovered, re-focused, etc.) themselves in all kinds of ways like cubism, impressionism, surrealism, etc.
In the end, the criteria remains the same. The engineers that creates products other people would pay for. The engineers that can convince executives to pay them or let them do this and that freely. The engineers that are thought leaders and have wide audiences.
Anyway, at the micro level, I think "How to How" is still important. I believe in developers that can talk about their workflow in detail, how it evolved over time, etc. Really good engineers invest in the workflows of themselves and others. That's my benchmark before and still is even now.
I actually would argue that Hashimoto "left" earlier. He "stepped down" from the executive team July 2021 and became an individual contributor then. He likely lost interest/power a long time before 2023.
In a way, is the author advocating that the best way to get out of the rat race is to win at it?
Also, looks like the author is very different from the typical high school aged person. The author is clearly intelligent and highly motivated, they're also able to maintain good relationships with the people around them (teachers, internet friends, etc.), but if it was so easy, we would see more well-adjusted early graduates of the education system.
Hey guys, I sit next to George who is a real driving force in anything he does, including this one. He's letting me have the upvotes for this one but the GitHub project page is: https://github.com/olafurw/opssat-doom/tree/main
Hey, looking for a source for "about half the US economy is government spending these days". I've searched online for 2023 and I'm seeing a pretty okay 23% for government spending.
2021-11-08: https://shopify.engineering/high-performance-hydrogen-powere... ("The future of commerce is dynamic, contextual, and personalized. Hydrogen is a React-based framework for building custom and creative storefronts powered by Shopify’s platform and APIs.")
2025-01-13: https://shopify.engineering/five-years-of-react-native-at-sh... ("React Native has come a long way in the last 5 years and a lot of limitations that led people to not adopt it simply don’t exist anymore. If you haven’t tried using RN in a while, now would be a good time to revisit it.")
2025-09-05: https://shopify.engineering/react-native-new-architecture ("We successfully migrated two of our largest apps, Shopify Mobile and Shopify Point of Sale (POS) to React Native's New Architecture")
2026-09-10: https://shopify.engineering/back-to-native ("React Native was working well for us, and it remains an excellent framework. But since then, coding models have gotten dramatically better, and for our apps and our team, building the same feature in Swift and Kotlin no longer carries the cost it used to.")
^ to show the timeline of things.
reply