Well Sargeant, it was cool to see an American for a bit. Good luck in whatever comes next, mate.
Getting canned after your home race (speculation) would feel like shit.
There isn’t anything interesting here.
Well Sargeant, it was cool to see an American for a bit. Good luck in whatever comes next, mate.
Getting canned after your home race (speculation) would feel like shit.
Hahaha; I dunno what I expected but this sure as shit isn’t it. Woo… thanks for the morning laugh.
As an FYI to myself: the leaps have not been made.
I would love to have TypeSpec enable support for examples, callbacks, and links. If it added those three, it’d be a total game changer (for me).
My position is one of always design an API first (produce the OpenAPI document of what you want to build) and get buy off from your customers/stakeholders. Then when we start coding, we know exactly what well the end result should be.
Even better would have the ability to do request/response validation via a OpenAPI spec in .NET. Still holding out on that pipe dream (I know it’s available via other languages).
Feels weird to introduce something that’s been around for a while. I’ve been using typespec for about a year. Works well but it needs to make some leaps to match with the OpenAPI spec.
Perhaps I should see if those have been made…
What was the deal with the grass catching fire? Did that get figured out?
TIL. How did that end up? I suppose it doesn’t really matter. He got his shot and he couldn’t perform at the level required. Shrug