https://t.co/PFrrv0NV29 is all fun and games until Sam & Dario hit us with full-screen ads that must stay in focus for the AI model to keep working...
@MrPunyapal OpenCode CLI + OpenRouter for having access to multiple models. Mostly use it as a pair programmer to validate code I write and to help me find ways to improve performance and learn.
I also use local line autocompletion from PHPStorm
Pretty happy with this setup.
Seriously impressed with the new @laravelphp scale-to-zero startup times. Feels instant ๐
It also only took me 1 minute to upgrade from the legacy compute to the new scale-to-zero compute.
@freekmurze For me, code is a kind of art form... That's why I have a hard time letting AI write it for me. So yeah, personally, it's still really important to me.
Looking for some freelance work as a Laravel developer with 7+ years of experience ๐. Based in Belgium, fluent in English and native Dutch speaking. Active in open source under my own company @outerweb_be / https://t.co/MNsC3oTAHF
@CodeWithDennis@laravelphp I personally don't like to use this. Imagine a scenario where you are deleting the user model. This code will now reference a model that does not exist anymore. Running your migrations fresh on your local setup will throw an exception and so on.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
@dannyvankooten@spatie_be I'm not personally, but I use a lot of their other products / open source packages and they always deliver great quality.
Maybe @freekmurze can hook you up? ๐
@PovilasKorop You may be interested in outerweb/filament-translatable-fields which lets u modify a field using a closure.
Disclaimer: I made the package.
Pretty cool feeling: 2 of my feature contributions just got merged into the newest release of Pest PHP ๐
Feels good to finaly give back to a package I use daily ๐
Thanks @enunomaduro !
@magadum_aniket I personally use @use_bruno . It enables you to commit your collection of endpoints, environments and variables (excluding the ones marked secret) into your project in a .bruno directory. Allowing all developers that clone the project to instantly have access.
laravel/filament tip! ๐
When using the lara-zeus/spatie-translatable package, you can easily sort your Filament table by a translatable attribute using the current selected locale.