Code with fewer lines is not always simple code.
Fewer lines of code often indicate an abstraction.
Abstractions are not inherently simple; they create the illusion of simplicity.
They don’t remove complexity—they hide it.
This hidden complexity can cause engineers to lower their guard.
Eventually, abstractions leak this complexity to end users in unexpected ways:
Often in the form of performance issues, latency, or high CPU and memory usage.
Deep down, we know this.
Wrap a large block of code in a function call, and the client code appears simple.
But we know it’s not.
Put that function in a library and ship it.
Now, only you know the true nature of the code.
The developers using it don’t.
Those devs build more software and libraries on top of it, creating further illusions of simplicity.
The same applies to frameworks, client libraries, APIs or even languages.
The best performance comes from fully understanding the intricacies and complexities of a system—
And tuning them to your specific use case.
Abstractions are most powerful when we understand what lies behind them.
Use them, but never let your guard down.
Imposter syndrome is like a self recursive function.
For a brief moment, thought “A” is generated claiming “you are not good enough for a task”.
Thought “A” disappears and in its place thought “B” is generated says “maybe that is right”. (can’t have two thoughts at once).
“B” is gone and thought “C” takes its place says “you shouldn’t feel this way”,
“C” is gone, “D” comes in with “Others could do it why not you”
See how all thoughts B, C, and D further strengthen “A”. because they all have thought “A” in them. They all load thought a full copy of thought “A”, bloating the mind.
That is why inherent in imposter syndrome is a recursive thought process. Acknowledging it or denying it further strengthen the imposter feeling.
There is nothing to do but take it all in and let the game rewind.
Slowly getting down to the base condition.
Where the recursive function terminates.
Imposter syndrome is like a self recursive function.
For a brief moment, thought “A” is generated claiming “you are not good enough for a task”.
Thought “A” disappears and in its place thought “B” is generated says “maybe that is right”. (can’t have two thoughts at once).
“B” is gone and thought “C” takes its place says “you shouldn’t feel this way”,
“C” is gone, “D” comes in with “Others could do it why not you”
See how all thoughts B, C, and D further strengthen “A”. because they all have thought “A” in them. They all load thought a full copy of thought “A”, bloating the mind.
That is why inherent in imposter syndrome is a recursive thought process. Acknowledging it or denying it further strengthen the imposter feeling.
There is nothing to do but take it all in and let the game rewind.
Slowly getting down to the base condition.
Where the recursive function terminates.
Meet Laravel Wayfinder — Wayfinder automatically generates fully-typed, importable TypeScript functions for your controllers and named routes so you can call your Laravel endpoints directly in your client code just like any other function. ✨
Available now in public beta.
https://t.co/KyxCGPLLBe
Hey Laravel devs, here's a gem for you! 💎 Clean up your post-query transformations with afterQuery()!
This elegant approach keeps your code DRY by handling model modifications right where they belong.
#Laravel
@taylorotwell@calebporzio Usually. The edge case is like, you have a static-capable closure in memory that "backpacked" out a large variable, and that data could otherwise be GC'd but it won't be, because the closure maintains a reference to it.
This code is the same, except for `static fn`
64× mem use
I finally have a spare moment after all the craziness of @LaraconUS and I just wanted to sit down and say thank you.
Thank you to @taylorotwell and the @laravelphp team for trusting me to be out front.
Thank you to the speakers for being SO prepared and for bringing the heat.
Thank you to the community for continuing to be welcoming, funny, sharp, and optimistic.
And most importantly, thank you to @JenKfrancis for holding down the fort at home while I hang out with my silly internet friends. She truly does the most and never asks for recognition.
I love my made up job. I love playing my part. I love the Laravel community and I'm so grateful to be in it.
Alright, my talks not up yet so anyone who didn't catch it is confused about Flux.
Definitely watch my talk when it's up - but here's a little personal tour from my hotel room this morning
(lots of stuff I didn't show in my talk)
@Rmitesh32 What I do to avoid this error is explicitly return the factory class in the model class.
See this in the laravel docs
https://t.co/f5S1oQ6vXl
We often concentrate on the outcomes rather than the journey, which make our minds always alerted on why we haven’t achieved anything. To be immortal is to live in the present, to forgive the past, and to welcome the unknown with open hands
Laravel Tip ⚡
Ever heard of the "Tell, Don't Ask" principle?
It states that we should not fetch data from an object to do conditional checks upon it, instead, we should ask the object to do that for us.
Added benefits: clear intention, reusable logic & less error-prone code.
🧙 @arnaud_lb has crafted a patch for #PHP that improves #FrankenPHP performance when using @ApiPlatform by 20% with GNU libc and 40% with musl (Alpine Linux). What a wizard!
Of course, this will also benefit many other projects.
https://t.co/dCg6myrrmm