HN user

solumos

621 karma

mail [at] tomhadley dot link

solumos.at.hn

Posts9
Comments279
View on HN

I think it's a bit nuanced, and maybe poorly explained by the original author, but to me, "left-pathers" are always "move fast and break things" to the point that whatever they build really only works as a throw-away prototype, and the effort to architect sensibly is minimal.

"We don't really need to use REST, we can just create some endpoints that have undocumented side-effects. We don't need to abstract vendor calls into a separate class, we can just implement that functionality directly in our endpoint code."

These sorts of decisions aren't actually materially faster, they're just lazier. And maybe that's "a sprinkle of QC"? But it's a lot of unforced errors that don't really save time to implement, and also create a lot of problems later on.

On the other end, with the "right-pathers", you can have people that really try to over-engineer at any opportunity. This is sort of typical of people who have worked in much larger teams. This can mean building out a k8s cluster when you're still a team of 2-3 people, splitting into 10+ microservices, deciding to use Kafka when a simple queue system would work, building out in-house load balancing for dubious reasons, etc.

The middle path is really something that resembles the "Best Simple System for Now" — when I've done this, I think about how I can solve a problem and not have to rebuild it entirely within 12-18 months.

With integers/floats, he's saying it's not opinionated enough. Anything other than integers with minor-unit precision, unless you have a very good reason, is a bad idea. So "floating point is almost a bad idea" doesn't go far enough, and the other alternatives are presented somewhat equally.

The FX critique is saying that it's glossing over a lot of the complexity. I'd say the same is true for the treatment of DE ledgers, and it borders on bad advice (e.g. "Balance is never stored. It’s derived from the movements of money.")

Without regulation, yes. Brokers (i.e. scalpers) will buy up tickets to events and take all of the risk off of TM’s plate, and reprice however they’d like. ~80% of tickets in the U.S. are sold this way. Stubhub has done a great job of lobbying for this since their existence depends on ticket brokers.

Something different that other folks might not have thought of: Robust multi-environment infra deploy scripts that leverage terraform + AWS SSO

I've found that converting stuff that's previously been very ops-cli heavy into very detailed skills has worked really really well.

I use Claude Opus 4.8 + Conductor as my daily driver

This is such an important step forward as we start to understand the 2nd order implications of AI and how it will change UIs in the future.

We used to have to allow + review 3rd party plugins for software so that people could customize it, but when the cost of development is near-0, we can simply hand over the development reigns to customers.

No meaningful benefit? Tell that to the people in emerging economies who now have access to digital US dollars.

Bitso processes 10% of US-MX remittances. 12% of people in Argentina use stablecoins. The shift is happening in real time.

I think it's just explaining the difference between comms/collab being a supporting thing vs the only thing? It doesn't seem intended to be deep to me, but it's a little verbose.

It can make/take phone calls[0], but they need to be prompted on the nature of the call, the data they need, and how to collect it. They can also output the results of the call via API. An AI agent from Masterworks recently called me using this technology.

[0] https://vapi.ai/