Comments URL: https://news.ycombinator.com/item?id=47347293

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46673288

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46563526

Points: 1

# Comments: 0

The more I look into these systematic changes the less sense it makes.

The complaint isn't that logistics should follow Moore's Law or that we need same-day delivery for everything. It's that we're paying more for objectively worse service than we had a decade ago. Services aren't "adapting to consumer needs", its just objective decay being masked as optimization.

The Lettre Verte example actually reinforces the point: service got slower, then slower again, not because physics demanded it but because maintaining the previous standard became inconvenient. The dedicated sorting train wasn't decommissioned because trains stopped working; it was decommissioned because the institution decided the mail didn't matter enough to run it.

Nobody expects sea transport to break the sound barrier. But when 73% of consumers experience an outright delivery failure in a three-month period, that's not bumping against hard physical limits. That's drivers marking packages "delivered" that weren't, because lying clears the route faster. That's solvable. We're just in a system that doesn't incentive fixing it.

The asymptotic argument would land if we were approaching some theoretical maximum. We're not. We're sliding backward from where we were, while costs rise. I'm not asking for magic, I'm asking where went the reliability we already had, at the prices we're already paying.

Comments URL: https://news.ycombinator.com/item?id=46549105

Points: 66

# Comments: 60

Comments URL: https://news.ycombinator.com/item?id=46536681

Points: 2

# Comments: 0

I like the idea of its spec docs and steering format but found it very underwhelming to try and use them, often they caused more confusion of the AI then functional code.

But even before LLM coding, I had team members walk into its numerous footguns - especially around public buckets and bad firestore rules. How many of these stories are really to be blamed on the AI tooling, and how many could be blamed on the very poor default settings of Firebase?

Remote: Yes

Willing to relocate: Yes

Technologies: JavaScript/Node.js/Deno/Bun, Vue.js, Go, Docker/Podman, HashiCorp Nomad, GCP/Vultr, CloudFlare Workers, Firebase, SQL/NoSQL, Grafana/Prometheus/Loki, Ansible, CI/CD

Résumé/CV: https://lagomor.ph/cv.pdf

Email: [contact email from website]

DevOps Specialist & Technologist with 7+ years experience.

Hyper-functionalist design philosophy focused on building resilient, long-lasting tools.

Extensive cloud platform experience (GCP, Vultr, others), backend expertise in containerization and orchestration, monitoring stack proficiency. Strong automation and CI/CD background.

Working as a consultant currently. Built systems for radio stations, music venues, payment processing.

Previously in EdTech.

Comments URL: https://news.ycombinator.com/item?id=44707569

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=44370443

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=44323273

Points: 6

# Comments: 0

The idea for the article was to make a real example of logical equivalence, as books on the subject stay pretty abstract. - like others have mentioned, in the real world there are smarter choices to be made.

Thanks.

The issue was that for some reason, different types of code had different font size settings.

Comments URL: https://news.ycombinator.com/item?id=43335586

Points: 48

# Comments: 14