dan_sbl
Joined 1 year ago
Karma
167
Submissions
33
Member since
Dec 2
Recent submissions
Comment · 2 months ago
Comment · 2 months ago
> SPF record syntax follows one shape:
The first six words do not scream "human written" to me.
Comment · 3 months ago
I took one of the examples ("Leveraging sqlpipe's robust...") and just prefixed it with this:
> 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?
Comment · 3 months ago
I believe a big issue was that significant amounts of parking were closed at each of the host stadiums for "security reasons", fan watch areas, etc. When they did some overhead shots of the stadiums, you could see tons of empty parking lot space.
Comment · 3 months ago
`timestamptz` is probably poorly named. It doesn't actually store a timezone at all - all values are stored as UTC. The underlying storage is 8 bytes and otherwise identical for both timestamp types. However, using `timestamptz` allows you to more easily group by day, hour of day, etc. in a non-UTC timezone when that makes sense. Especially when dealing with summer time/daylight savings time, this can be quite useful.
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.
Comment · 3 months ago
Very similar detailed site for the Chicago L. Here's the signals page, but a ton more to explore as well: https://www.chicago-l.org/operations/signals/signals.html
Comment · 3 months ago
Just an FYI- your "Read more" link under "Seat Reservations" on both pages just leads back to the same page, rather than actually linking to anything offering more information.
Comment · 3 months ago
GTFS is widely adopted, "standardized", but also quite a wild west when it comes to the actual details. I've been building http://mobility-bot.com/ as a spare time project for two years, parsing the alerts GTFS feeds from a handful of providers, and for just about every one of them, I have to do something in the pipeline to clean up the provided data - fixing unicode issues, remapping route and agency IDs, rewriting headers and descriptions to not be identical, etc. You also have to watch and capture the data over time to make sure you have a corpus to generalize parsing and cleanup rules from.
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.
Comment · 3 months ago
Meanwhile, the sad state of intercity trains in the United States, outside of the Northeast Corridor.
Comment · 3 months ago
Billion dollar company can't afford one human copywriter. The future is great! (edit: copyrighter -> copywriter)
Comment · 4 months ago
> The test suites run in public CI.
> 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.
Comment · 4 months ago
> unveiling it to the confusion of officials and competitors in a 150 yard medley race in 1933
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.
Comment · 4 months ago
This feels like what is really splitting the programming community right now- those that have typically enjoyed the journey, and those that just want to be at the destination as soon as possible.
Comment · 4 months ago
> After this story was published Google's spokesperson reached out and asked us to publish a slightly different version of that statement. The new statement no longer stated that "it's critical that we maintain humans in the loop."
I'll let that stand on it's own.
Basically, 80% of sales are still brick-and-mortar. That doesn't seem very depressing?