Orgs get what they measure for. If your team values that sort of interactivity and support, it will ... observe it, measure it, and hire for that sort of person. I've seen groups evolve towards that, and they've been great, but it doesn't seem to be a default - most groups/orgs have to work towards it and and keep working at it.

Having got back in to some WP in the last year, the big thing that struck me compared to other framework/environments is... no... build step, or even plugin/module install step. Files are just there in the document root, accessible by default - the logic files are invokable and the asset files are reachable. Most other php frameworks will install a plugin/module outside the document root then have some sort of publish/install step that will copy assets to be publicly accessible as needed. No plugin logic files would be invokable directly from a URL. That one change would make a big difference, imo, but seeing so much of the last 15-20 years of WP involves helper functions to assumed paths, and default assumptions about assets and logic living in the same paths... I'm not sure the ecosystem could adapt or support an alternative approach at this stage. Might be wrong. It's taken me a while to put my finger on why the current situation encourages less-secure-by-default systems, and this is probably the biggest thing I've landed on. There are other issues, but these issues all help contribute to WP popularity in the first place...

They may end up believing they are being impacted, but many will still deny or argue the root cause.

If our tariff structure went back to, say, October 2024, and companies who'd paid some inordinate tax - forcing layoffs and reductions - got a chunk of that back - and the taxes went back to what they were - there'd likely be some return to hiring and raises as before. But we can't get back to that any time soon with an administration hellbent on extracting as much from us via tariffs as possible.

Delayed refunds won't even start to repair the damage done by bankruptcies triggered by high tariffs, the snowballed cost of tariffs impacting multiple steps in the supply chain, the emotional toll on families and communities having to deal with less money and rising prices. But rehiring and getting some regions and communities back to work might be a step in the right direction.

EXCEPT WE NOW HAVE A 15% GLOBAL TARIFF ONGOING. And a lunatic administration that will fight tooth and nail for years to keep this going as long as possible.

Trump "loves" this country so much it hurts me.

Country AND Western!

I didn't read that as you need to be spending $1k/day per engineer. That is an insane number.

EDIT: re-reading... it's ambiguous to me. But perhaps they mean per day, every day. This will only hasten the elimination of human developers, which I presume is the point.

When it came out, Github Copilot was an autocomplete tool. That's it. That may be what the OP was originally using. That's what I used... 2 years ago. That they change the capabilities but don't change the name, yet change names on services that don't change capabilities further illustrates the OP's point, I would say.

If the comment was

  // We match them by looking for equal-opposite amounts within an X-day window defined by BANK_TRANSFER_MATCH_WINDOW_DAYS

If it's on a screen in a browser, probably. If it's printed, or on a display not under a reader's control, probably not.

FWIW, I'm partially split. I generally prefer sans-serif overall - have for decades. I think I slightly prefer serif for some printed material visually, but... when I actually have to engage and read it, for long periods, I think I tend to opt for sans-serif. Noticed this on my kindle years ago, and kindle reader now - I usually swap to sans-serif options (I think it's been my default for a while).

Can he read? No doubt he can read some. I can't say he's illiterate. But functionally, he's nowhere near the reading and comprehension skills of what we should expect from a national leader.