Samuel Levy
Samuel Levy
@imsamlevy.bsky.social
PHP, Laravel, Livewire, Tailwind, and Opinions!
78 followers32 following83 posts
Samuel Levy reposted
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
Samuel Levy reposted
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.
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...
Samuel Levy reposted
Samuel Levy reposted
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.
LLMs hallucinating nonexistent software packages with plausible names leads to a new malware vulnerability: "slopsquatting."
Samuel Levy reposted
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.
There are two acceptable PR review processes: 1. we went through all the checks, thorough review, and approval processes 2. there were a couple smart people in the room and we said "fuck it"
Samuel Levy reposted
Looks like my Laracon EU talk is live on YouTube! Somehow I didn’t notice. youtu.be/EDlxFQz5kh8?...
Samuel Levy reposted
Samuel Levy reposted
I'm going to share my journey with learning new things, starting with my experiences with Livewire. And of course my personal ramblings and insecurities, but hey, that's natural with me, right? I'd love for you to join in on the conversation! www.martyfriedel.com/blog/dev-dia...
Fun fact: bcrypt does NOT only hash the first 72 chars of a password. It TRUNCATES the input to a maximum of 72 bytes. Which could mean as few as 18 characters, depending on the character encoding. The actual spec says to truncate to 56 bytes, but none of the implementations do that.
Password length limits are often a sign of a legacy backend or insecure hashing, but did you know bcrypt only hashes the first 72 chars? It raises the question, should we be limiting password lengths when using bcrypt? 🤔
It's wild how much of my JS and HTML @calebporzio.bsky.social has actually written for me.
It's wild how much JS and old HTML/CSS I can replace with just Flux...
Samuel Levy reposted
You are up to date.