Sure :) And I also agree. However we need to face the software we have, not the software we wish we had written.
The gist you linked is exactly why globally changing the calendar that's used in software is really hard. Even if we followed best practices along the way, which we didn't. Because too many programmers believe falsehoods about time, are pressured by their boss to deliver faster, don't care about quality and these days don't even look at the code they generated.
You don't ask where people are after the purge night. You know and you don't want to know.
This isn't meant as an insult, but have you actually worked in software? Because yes of course, the OS keeps track of time with Unix timestamps, but there's a ton of applications using strings, separate fields for year, month, day; etc, etc. Even if all software used Unix timestamps internally, there's still so much display code that would need to be updated. Of course for a real migration both calendars would need to be supported, probably for more than a decade (think: banks, governments).
In fact, I'm working on an application right now that uses/used text fields to store the year of an event. Proper timestamp-based dates exist now, but the migration away from the old field is not completed, because it's still used for ordering. (๐)
And, more re: snek_boi's comment, yes, having 13 evenly sized months would make writing software dealing with dates somewhat easier, but you still have leap years, non-leap leap years, leap seconds, time zones and many more issues that make it hard to deal with dates. So most likely still a headache.
Yeah, I guess having stable weekdays per date would be efficient, however I don't think we should actually go down that road. In general I appreciate that this changes, and be it only so my birthday is not on a Monday every fucking year.
I don't get how using 13 months would fix the naming disparity though. We could also just keep our current system and name the months according to their number, like they do in many Asian languages already. September was the 7th month, but IIRC Julius created a month named after him (correction: Julius Ceasar renamed a month after him. The Roman year started in March, matching the Sept-, Oct, Nov- & Dez- with the number of the month of the year).
Regarding the software, see my reply to DomeGuy in the sibling comment.
The sun will explode. Eventually. Interesting and fascinating, yes. Useful? Nope.
I like the ideas of the Holocene calendar and the fixed one (13 Months). However I think too many software has been written and the costs to globally change the calendar would exceed billions with no real benefit (apart from being satisfying af).
A lot better would be to adopt the Gregorian calendar everywhere in the world, so it's easier to share and coordinate. The business world uses mostly Gregorian dates anyway. And if we're talking about that, I hope the ISO format (2026-03-19) will replace the illogical formats like 19.03.26 or even worse 19/03/26 and 03/19/26.
The post doesn't scream "I'm guessing", it says it.
Can you point me to a study showing babies are racist then?
They will certainly have a harder time judging people by their skin color.
However many racist people aren't actually confronted with "foreigners" a lot. So I guess blind people can perfectly be racist about someone's accent or form racist opinions just by the discourse around them and the news they consume.
Babies aren't born racist, it's something you learn. So my guess is blind people are pretty close to the average, maybe a little less.
Woah, nice! I really like it.
re: applying for jobs
Not criticizing your use to write your CV specifically.
But in general, I wonder where this arms race is going? Companies using AI to pre-filter applications, because they get too many. Applicants then using AI to write their CVs, because they have to apply so many times, because they automatically get rejected.
Basically in the end the entire process will be automated, and there won't be any human interaction anymore... just LLMs generating and choosing CVs. Maybe I'm too pessimistic, but that's the direction we're headed in imo.
Yeah... devs love greenfield projects, but always end up maintaining some legacy code ๐ ๐ฅฒ
I didn't use the Temporal API yet, but I'm excited to try it for the first time.