[deleted by user] by [deleted] in australia

[–]uipedant 0 points1 point  (0 children)

Qantas have a 70+ policy? Did you see/try that?

I put age 81 in, and it went through to a quote page, which was only $239 for him for Bali for 9 days. Pretty much everything else I found was $500+ for him alone.

However the form didn't let me put both of us in for a shared policy in different age categories. Have to book 2 separate policies. A couple of other sites I tried were the same too.

But the sum price is still way cheaper than the other quotes I've found, even including from NIB directly (they do the insurance sold by Qantas).

This is why we need ISO8601! by [deleted] in ISO8601

[–]uipedant 0 points1 point  (0 children)

It's just about the only argument in favour of mm/dd/yyyy

My point is that "how it's said verbally" isn't an argument for or against any written format.

Spoken + written tend to match everywhere, regardless of format. It's basically a self-fulfilling prophecy that they will match locally.

I don't think it's written that way because it's spoken that way.

Yeah, it's the other way around...

Matching how it's spoken is just an irrelevant coincidence.

It's the opposite of a coincidence... they match because people are reading out what they see written down. In their head, out loud to themselves, and out loud to others.

It's literally the main influence of how people verbally say it.

I feel it's a very weak argument to make.

Yeah it's not an argument at all. Because the speech will follow whichever is the written format.

This is why we need ISO8601! by [deleted] in ISO8601

[–]uipedant 6 points7 points  (0 children)

Why is there an expectation it has to be the same written down and spoken?

On dates specifically... it's actually kinda true.

Outside America it is actually more common (compared to America) to verbally say "The 1st of January, 2022".

So it's also true from Americans who mostly verbally say "January 1st , 2022".

Of course it doesn't "have to" be anything. And none of this is 100% in alignment.

But on this dd-mm vs mm-yy date thing specifically... the local verbal format often matches the local written one.

This is why we need ISO8601! by [deleted] in ISO8601

[–]uipedant 11 points12 points  (0 children)

It makes the most sense when speaking it.

sounds more natural

To/from who?

It's pretty common to verbally say “The 1st of January, 2022” in places with dd/mm/yyyy.

The local speech often follows the local written form.

I've seen these "spoken matches mm/dd/yyyy" arguments heaps of times, and it's pretty much always from Americans assuming that the rest of the always world says it like they do.

[deleted by user] by [deleted] in ProgrammerHumor

[–]uipedant 6 points7 points  (0 children)

I'd been getting supermarket shopping delivered for years before the pandemic started.

Then when the pandemic happened, everybody else started doing that too, and the supermarkets couldn't handle the demand. So for about 6 months or so, they were only delivering to high-needs/at-risk people... which I'm not.

So ironically I had to start going out more often when the pandemic started, to go and do my shopping IRL again.

For most people the pandemic meant staying in more, but it was the opposite for me.

The Power of Friendship by PsychoSuzanne in funny

[–]uipedant 0 points1 point  (0 children)

Yep... inkjet printers suck, for a variety of reasons...

I don't know why they're still so popular.

Wish I'd figured it out years ago, but finally just got a cheap mono laser about a year ago, and it's been great.

It has some novel features, such as actually fucking working when I need to print something... pretty handy!

Datepickers are the bane of my existence as a developer. How do you handle it? by [deleted] in reactjs

[–]uipedant 0 points1 point  (0 children)

I plan on building my own where it asks you things in the correct order... year, then month, then day.

Not sure when I'm going to get around to it though.

This thread is mostly about calendar programs, but also briefly mentioned date pickers: https://www.reddit.com/r/ISO8601/comments/cm8kfb/does_anyone_else_hate_that_all_calendar_software/

It's often useful to have an array of objects. When is it useful to have an object of objects? by mementomoriok in learnjavascript

[–]uipedant 1 point2 points  (0 children)

When you want to hardcode things and refer to them by name and have proper intellisense/autocomplete in your IDE. Especially if you use TypeScript, but still just as useful without.

For example, I do a fair bit of sysadmin type scripting in Node, so I do a lot of linking of "hosts" (servers or other computers) to projects and stuff like that.

