Full stack web developer currently working mostly with #PHP / #Laravel, Vanilla #Javascript and #SCSS. Love learning more about (almost) anything, but particularly #MySQL and #InfoSec. Currently learning Arabic. Husband, father of two boys, Christian.
@Crell thank you for saying that. I have a number of DTOs with methods and sort of always feel kinda dirty about it, but also feel that the alternative would be worse …
Have you ever stood up, from scratch, a completely new version of your application in a production-ready state?
If you haven't, you should.
You may never need to fully stand up a complete production instance, but what happens if a part goes down like your database, your webservers, or your jobs? Are you prepared for emergencies?
@sarah I had to do this some time last year. Proud to say: it only took us a few hours, in part because we had copious backups and had trained for this. 👍
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
For the first time the #CoSocialCa Mastodon server has started to struggle just a little bit to keep up with the flow of the Fediverse.
We’ve usually been “push” heavy but we’ve started to see some spikes in “pull” queue latency. The worst of these spikes was today, where we fell behind by at least a couple minutes for most of the afternoon.
@mick I haven’t read the entirety of the thread, so forgive me if that’s already been covered, but have you tried defining your workers with different sequences of queues.
That wat you would have 10 workers prioritising the pull queue, but picking up other queues when capacity is available. And another 10 workers prioritising the default queue, but picking up other queues (including pull) when capacity is available.
You could permutate this for some different combination of queue priorities.
Then that first command will process the push queue, after the pull queue has been emptied. And the second one will process the pull queue after the push queue has been emptied. Thus potentially wasting fewer resources.
Got to say: Just been through upgrading an app from #PHP 8.1 to 8.3 and it's really nice and painfree.
Very few breaking changes, and the few that are there are stuff that a sensible person would've addressed a long time ago.
Unfortuantely that means that apart from readonly classes, there are also few exciting new things in there. But I guess these also are just point updates after all…
Almost boring 😉 (Not a bad thing! Stability is also nice.)
@Crell yep I still got scars from when I upgraded my very first ever PHP application from 3 to 5. I was a kid when I started writing that app, so it definitely was full of stupid shit (still is, to be honest: always only ever stuck on band aids - the full rewrite is finally planned for later this year), so the upgrade was beyond hard.
But yeah, since then I’ve learned how to code properly (I think) so upgrades tend to be a lot simpler.
That first experience traumatised me for life though, so I’m still always scared when I start …