American Express Engineering
americanexpress.io · Company blog · on HN since 2017
American Express's engineering team writes about its technology choices, including Go, React, and resilient payment architecture.
What HN saysHN commenters quote it for why Amex chose Go over C++, Java and Node.js, and for its yak shaving and React render-prop posts.
23HN people shared it
4linked it in comments
31stories submitted
402story points
5 months agolast shared
2017people per year2026
Most-shared posts
- 1Yak Shaving: A Short Lesson on Staying Focused (2018)4 people · 182 points · first shared 2022 · 112 comments on HN
- 2Function as Child Components in React Are an Anti-Pattern4 people · 6 points · first shared 2017 · discussion on HN
- 3Clean Code vs. Dirty Code: React Best Practices4 people · 5 points · first shared 2017 · discussion on HN
- 4Choosing Go at American Express (2019)3 people · 105 points · first shared 2019 · 69 comments on HN
- 5American Express Engineering2 people · 10 points · first shared 2017 · discussion on HN
- 6Eliminate the Database for Higher Availability2 people · 5 points · first shared 2017 · discussion on HN
- 7American Express: Cell-Based Architecture for Resilient Payment Systems2 people · 5 points · first shared 2026 · discussion on HN
- 8GraphQL, REST, RPC, Who Cares? Keep a Single Redux Store with Iguazu1 people · 31 points · first shared 2018 · 1 comments on HN
- 9Using Git Bisect to Find Bugs1 people · 22 points · first shared 2019 · 2 comments on HN
- 10On the Importance of Commit Messages1 people · 8 points · first shared 2018 · discussion on HN
- 11GraphQL for the JVM: An Introduction to Nodes1 people · 5 points · first shared 2018 · discussion on HN
- 12Go at American Express Today: Seven Key Learnings1 people · 4 points · first shared 2025 · discussion on HN
- 13Migrating the American Express Payment Network, Twice1 people · 3 points · first shared 2026 · discussion on HN
- 14Support Both Hooks and Render Props with One Simple Trick1 people · 2 points · first shared 2018 · discussion on HN
- 15Spread Love: A Look into JavaScript's Rest and Spread Syntax1 people · 2 points · first shared 2018 · discussion on HN
What HN people wrote when they linked it
vlod · 2024-01-03
From [0] "Based on these criteria, we narrowed our testing languages to C++17, Java, Node.js, and Go. The first three languages were already in use at American Express, whereas Go was not."
[0]: https://americanexpress.io/choosing-go/
pdntspa · 2022-09-07
https://americanexpress.io/yak-shaving/
Pretty much the first result on DDG...
Smaug123 · 2022-04-30
I'm not sure what it means for the one who coined a term to not understand the term they coined. (At https://americanexpress.io/yak-shaving/ they are quoted as stating clearly that they coined it and attempted to spread it. Which need not be true, but if you're going to suggest that it's false, you'll also need some evidence.)
methyl · 2017-11-10
The author claims the article [1] says render props are anti-pattern, while this is not true. The only thing that's called an anti-pattern there is "children as a function". If you use properly named render prop other than children, they seem to be fine with that.
Will be good to correct that since it's pretty confusing.
[1] http://americanexpress.io/faccs-are-an-antipattern/