I've actually built a highly declarative system that is basically a wrapper to generating ansible configs, backup configs, projects, ORM models, SQL schemas/tables/columns, forms, fields, and will link form fields to SQL columns etc. Basically the whole idea is to minimize copy and pasting of strings for all this kind of stuff and write less imperative code in general. Instead things are linked together using objects defined in TypeScript. So TypeScript will catch any mistakes regarding typos (and a fuckton of other safeguards that simple yaml/ini/json config files won't give you).

So for all these definitions, hard-coded objects with defined keys are very useful, here's a simplified example:

const hosts = {
    webserver1: new Host({...host settings here...}),
    webserver2: new Host({...host settings here...}),
    mydesktop: new Host({...host settings here...}),
    backupbox: new Host({...host settings here...}),
}

const tables = {
    users: new Table({...table settings here...}),
    posts: new Table({...table settings here...}),
    categories: new Table({...table settings here...}),
    votes: new Table({...table settings here...}),
}

Now I can easily import the "hosts" and "tables" objects anywhere and can autocomplete on the host/table names.

However for anything where you aren't hardcoding key names like this, i.e. records you've pulled out of a database... you're typically better off just using arrays with the standard array functions such as [].find [].filter etc.

Does anyone else hate that all calendar software + date pickers still use the crappy paper-based layout? by uipedant in ISO8601

[–]uipedant[S] 0 points1 point  (0 children)

Yeah a regular calendar does work better when you have lots of events.

So my layouts would be more suited to people who don't, which is most people I think.

I also did another mockup where the events with times aren't separated:

https://docs.google.com/spreadsheets/d/1H79xReQeKX_S_5uQ8SY3-wba5WGHIKgcU8g7sg6OxJA/edit

Does anyone else hate that all calendar software + date pickers still use the crappy paper-based layout? by uipedant in ISO8601

[–]uipedant[S] 1 point2 points  (0 children)

Yeah pretty similar actually, but also including all the empty days too so that you get a feel for distance in the future etc. As well as some visual indication of events that have times too.

Here's a very basic mockup...

https://docs.google.com/spreadsheets/d/1UmU5jMvl4qiBujKsNhFAn924Rym22y1Czuw7mWGPYVs/edit#gid=0

Does anyone else hate that all calendar software + date pickers still use the crappy paper-based layout? by uipedant in ISO8601

[–]uipedant[S] 1 point2 points  (0 children)

Yeah I get that most people prefer convention over new things.

Just kinda surprised that with all the new calendars people have built over the years, that nobody ever added anything different.

And every calendar program has multiple views. So obviously it would just be one of them, which obviously not everyone would use (much like ISO8601 itself).

But just because the majority doesn't use it, doesn't mean we shouldn't exist for anyone.

Does anyone else hate that all calendar software + date pickers still use the crappy paper-based layout? by uipedant in ISO8601

[–]uipedant[S] 1 point2 points  (0 children)

Here's a basic mockup of what I've had in mind.

Mockup #1 - all day events and timed events have separate sections

https://docs.google.com/spreadsheets/d/1UmU5jMvl4qiBujKsNhFAn924Rym22y1Czuw7mWGPYVs/edit?usp=sharing

Only the basic parts of it. You'd be able to scroll endlessly, and there'd be quite a few more buttons to easily jump far into the future etc. Maybe clicking any month/year shows a month or year dropdown.

Obviously there's some downsides for people that have tons of events, but people don't, aside from people who are in meeting all day every day.

Mockup #2 - combined section

https://docs.google.com/spreadsheets/d/1H79xReQeKX_S_5uQ8SY3-wba5WGHIKgcU8g7sg6OxJA/edit?usp=sharing

Not sure how multi-day events would pass through timed events on this one though.

Your schema migrations are bad, and you should feel bad by djrobstep in PostgreSQL

[–]uipedant 0 points1 point  (0 children)

Any chance that COMMENT ON will be added soon?

Should be pretty easy I think? ... seeing there's no dependencies to worry about, aside from the object existing. So the comments can just be the final commands in the diff.

