Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:

I can get behind that

Ohh the “what time is it in films” argument is good, haven’t heard that one before, thanks

It’s gonna get much worse when you start to try mapping days of the week onto the new times. Are days gonna be the same everywhere as well, to stay from 0 to 24? If so, have fun saying things like “Let’s find a time on Wednesday/Thursday”. People likely couldn’t be bothered and would probably just use the day that their normal wake-up time falls on to mean the full solar day instead. At which point you could also just say okay, weekdays are still following local solar days. But now what weekday is it halfway around the world? Now you need to look up their solar day.

All this to say - abolishing time zones will introduce the reverse problem for every problem that it seemingly solves. You can’t change the fact that our planet rotates and people in different locations will follow different schedules. Turning the lookup-table upside down is just a cosmetic change that doesn’t remove the situation that’s causing the confusion. I’d rather just stick with the set of problems that we’re already used to dealing with.

No

Yeah, but by generating with AI you’re incentivized to skip that initial research stage into your own code base, leading you to completely miss opportunities for consolidation or reuse

There are some cases though where the code is just complicated for reasons outside of your control, in which case “what” comments are good - but they should never be taken at face value, but only used as a first step in understanding the code. There’s a significant risk of the code not actually doing what the comment says.

Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?

I’m not talking full blown ORM here, not a fan of those either. I’m talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I’m coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.

As the other commenter said, the Jetbrains IDEs do this perfectly fine. Although I’d also argue that if you’re working with SQL from within another language already, a DSL wrapper is probably gonna be the better way to go about this.

Well then use all-caps keywords whenever working on those systems, I don’t care. But an edge case like that shouldn’t dictate the default for everyone else who doesn’t have to work on that, that’s all I’m saying.

My ide isn’t limited to color when it comes to highlighting, so being color blind generally shouldn’t be a problem. Set keywords to underlined, bold, italic, whatever works for you.

Your other examples I can see, but at least at my work those are rare edge cases, and I’d rather optimize for the brunt of the work than for those. Of course at other places those might be much more of a concern.

I understand it as an attempt to get very basic, manual syntax highlighting. If all you have is white text on black background, then I do see the value of making keywords easy to spot by putting them in all caps. And this probably made sense back when SQL was first developed, but it’s 2023, any dev / data scientist not using a tool that gives you syntax highlighting seriously needs to get with the times

Never heard of that, thanks for bringing it to my attention!

Just gonna leave this here: The coming war on general computation

Not really self-hosted in the typical sense, but Obsidian with the Tasks and/or Kanban plugin synced through a (self-hosted) solution of your choice could work?

Haven’t tried the whiteboard tool in Google keep (didn’t even know there was one), but the Excalidraw plugin for Obsidian should cover almost any whiteboard use case I can think of. A bit more limited but also good is the native Canvas plugin in Obsidian.

That’s fair enough, but it would have been way better in that case to use the correct name, and adding a reference in parenthesis or something for those who are not yet up to date, rather than using only the deadname.

She has come out as a transgender woman recently and changed her name to Emily. I don’t think there has been a lot in terms of official communication around this, but I guess this video from her personal channel sums it up: https://www.youtube.com/watch?v=b-owBhLGaH4

The person formerly known as Anthony goes by Emily now, let’s try and not use deadnames :)