I think the lack of ordinal suffixes seems to be an increasingly (non-format-specific) used thing across many date formats and date vernaculars. I still add it when Im saying dates out loud or writing emails (eg "26th January" vs "26 January") because it sounds less mechanical and robotic.
Probably doesn't help that I'm autistic and omitting tiny little details like that give me eye twitches.. Lol
I tend to disagree. The only people I know who use American date format pf mmm dd are either heavily influenced by American culture, media and other sourced like these, or are actually from a country which uses mmm dd date formats. The vernacular that I've experienced over 3 states and 5 cities on the east coast of Australia is "day month".
Anyway, as I said, I'm not here to argue with you. I feel as this thread is just detracting more and more from your point (which I agree with) that Australia day is not a day of celebration.. So how about we agree to disagree on the date format and move on.
Fair enough, although "January 26" is still American date format, not Australian date format.
Anyway, not trying to cause an argument or anything, just pointing out some tips you might like to pass on to the graphic designer and marketing team.
I'll see myself out.
"January 26 15" at the top. I mean, even translating that from American date format, it still doesn't make sense unless the poster was originally made for Australia day 2015..
Again though, nothing against the statement being made, I am in the "Australia day isn't a celebration" camp too. Just a shame the date format isn't Australian date format. It detracts from the effectiveness of the statement by making the incorrect date format the focus, rather than the statement being made.
Never had to because, well, doesn't work here. I'm in one of those many other countries that exist who still have emergency services but use other numbers. 😉
I vibe code from time to time because people sometimes demand quick results in an unachievable timeline. In saying that, I may use a LLM to generate the base code that provides a basic solution to what is needed and then I go over the code and review/refactor it line by line. Sometimes if time is severely pressed and the code is waaaay off a bare minimum, I'll have the LLM revise the code to solve some of the problem, and then I review, adjust, amend where needed.
I treat AI as a tool and (frustrating and annoying) companion in my work, but ultimately I review and adjust and amend (and sometimes refactor) everything. It's kind of similar to when you are reading code samples from websites, copying it if you can use it, and refactoring it for your app, except tailored a bit more to what you need already..
In the same token, I also prefer to do it all myself if I can, so if I'm not pressed for time, or I know it's something that I can do quickly, I'll do it myself.
If this is on Twitter, then it makes sense. That platform is a cesspool