I come from Mexico, where millions of people walk and take public transport every day. Unfortunately, poor infrastructure and our mobility culture hurt pedestrians the most. Sometimes people have to wait several minutes just to cross a street. Years ago, a teacher told me that giving way to pedestrians was a simple action to make the world better. It makes a real difference for those who don't have the privilege of being in a car. This stuck with me, and I try to do it whenever possible. It might not apply everywhere with better infrastructure, but I find it to be a small yet meaningful action.

I actually think this project makes a lot of sense. It lets you get started in minutes without dealing with unnecessary details. Furthermore, you can always access the low-level Pulumi component and override whatever you need. Keep doing what you’re doing! Your project makes IaC more accessible to everyone, and that’s a good thing. I’ll be happy to try it.

- https://github.com/binhnguyennus/awesome-scalability

- https://github.com/git-tips/tips

- https://github.com/donnemartin/system-design-primer

- https://github.com/ZachGoldberg/Startup-CTO-Handbook

- https://github.com/pilcrowonpaper/copenhagen

- https://github.com/codecrafters-io/build-your-own-x

Quick question out of curiosity: why does the example include an API key when initializing the logger? I couldn't find an explanation on the GitHub page. Some people might be put off seeing that in the first example, thinking the logger requires a paid subscription.

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

Points: 1

# Comments: 0

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

Points: 3

# Comments: 0

Another benefit: since the docs live in the repo, they’re easy to feed into AI tools.You just drop the relevant Markdown files in as context. This workflow has worked really well for us.

The only real headache was adding auth to our Wiki, but we eventually found a simple solution.

I’ve run into this myself. I tried middleware, AsyncLocalStorage, even wrapping layouts and pages in HOCs. After plenty of research, it still feels over-engineered for such a trivial task. Ironically, my understanding is that Next.js on Vercel already provides a requestId by default.

Another recurring issue is the documentation. The moment you hit anything even slightly advanced, it becomes too simplified to be useful, and the only guidance you find is a handful of open GitHub issues.

* Do you plan to somehow collaborate with local post offices/companies/partners in order to avoid long-distance trips and increase the efficiency of the delivery?

* How will the delivery fee be calculated? Will it be roughly fixed or will it increase according to the distance/remoteness?

If you ever decide to host your blog on a cloud provider, Cloudflare provides nice and simple analytics.