I've been coming back to social media.

But, I'm taking the reins on blocking myself from doomscrolling.

I've got two vibe-coded (thanks Claude) Tampermonkey scripts for X and Insta:

gist.github.com/nikspyratos/3c5b82d24e835d63419700d26db0e696
gist.github.com/nikspyratos/a340af08e1a72acf76ce981f0900554c

Mastodon is already good with not enabling doom scrolling behaviour. Might do one for Blue Sky as well - that algo feed is better than X, but still far too full of US and other geopolitics.

Otherwise: For Youtube on web, I recommend Unhook.

For Android, I recommend ScreenZen - it can block specifically the short form video sections of Instagram and Youtube.

Is anyone here working with Filament while using a heavily custom UI for it?

It's generally not been recommended to customise the components directly to my understanding - makes updates difficult.

I'd really like to advocate for Filament going forward at my new role, but the biggest barrier is corporate requirements to use a specific UI/Design language, even for web apps that ostensibly would be much better served by being built with Filament rather than by hand with something else.

I'm looking for anecdata on difficulty/ease if building & maintaining with more custom UIs.

Any news on that Laravel VS Code extension 👀

Has anyone here had to fix parallel tests when using RefreshDatabase on a Laravel 11 repo?

I've got a test suite that works fine in normal testing, and in parallel on L10, but in L11 it seems it completely breaks and the seeded database data is not present in the test case.

There seem to be a handful of issues related to this, but none of them have a true resolution and deviate off into other problems that were fixed.
github.com/laravel/framework/issues/52414
github.com/laravel/framework/issues/50790
github.com/laravel/framework/issues/50840

I'm thinking there's an undocumented impacting change when it comes to that trait and parallel tests.

I have a slightly modified RefreshDatabase that starts from a DB sql dump and runs migrations from there, rather than running migrate:fresh.

No one? 🥲

Ended up source diving a bit, and I think the root cause was around cli command argument parsing with Artisan. I swapped:

$this->artisan('migrate', ['--seed' => 1]);

For

$this->artisan('migrate', ['--seeder' => DatabaseSeeder::class]);

Not gonna lie... I might rejoin the VSCode group soon.

PHPStorm is great, but... just feels so sluggish for what I get out of it.

The incoming VSC Laravel extension will likely be a great Laravel IDEA equivalent, and with some decent extension setup and better keybindings VSC can achieve most of the same functionality as the rest of PHPStorm.

Especially if you're used to using the CLI for things like git, tests, etc.

Oh yeah, Zed has been really neat. I've been using it as my Sublime/Atom/VSC alternative when I want a light editor for referencing code while I write in PHPStorm.

Once extension support increases for it, it'll definitely be a good alternative.