Samuel Levy

It's #hottest100 day! Let's find out how out of touch the youths are with good music!

YouTube video by Laracon AU Marty Friedel - The Invisible Developer - Laracon AU 2024

It’s been a year today since I walked on stage at @laracon.au 2024 and opened up about my experiences with depression and anxiety.

Mental health should be talked about.

And with 2025’s conference just days away, a reminder to be aware of those around you who feel invisible.

youtu.be/0kwNx93aha0

I have run into similar issues when working on school systems, classification systems, and systems for events.

Verbs also brings "State" into the list of "Normal things that you can't call your classes"

6. Everyone in the town is far too willing to allow the "children" access to areas that you wouldn't normally, unless your actual job was to observe their actions/reactions.

5. They're always taking one child at a time to experience a "new" thing in a controlled environment. Many of these "new" things should be fairly mundane by their age.

4. Almost every parent has a fairly particular/important job in the town - a lot of medical staff - but they're often seen pulling double duty in completely unrelated roles.

3. Their heads are just way too big. They're bigger than the adult's heads - it's not even close.

2. Shared "imagination"/hallucinations through the use of an odd device that they can use to draw in the air.

Consider the evidence:

1. The "children" are incredibly eloquent for their age, with the ability to describe the effects of complex feelings, only lacking the correct terminology.

After some consideration, I have come to the understanding that #CocomelonLane is some form of "Midwich Cuckoos" type of situation.

In terms of concise code? It's cool and I do it - way better than `throw_if()` or `throw_unless()`

In terms of following program flow? It can be easy to miss the escape hatch, but again... Still better/more readable than `throw_if()` and `throw_unless()`

Disappointing sourdough rye bread.

Lumpy disappointment. The yeast didn't go off properly.

Quick poll for a security friend. If you are a dev:

Do you know what threat modeling is?
Do you do it?
Why or why not?
If so what does that look like for you?

- Yes.
- Rarely, depending on the client and the project.
- Budget, and just the general nature of projects.
- Sometimes security audits, sometimes writing a bunch of reports, sometimes just making sure that there's enough monitoring/observability in place.

Without doubt.

Try `php artisan make:muffins --type=blueberry`

Is #LaravelBakers a thing? #Larabakers? Anyway, I'm half asleep after @laravel.com worldwide meetup last night, so instead of working I made blueberry muffins.

Laravel Worldwide Meetup - April 2025 YouTube video by Laravel

Last night I spoke at the @laravel.com worldwide meetup about the "magic" in Laravel.

And you can watch it now, on YouTube!

www.youtube.com/live/j9dqD9S...

PhD Timeline xkcd.com/3081

Always named routes because that makes things more refactorable. If I want to change the controller that's responsible for a route, I don't want anything referring directly to the controller except for the route definition.

1. LLM-generated code tries to run code from online software packages. Which is normal but
2. The packages don’t exist. Which would normally cause an error but
3. Nefarious people have made malware under the package names that LLMs make up most often. So
4. Now the LLM code points to malware.

CFP for this year's event, held in Brisbane on November 13-14, is now open!

Talks are 30min, and we welcome speakers from home and abroad presenting on Laravel and the wider ecosystem.

Submit as many times as you'd like! Successful speakers will be contacted by May 30th

Sick of people responding to AI summaries of your emails instead of actually reading them?

Try poisoning your email signature with new instructions for the LLM!

Doesn't it mean "You need to separate yourself from your concerns about the code I'm committing, because there's a single point of responsibility - the principal developer - Claude"

I would possibly simplify it to:

:where(h1, h2, h3):not(.reset)

The good thing with :where() is that it doesn't affect specificity.

I'm pretty sure that they call the second one "pairing", and yeah. It's a totally legitimate way to not have to do a formal PR review afterwards.

Outside of any automated CI checks, PR reviews are mostly just a form of asynchronous pairing with more passive aggressive nit-picking.

I'd be more interested in getting mad that you have to write `function` because that part should be pretty clear. Properties start with `$` and constants have `const` so the only thing left in a class definition is functions.

Consistency and being explicit. Adding public marks that you actually INTEND for it to be public instead of forgetting to set a more restrictive visibility.

As a result, other developers who touch your code will have a clearer idea of your intentions, and new devs will be less confused.

Why? There's a pretty long tradition of trying to make meat look and taste like not meat.

Hail Setitan!