Creating Your First Laravel Package
Pulling the code you keep copying between projects into something reusable.
Pulling the code you keep copying between projects into something reusable.
Catching a missing environment variable at boot rather than in production.
Opening and closing the day deliberately instead of just letting it happen.
Getting the linter to enforce the thing you keep repeating in reviews.
Type safety from client to server, with none of the code generation.
Moving a lot of data without your process quietly running out of memory.
First-party WebSockets in Laravel, without reaching for a third party.
One codebase serving many customers without their data getting mixed up.
Building a narrow assistant that knows your workflow rather than everything.
Moving the tedious jobs into the CLI, where they were always meant to live.
Use Dataview queries to automatically aggregate daily notes and completed tasks into a weekly review.
Letting a bot take the boring first pass so people review what matters.
Small atomic notes that quietly compound into something genuinely useful.
Validating at runtime so your compile-time types are not a comfortable lie.
Sending events to other people’s systems and coping when they are down.
Getting a model to answer from your documents instead of inventing things.
Letting other people extend your code without it descending into chaos.
Blocking ads at the DNS level and doing your own recursion while you are there.
Keeping track of the people you care about without paying monthly for it.
Give Claude direct access to your local notes folder using the Model Context Protocol.
Jellyfin and the *arr apps wired together so the library looks after itself.
Using Yjs so your app carries on working when the network does not.
Getting slow work off the request cycle without losing any of it.
One page that tells you whether everything in the house is still up.
Terminal UIs in React with proper command parsing.
Start typing to search...