Regis Freyd

@djaiss.bsky.social

💻 software engineer working on open source. 🎁 creator of https://monicahq.com and https://getkollek.com ☃️ Montreal 🇨🇦 🇫🇷

Absolutely convinced you do not need Vue or React anymore in most web apps. Alpine Ajax coupled with Turbo, or HTMX, is all you need to keep things so, so simple and easy to understand.

It's impressive to witness all those tech CEO or CTO become basically super far right wing as soon they have success. Like money unleashed their inhibitions. For the worse.

Over the last few months, I've rebuilt my RSS / content reader project call Feedster. It's unique in that it gives users a front page view of their feed content, organizes feeds into channels, allows users to share these channels, and supports MCP for AI agents to access feeds.

Bild

Last week I had to send back the Unifi Express 7. I have both the UE7 and the Dream Router 7 (this one is connected to 1Gbps internet), and Internet works much better at home now that the UE7 is not there anymore. Hope the replacement unit will make it better.

Since I plan to move to Linux full time in 2026 (desktop is already on it, laptop is not), I will not use external tools to automate stuff. I've just setup auto upload of screenshots to GDrive with bash scripts. It works really well.

After using Kagi for a while, I decided it was not for me. Its promise to make search better conflicts entirely with the fact that Kagi uses Google behind the scenes. I've been using Duckduckgo instead exclusively for the last 9 months and it's been amazing. Not using something else. Just works.

iOS 26 will be the last iOS I'll use. I'll wait for my iPhone to die, then never buy from this company again. Same for the laptop. Their software truly are becoming atrocious.

Great library to implement search locally on any content website. It basically indexes your (mostly static) site on build time and gives you a bundle that you include on deploy. There has to be a use-case in one of my projects so I can try it. pagefind.app

Pagefind | Pagefind — Static low-bandwidth search at scale

Pagefind is a fully static search library that aims to perform well on large sites, while using as little of your users’ bandwidth as possible, and without hosting any infrastructure.

pagefind.app

I’ve been a Pro Raycast subscriber for a year, but I haven’t renewed my subscription. If I may use this classic comparison, your product is either a medicine or a vitamin. For me, Raycast is a vitamin.

Since many of my computers are doing nothing at home, they are now running the @foldingathome.org project to help science. It allows you to donate your computer’s idle processing power to scientific research. If all my machines can help, yours probably can too.

Screenshot of the Folding@home web control dashboard on the Machines tab. It shows one machine listed, named “bigdjaiss-4.local,” running v8.4.9 with 8 CPUs. Global counters for CPUs, GPUs, and PPD display 0. The machine is marked “Unlinked.” A progress bar shows 22.8% completion for the current work unit, with PPD at 0. Action buttons are visible: “Fold All” (green), “Pause All” (blue), and per‑machine icons for settings, log, info, and pause/stop. The top navigation includes Machines, Work Units, Stats, Projects, and News, plus a Login button

It's too sad to see that the main people that I love in the Laravel community decide to remain on Twitter, this horribly toxic place. In a heartbeat they could move the entire community on Bluesky instead.

These are a bunch of new CI checks I've added to one of my new project. It's really fun, and also really useful. For instance, I have this check that makes sure all translation files are complete and no translations is missing.

GitHub Actions workflow summary showing five successful checks for a pull request: Check translations, Lint PR title, Profanity check, Static analysis with PHPStan, and Type coverage at 100%.

Alright. To this day, I didn't use Pest because I thought PHPUnit was doing what I needed. Now that Pest has changed the game with browser testing, I have to admit: this is incredible. I've migrated my test suit in a matter of minutes, and I implemented browser testing, replacing dusk. It's SO FAST.

nunomaduro@nunomaduro.com · 12mo ago

Pest v4 is here — now with browser testing! Browser tests that feel like unit tests: Laravel-ready, Playwright-powered, parallel-fast, with smoke & visual regression built in. Discover Pest v4 — and our new website: pestphp.com?ref=v4

🌟 Why I don't use down migrations

Why I don't use down migrations

Every once in a while, someone opens a PR on one of our open source packages adding a `down` function to the migration. I usually close those PRs fast with a thank you and a message “We don’t use down migrations in our projects”. While down migrations might seem like a safety net, they're often a false comfort that potentially creates more problems than they solve. Instead of explaining this in every PR separately, let me share why we don't write down migrations and what we do instead. <!--more--> ## The untested code problem Down migrations are unique in that they're probably the least tested code in most Laravel applications. While features, APIs, and business logic will get tested in most projects, down methods tend to be written once and then forgotten. Think about it - when was the last time you ran a down migration in your test suite? Or verified that complex data transformations actually reverse correctly? Probably you don’t do this. Testing rollback scenarios is hard and often feels like preparing for something that rarely occurs. ## What about new data? The tricky thing about rolling back migrations is that data created after deployment doesn't simply disappear. When you have a busy application, users will interact very fast with your database after deploy. If you've added a new table and users have created records, rolling back means that data has nowhere to go. When you've transformed data from one format to another, the original format might be lost forever. Even seemingly simple changes like splitting a name field into first and last names become complex when you need to reverse them after users have updated their information. ## Keeping code and database in harmony Your application code expects a certain database structure, and when the database schema changes without the code changing too, things can break in unexpected ways. Models might reference columns that no longer exist, controllers could query tables that have been dropped, and validation rules might check fields that have vanished. The complexity multiplies with modern deployment strategies like container orchestration and blue-green deployments, where different parts of your system might be running different code versions. ## Go forward At Spatie, we've embraced forward-only migrations for many years now. When something needs to be reversed, we will first think carefully about the appropriate solution for the particular situation we’re in. If necessary, we’ll handcraft a new migration that moves us forward rather than trying to reverse history. ## In closing The next time you're tempted to write that down method, ask yourself: will this code ever run? Will it actually work if it does? And most importantly, wouldn't your time be better spent making sure the up migration and new code is rock solid? The choice is yours!

freek.dev

I think only sales people think that other humans want to talk to sales. No one, ever, wants to talk to sales. And I do work in a *huge* company who is used to these kind of big vendors. So it's even worse for solo devs. Show us the product.

Bild

I’ve been using Kagi, a Google alternative, for 8 months now and have an annual paid subscription. Here's a short review. Results are great. UX is great. But at the end of the day, behind it's powered by Google. I'll stay with DuckduckGo from now on.

have a buddy who's worth $100mm+ at just 28. here's his salary progression: 22 - $0 (undergrad) 24 - $0 (grad program) 27 - $0 (phd candidate) 28 - $100mm (works at meta and lied about having an offer from openai) follow me for more financial advice

Trying out Laravel Nightwatch. The onboarding is really well done. I absolutely love the Laravel ecosystem. This, and Laravel Cloud, makes us completely autonomous in shipping our projects. This is perfect.

Every new major macOS release convinces me that my current Macbook M1 pro is definitely my last Apple machine. On desktop I've been back on Linux for two years and it's fantastic. The next laptop will be a @frame.work for sure.