Oh, FFS. The irony!
There's a statement at the top of the file that says `declare(strict_types=1);`. And yet it's happily ignoring a `use` on a non-existent class.
So strict. Much declared. Very enforcing 😆
It was a terrible idea for anyone to do much more than templating with PHP!
Having to deal with a PHP issue in WooCommerce *shudders*
If I'm reading and diagnosing this right, PHP will quite happily let you write `use No\Such\Module;` and silently ignore the fact that there's no such module, as long as you don't try to invoke it?! REALLY?!
Because it looks like my error was from a constructor call that was cached but removed in updated code. Only the `use` wasn't removed. But now it doesn't error.
PHP is an awful language. And modern web apps are awful.
Client: "Well, sometimes we have to break accessibility on our site when it gets in the way of other users."
Me: 🤔
client: We want a site that looks like a trillion-dollar company.
web designer: Say no more.
Hey folks, just got laid off after 4 years with my employer.
I’m a 25y veteran python developer (web, backend, and data processing) with many years of experience working remotely for companies in the US and Europe.
I have the most experience working with web, backend and data systems, and am also be drawn to opportunities to improve internal tooling and web services that give coworkers the information and capabilities to do their thing better.
Chrome's biggest innovation was the short release cycle with a silent unceremonious autoupdate.
When updates were big, rare, and manual, buggy and outdated browsers were lingering for soo long, that we were giving bugs names. We documented the bugs in magazines and books, as if they were a timeless foundation of #WebDev.
Nowadays browser vendors can fix bugs in 6 weeks (even Safari can…). New-ish stuff is still buggy, but rarely for long enough for the bugs to make it to schools' curriculums.