Absolutely. I’ve been at it for 20 years and am filling knowledge gaps on a daily basis with AI.
Its not just the “how” either, but the “why” - so I can be an annoying child asking excessive questions again

Of course! Currently marinating whether the things I’ve done to in-app Notifications today was in fact bad

Fair enough - I guess the attribute could take an optional name param / set a sensible default? I need to take a look at the source but sounds interesting!

I’ve never put a lot of thought into routes, just went with file based routing in codeigniter then laravel routing when I moved over.

Attribute routing makes a heap of sense; I wouldn’t be surprised if this became optional in laravel at some point.

How would you share routes with client-side?

Very nice trick! Any thoughts on how you’d update an item in a collection / paginated data?
Would you map over the collection and replace the updated item?

I’ve run a small team ranging from 2-10 people for over 10 years - currently at 7 full stack devs (including me).
Definitely very hard to strike the right balance across skill sets and business requirements.
Strong workflow processes and shared responsibility with stakeholders goes a long way.

This is smart. Thinking back on tests where I’ve done 3+ ifs on the attributes; assert equals is much cleaner 👌🏻

Looks promising 👀

Fair point, I haven’t tried the bom app but WillyWeather is pretty good and has push notifications for BoM warnings.
Also just discovered ZoomEarth which has some great visualisations and projections

Of course this also requires that every date in the db is UTC and the app is writing UTC dates. Basically everything is UTC except for display purposes 🤝

As long as you are casting to a carbon date you can apply any manipulation you need on the app side… +1 for UTC, I’ve never seen a good use case to keep dates in any other tz.

yup i'm a bit on the fence as well, love that it is actually possible to do that, but would prefer to have a php class in ./app that can magically wire up to a vue page / component with a composable or something.

Also generating types for autocompletion would be amazing.

AFAIK no, but having a standardised “Laravel backed component” approach would be awesome. Watching with interest what @aaronfrancis.com is about to demo

import.meta.glob() takes care of discovering all the possible components (for Inertia people, bear in mind Pages are already registered, so don't put the components there).

With the component ready to import, we then simply need to register it with vue.

Example use case: user generated templates

We don’t get any meaningful help from authorities, and hacker capabilities are improving at least as fast as our own.

It’s not like the authorities have abandoned us online, they were just never there in the first place.

I’m not sure I even want them to catch up, but better firewalls would be 👌🏻

I almost never write tests first, but I do introduce them as early as possible and iterate with them.
Main reason: manual testing is slow and unreliable.

The best time for a test-first approach is when changing something that already exists as you can just write a failing test for the change.

I had the same thought… seems like a giant waste of money for a business we have no relationship with. Maybe they think it will keep regional people away from starlink 🤷‍♂️… good luck with that

The hardest problem I’ve encountered in livewire is organising complex logic and readily finding where things are happening, especially when state mutates across multiple methods.

I just love invokable controllers that do one thing well.

I’m sure there are many things I could do better in LW.