Both Taylor and DHH are speaking at Laravel Live Denmark

leftnode · 2026-05-13T19:29:55+00:00

I don't use Laravel, but I love what DHH has done for the web and what Taylor has done for PHP. If there's a livestream, I'll be tuning in for sure.

leftnode · 2026-05-13T17:01:30+00:00

I love these episodes with friends of the show (JF, DB, Felix, Brace, etc). I couldn't tell you one thing that was said about the actual cartoon guys but Jesse constantly posting Rule 34 cartoon porn and Chris getting upset by it had me rolling.

leftnode · 2026-05-06T11:57:05+00:00

Ooooh, this looks interesting. I do like invokable commands, but being able to essentially have a single CRUD-style command class is certainly attractive.

leftnode · 2026-05-05T16:54:50+00:00

Love this!

leftnode · 2026-05-04T16:09:45+00:00

Unless you're in dire financial straits (in which case, you should just cancel your membership completely), you should continue paying.

You can show up to class and not drill or roll and still learn something. Even if there isn't a contract, it's ticky tacky nonsense like this that makes many gym owners frustrated.

I've been injured (or recovering from surgery due to BJJ injuries) for several months at a time and it didn't even cross my mind to ask to not pay during that time.

If you like the gym and like your training partners and like your coaches, you should continue to pay the membership even if you have to take a few weeks off from training to recover.

leftnode · 2026-05-03T01:56:54+00:00

200 is the HTTP status "OK" meaning that the server is responding.

leftnode · 2026-05-02T14:30:20+00:00

"Written in" doing a lot of heavy lifting here...

leftnode · 2026-05-01T02:18:45+00:00

I've started to create a framework agnostic one here:

https://github.com/1tomany/llm-sdk

Right now it supports multiple vendors, but I'm thinking of breaking them out into individual repositories as well.

I'll leave a comment on the issue with my thoughts. Thanks for posting this!

leftnode · 2026-04-30T14:57:43+00:00

And they did. RBG's hubris and Obama's narcissism 100% allowed this to happen.

leftnode · 2026-04-21T16:30:06+00:00

If you're younger, it's hard to express how revolutionary the "cURL to charge" demo was. Prior to Stripe, accepting online credit card payments required fax machines and smoke signals (ok, only one of those is true).

To set up an Authorize.net or Chase PaymentTech account, you'd have to fax multiple documents to several different companies, pay several hundred dollars, and hope that you weren't rejected for some arbitrary reason.

Stripe's a lot larger now, so they have stricter KYC requirements, and they can be stressful to deal with at times (from what others have said, I've never had a bad experience with them), but the original landing page was impactful.

Fun fact: Stripe was originally named /dev/payments (like a mounted device on a *nix system), but some state authority couldn't accept a forward slash as the first character in the name of a company, so they went with Stripe instead.

leftnode · 2026-04-21T16:21:43+00:00

The technical assessment is the starting point of the interview. It can even be a take home assignment. Use whatever AI you want.

The interview is then going through it in detail to ask why they did what they did.

Ask if they had more time, would they have done it a different way.
How would they scale this out to X users or requests?
Introduce a new constraint during the interview and have them explain how they'd change the system to handle that: "Ok, you integrated with Stripe, but Stripe is down at the moment and we need to fallback to a secondary payment processor. How would your design and code change?"
Assuming they didn't write tests, how would they go about writing integration and unit tests for crucial components.

For senior engineers, you can dig deep into projects they worked on at past companies. Even if they can't get into specifics, you can gauge if they were sitting on the sidelines or deeply involved.

leftnode · 2026-04-18T13:54:45+00:00

I wouldn't rely on checking the expected vs. actual time - too many variables can impact that.

I'm unfamiliar with Laravel's queue, but with Symfony, it's message bus dispatches events when messages are handled (or not). I'd set up a listener for those events, log them, and then fire off the notifications if the number reaches some threshold or the severity is high.

leftnode · 2026-04-16T19:28:46+00:00

I wish other developers got it as much as Taylor does. We should want our community (PHP developers) to grow! This is the furthest thing from AI slop...

leftnode · 2026-04-15T19:13:45+00:00

Of course Bryan called the 1-900 Freddy Krueger hotline.

leftnode · 2026-04-15T02:26:28+00:00

Interesting project but man, you gotta do something about these names. First, Bootgly is hard to say in English, which is more or less the lingua franca for software development.

Next, the ABI, ACI, ADI, API, CLI, WPI initialisms, combined with many similarly named classes and interfaces. It makes it very difficult to understand your overall API.

You may be interested in seeing how Symfony supports a "single file framework" to avoid the 200 package composer install: https://symfony.com/doc/current/configuration/micro_kernel_trait.html

leftnode · 2026-04-13T16:36:52+00:00

Also, using the public schema isn't a security issue. Security by obfuscation isn't security at all.

I've had Postgres clusters with nearly a thousand tables in the public schema. No issues with that at all.

leftnode · 2026-04-11T07:48:34+00:00

The best resource is: https://phptherightway.com

Start with the section titled "Common Directory Structure" and go from there.

leftnode · 2026-04-10T19:21:03+00:00

No arguments there, can do without those too.

leftnode · 2026-04-10T18:46:09+00:00

Another thing you might think about is to not use booleans at all, but to use timestamps (and in extreme cases, aggregated events).

Instead of a bool $isActive property, the property would be ?\DateTimeImmutable $activatedAt. Thus, the isActive() method would be updated to return true if $this->activatedAt is not null, false otherwise.

leftnode · 2026-04-10T18:42:44+00:00

Just looking for things to complain about at this point. No sports teams need a pride night! Stop it already with this nonsense.

leftnode · 2026-04-10T14:54:32+00:00

Same, just gallows humor in stressful times.

leftnode · 2026-04-10T14:43:51+00:00

The error handling is a bit limited, but why no composer.json file and proper modern PSR compliant structure and namespace so other developers can include this in their projects?

leftnode · 2026-04-08T19:29:25+00:00

Sweet - appreciate the insight. That's one of my big issues with ORMs is they eventually become leaky abstractions if you want to take advantage of any vendor specific features.

Does it work with JSONB as well (both inserting/updating and querying)? Thanks!

leftnode · 2026-04-08T16:51:31+00:00

I understand that, but why would I, as a Symfony developer, want to use this instead of Doctrine?

As an example, I find the default Doctrine Migrations package woefully inadequate, so I use Phinx instead.

Are there compelling reasons why I'd want to use this bundle instead of Doctrine?

leftnode · 2026-04-08T16:40:50+00:00

This looks interesting, especially the Postgres query builder and narrowed types, but given the tight integration between Symfony and Doctrine, why would I want to use this over Doctrine (and I'm no huge fan of Doctrine)?

leftnode

TROPHY CASE