FunnyLookinHat

I think it's important to share the difficult / hard experiences of having kids as much as the good ones. I've noticed that there is a huge bias towards only sharing the good moments and white-washing all of the bad as something you can "laugh about later." To be frank, not enough people were honest with me about what it would be like having kids before I had them - and I was incredibly upset when I realized that (several years into being a parent).

I now make it a point to be honest with people when they ask "Should we have kids?" and tell them about how hard it can be, etc. Most importantly, I tell people that they shouldn't have kids unless they would still want to do it if their experience doesn't land in the middle of the bell curve. We tend to romanticize the decision, and expect that everything "just gets even better" with kids. There are all sorts of ways your experience can be less than ideal. Unless you're evaluating your decision with those potential outcomes in mind, you're doing yourself, your partner, and even your future children a disservice.

Anyone else surprised that the download links are plain HTTP without SSL? I know it's a page that in the past I would have typically not worried about securing - but nowadays it's SSL everything or else your browser yells at you.

I really enjoyed Leaving Microsoft to Change the World by John Wood. It's fairly obscure though - I was surprised to see it mentioned here.!

I think you're looking at OTel from a strictly infrastructure perspective - which Cloudwatch does effectively solve without any added effort. But OTel really begins to shine when you instrument your backends. Some languages (Node.js) have a whole slew of auto-instrumentation, giving you rich traces with spans detailing each step of the http request, every SQL query, and even usage of AWS services. Making those traces even more valuable is that they're linked across services.

We've frequently seen a slowdown or error at the top of our stack, and the teams are able to immediately pinpoint the problem as a downstream service. Not only that, they can see the specific issue in the downstream service almost immediately!

Once you get to that level of detail, having your infrastructure metrics pulled into your Otel provider does start to make some sense. If you observe a slowdown in a service, being able to see that the DB CPU is pegged at the same time is meaningful, etc.

[Edit - Typo!]

> And I'm actually quite happy that most Deno projects don't have a custom testing and linting setup.

I feel similarly. The standard configurations (e.g. tsconfig, linting, formatting) and bolts-included tooling (test, lint, fmt, etc.) are what make Deno so great for developers.

I've started using Deno in my spare time for various projects - and it just _feels_ more productive. I go from idea to testing TypeScript in minutes - which never happened in Node land.

> Server authors working on large systems likely already have an OAuth 2.0 API.

I think this biases towards sufficiently large engineering organizations where OAuth 2.0 was identified as necessary for some part of their requirements. In most organizations, they're still using `x-<orgname>-token` headers and the like to do auth.

I'm not sure that there's a better / easier way to do Auth with this use case, but it does present a signficant hurdle to adoption for those who have an API (even one ready for JSON-RPC!) that is practically ready to be exposed via MCP.

Everyone I know who uses Teams does not like it. Is that selection bias based on my personal network of technically savvy peers and professionals, or is it founded in a broader experience?

More importantly, does Microsoft really believe this is a winning product? Are they that out of touch with their customer base?

Came here to recommend Porkbun - I've had great experience with them and so have all of the friends and family I've recommended.

Yeah, the fatigue is real.

It takes much more energy to stop a bad idea / framework from taking root in a large org than to start one.

Caddy is great! But am I the only one who gets frustrated seeing breaking changes in a minor version release? I know semver isn't "the one true way", but it sure does solve a problem for me. I've had too many applications FTBFS or start up on minor (or even patch!) version bumps because they included breaking changes.