maudev

20 years PHP, mostly Laravel. AI writes the code. I decide what ships. The how is in my book (pre-order). Built @minimailerapp.

[maudev @maudevme]

I wrote a book about building a Laravel SaaS with an AI agent doing most of the typing.

It's called The Artisan and the Agent, and explains the method I used to build my own SaaS: Contract, Analyze, Build, Test, Deploy.

You decide what gets built and how it gets checked. The agent does the heavy lifting, inside rules it can read.

The Core Book: 501 pages featuring 130 contextual AI prompts.

The Complete Package: Adds the companion app the book was built on, featuring 31 tagged steps you can navigate via git diff.

It ships on Wednesday 14 October. Pre-orders are open now at the launch price, €59 for the book and €97 for the package, until release day.

A free preview is available to download, no email asked: https://t.co/2SGlymBf5s

[maudev @maudevme]

@rkbdevir7 HI 👋 let's connect!

[nunomaduro @enunomaduro]

coming for php 8.6: clamp function

kinda cool, no more of that min(max( chain we were always doing

[maudev @maudevme]

@itsfazley Hi 👋
I built @minimailerapp in beta now and write a book about building production-ready apps with AI.

[maudev @maudevme]

In many single-page apps, a keyboard user follows a link, the new page appears, and focus stays where it was.

A full page load normally starts keyboard focus from the top of the new document. Client-side navigation only swaps the content, so focus stays on the link in the menu, or drops to the body if that link was removed.

Unless the app moves focus or announces the change, a screen reader user won't reliably be told the page changed, so from their side the click may have done nothing. A keyboard user has to tab past the rest of the menu to reach the content they asked for.

The fix is a few lines in the router. After a route change to a new page, move focus to its main heading, and give that heading tabindex="-1" so it can receive focus. Leave links to an anchor on the same page alone.

It's one of the most common accessibility failures in single-page apps, and one of the cheapest to fix.

Hey I wrote a book 📖
Get your free copy 👉 https://t.co/2SGlymBf5s and let me know what you think in the comment.

[maudev @maudevme]

@1337hero Oh gosh! Memory unlocked.

[Daria @DariaWithAI]

Guys, only 38 new techies to 1900!

💻Founders and solo
💪AI buddies
🐈cats and ☕️ coffee lovers
📰news readers

Lets connect, our community is growing! 🌻

[maudev @maudevme]

@SamVale29 Hi Sam 👋

[maudev @maudevme]

@calebporzio You're a genius and the video is WOWWWW!

[maudev @maudevme]

@rishxwtf Hi 👋

[maudev @maudevme]

If the webhook retry schedule lives in two docs with two different values, an agent will pick the wrong one about half the time.

Then the real damage starts. Once you catch the mismatch, you'll stop trusting the docs and go back to reading the code, which is the work the docs were there to save.

So every fact gets one owning document. The retry schedule lives in the webhook doc, token lifetimes in the auth doc, and every other doc links to the owner instead of restating the value.

The moment you paste a fact into a second doc because it's easier to have it there, you have two versions of it, and every change after that has to find both.

Hey I wrote a book 📖
Get your free copy 👉 https://t.co/2SGlymBMV0 and let me know what you think in the comment.

[maudev @maudevme]

@Chandresh_Vora Let's go go goooo

[maudev @maudevme]

@SuiBuilds Have a great day too 🌅

[maudev @maudevme]

@ayoub_el77927 Here is one more 😉 !

[maudev @maudevme]

@haukejung Hi Hauke! Let's connect!

[maudev @maudevme]

It seems like a good substitute for JEV.

Have you tried comparing it with JEV to see how accurate it is?

If it's a local model, does it also work with low RAM (like 16GB)?

I'm curious, I tried replicating JEV using Bonsai 27B and these are the results (see image).

If you're interested, send me a DM and I'll be happy to share all the details of my experiment.

[maudev @maudevme]

@py_poojaa Be able to read a documentation.

Documentations have always been the holy bible for every developer.

[maudev @maudevme]

@skpnky Communication, public speaking!

[maudev @maudevme]

@jessievbreugel Hey Jessie 👋
Let's connect!

[maudev @maudevme]

@matthias_mrc Sleep 😅

[maudev @maudevme]

@zuess05 Congrats on the first one and keep going! 💪