Basically, 80% of sales are still brick-and-mortar. That doesn't seem very depressing?
167 karma · joined December 2, 2024
Basically, 80% of sales are still brick-and-mortar. That doesn't seem very depressing?
The first six words do not scream "human written" to me.
> Rewrite this using ASD-STE100 simplified technical English:
And you get a good-enough result, it seems? Maybe add another sentence or two for guidance, but what's with needing these giant skills, when ASD-STE100 was surely in the training material?
As far as storing a datetime with an associated timezone, I agree that usually this can be problematic. However, for things like weekly repeats, you may want to store broken out components so it handles cleanly across time switch boundaries - e.g. when going in and out of DST. So you'd have `timezone`, `time` (no TZ, no date), repeat schedule (likely using interval, internally stored in months/days/microseconds), and use these to set up your next exact timestamptz value.
Most of these projects made the smart choice to focus on a single or just a small handful of related providers. As soon as you're trying to aggregate, the problem becomes a lot trickier.
> Each card links to the CI pipeline.
Thanks for being explicit, AI written marketing site. Wouldn't have been able to figure that out! Every currently maintained and reasonably popular open source project either runs CI in public or makes the tests extremely easy to run.
The article doesn't say, but did the medley relay/IM become a 4 stroke event around the same time in 1952 when FINA recognized it as a new stroke? Funny to see a 150 yard event mentioned since it seems like such an odd distance nowadays.
I'll let that stand on it's own.
I haven't used a non-laptop GPU in some time, but that is a crazy amount of "idle" power consumption. Is this normal for cards like this?
Don't get me wrong- the rest of this mess falls pretty clearly on Google Cloud, but this one feels like something Railway did to themselves.
The dig in the middle - "you can skip the next part, but if you do skip, are you even a real reader? Not judging. Just saying" - ugh. Why would I bother reading every word if you likely didn't write every word?
Even if you don't use the Tiptap editor, hopefully the idea of a sidecar container is helpful to someone trying to solve a similar problem of allowing Typescript/Node code to interact with Go.
Honestly, really surprised to not see this mentioned til the end. Some of the other things in the article were almost jaw-dropping ($1+ million in instances savings, needing 48 cores to run CI, etc.), but having flakey tests regularly causing you problems, having to rerun extremely expensive jobs, is something that I would argue should have been addressed first, not last.
Can someone that has used Astro and an older static site generator framework explain the pros/cons of Astro in that context?