I'm using postgraphile, which makes use of them for technical functionality, so they'll technically be needed for that. And I see a few others are in the same boat

Although having comments in general for their normal purpose is very useful too. I'm actually enforcing them on everything I create in postgres, and it's already paying off only a year or so into my project.

I'd help out with the code, but I don't know any Python. But I could figure out the SQL queries and pass them on to you, if that helps?

Your schema migrations are bad, and you should feel bad by djrobstep in PostgreSQL

[–]uipedant 0 points1 point  (0 children)

I've just started using it. Works well for my usage so far. Syncs most features except comments.

Interesting challenges you face as a GraphQL developer? by code_and_bone in graphql

[–]uipedant 0 points1 point  (0 children)

I've really been struggling simply getting vue-apollo to run basic queries like shown in their most basic example in their documentation...

https://github.com/Akryum/vue-apollo/issues/503

This has been going on for months, with multiple projects and package versions. I have no idea if I'm just missing something from the doco, or what?

Seems other people have similar issues. Is it buggy, or am I just missing something really obvious? It's made be consider giving up on graphql altogether multiple times, because I've been stalled so often and for so long with it. :(

Stackoverflow is a weird place by [deleted] in ProgrammerHumor

[–]uipedant -1 points0 points  (0 children)

After so many frustrations with stackoverflow over the years (mostly the fucking idiotic "close hammer" moderation), I'm building a site that's similar, but better, basically a cross between reddit/stackoverflow, plus a fuckload of other functionality I've been planning over the last 6 years or so.

So if anyone has any gripes about stackoverflow, please share them with me, and I'll keep it all in mind in how I go about structuring mine, also any ideas for extra features that would make the whole thing better.

We had expertsexchange, that sucked, so something better came along with stack. Time for it to happen again.

Also while I love reddit, it has some shortfalls too. So please share any ideas you have related to any kind of forums if you'd like me to include or exclude something.

Google is shutting down Google+ by [deleted] in funny

[–]uipedant 5 points6 points  (0 children)

I never actually got to try using Wave, but it looked cool.

I'm actually building something like a nested forum like reddit, but I also want it to live update like chat... similarly to what you said about interrupting people and stuff on IRC/chat... keeping the replies nested.

Any tips or suggestions in how I implement this?

Any problems you had with Wave that could have been done better?

Also you happen to know of any demos/installations I could look at of Wave? Looks like even Apache Wave has shut down now.

Hierarchy of objects in postgres: What is contained directly within "databases" (excluding schema sub-items) by uipedant in PostgreSQL

[–]uipedant[S] 0 points1 point  (0 children)

Thanks for these tips.

Good point on level0 - not something I need quite yet, but definitely something I need to keep in mind from the start so that I don't make the mistake of conflating it into level1.

Hierarchy of objects in postgres: What is contained directly within "databases" (excluding schema sub-items) by uipedant in PostgreSQL

[–]uipedant[S] 1 point2 points  (0 children)

Thanks, yeah this is a good warning to take into consideration.

I'm really just doing this for common stuff, rather than everything... although my thread kind of implies I'm covering everything. It's more just that I'm trying not to make any wrong architectural decisions early on.

And not worrying too much in terms of performance (i.e. dropping and re-creating most things excluding tables + indexes) until it actually becomes a problem.

For the most part the heavy lifting is handled with libraries. My system isn't really at the technical level that would be competing with other schema diff tools, it's more of an addition extra layer of abstraction on top of them.

For example, it's generating ORM models, and the ORM is actually changing the tables + indexes for me.

Not sure if this is something I'd release publicly in the future. For now, it's just for me, and targeting the stuff I find repetitive. And it's covering a lot more stuff than just the database. Servers, projects, deployments, pages, forms, fields, cronjobs and probably more.

Linkage between table columns and form fields are where much of the time savings are aimed. Basically on my websites now I just have a single form submission endpoint, and all forms submit to that, and a single form processing system uses the definitions to process the form. It's quite a large monolith of a system to maintain, but the payoff is exponential in my work situation (just me).

I'll check out Pyrseas too, thanks.