Realization of the day: I’m not actually driven by money. I want comfort and to provide for my family, but I don’t care about Ferraris or flexing. What I’m really chasing is status through trust. Being widely known, being respected, having access to other respected people I can directly exchange value and collaborate with.

I talk to AI like I talk to a human. I don't expect it to know the nuances of what I'm building, so I give it all the context it could possibly need. My job is to extract the context. That's my job.

If your identity is a skill, AI is a threat. If your identity is solving problems, it's the best tool you've ever been handed.

AI isn't going away. Not saying that as a hype guy, I just don't see a single sign pointing the other way. So what's the game plan? Sit there and go out of business? It's speeding up, getting better, and getting easier.

Hot take: every side of this AI shift is coping, and it's the same identity crisis in two different outfits. Devs lost control of the syntax, so now the defense is "that's not good code." The drag-and-drop crowd spent years dunking on Wix and Squarespace people for not being technical, and now that the work asks THEM to get more technical, a lot of them just don't want to. I sit right in the middle and catch shit from both sides 😂 Chapters: 0:00 - I'm going to piss everyone off 0:33 - Today I learned to update my packages 1:51 - The cope on every side 2:31 - It's an identity crisis 2:54 - Developers lost control of the syntax 3:42 - Humans were writing slop too 5:39 - The second group is worse 6:53 - What I see in the WordPress groups 7:21 - Stuck in the middle 9:18 - They used to make fun of Wix 9:48 - What technical means now 11:06 - I care about outcomes 12:17 - This isn't going away 14:05 - "You're just vibe coding" 15:16 - If you're the best developer alive 17:06 - Who this video is for

Honestly need to completely stop consuming most tech social media. The cope is just out of hand.

Prompting is absolutely a skill. Saying build a website is not the same as handing it a pile of context and telling it what to do. Not enough context and you get bad outputs.

Everyone can build a web app with AI now. Most people skip the part where they know what the pieces are. This is my whole stack for web apps and SaaS: where the code lives, where the data lives, how it deploys, and how I back it up every night. Plus why I'd rather go straight to the infrastructure than pay a wrapper like Lovable to sit on top of it. Chapters: 0:00 - How I build web apps with AI 1:22 - What could you build? 2:35 - Website or web app: where the line is 5:20 - What changes from a marketing website 5:55 - How I orchestrate the build 6:46 - What it's built with 7:39 - Don't build your own logins 8:41 - Where the code lives 9:34 - Where the data lives 11:43 - Back it up every night 13:10 - Where it's hosted and how it deploys 15:10 - Domains and DNS on Cloudflare 16:28 - Integrations: email, legal, and payments 17:26 - Why Next.js and Vercel, not Astro 19:06 - Where the marketing site goes 21:10 - Why not Lovable, Replit, or Base44? 23:36 - Point your agent at this video 24:45 - Want help with this?

🙌🙌🙌

You don't have to use Claude for this. Codex, Gemini, some free model, any of them will run it. The models are just the employees. If three of your five people are bad at the job, the product is worse. That's the whole rule.

Checking in on my @WisprFlow stats...... If you want to never type again -> mjs.link/wispr-flow

Every time I say I build client static websites with AI, the same questions show up. What about forms? What about SEO? Can clients edit it? What about dynamic data? So I answered all of them in one video. How I do it, not gospel. Chapters: 0:00 - Static doesn't mean what you think 1:12 - Where these questions come from 1:46 - Marketing website vs static, defined 3:09 - What about a page builder? 4:19 - Do you really feel in control without one? 6:39 - How do you know the code is any good? 8:10 - Isn't static too limited? 9:54 - Bookings, payments, and logins 11:02 - Can you sell products on it? 11:50 - How do you edit it? 13:41 - Can a client edit it themselves? 16:15 - Custom post types, fields, and taxonomies 18:02 - Does filtering and search still work? 19:18 - Don't you need Yoast or Rank Math? 21:17 - Will it actually rank? 22:18 - What about security? 23:27 - What about updates? 25:04 - What about backups? 27:50 - What about caching? 28:35 - What happens if I'm gone? 30:03 - Want help with this?

The Claude or Codex app is fine. Just don't stay in the chat part of it. Hook your AI into something that can reach your files and run commands, like Antigravity or VS Code. If you work technical, that's where you want to be.

I don't ask humans for help on technical stuff anymore. Not because people don't matter. I still talk to mentors. But if you actually want the answer and you want to move fast, it's AI now.

Played with some new website hero tweaks on desktop and mobile Some cool entrance animations too - markszymanski.co

I don't build websites in a page builder anymore. I don't write the code either. It's all orchestration. I say what I want, it builds it, I check the result. But I still have to know what every piece of the stack does, so this is the whole thing, piece by piece, plus a live demo: one prompt, two changes, live a few minutes later. Chapters: 0:00 - How I build marketing websites now 0:35 - What a marketing website actually is 3:03 - What changed: it's all orchestration 4:15 - How I orchestrate the build 5:16 - What it's built with 8:46 - Where the files live 11:18 - Where it's hosted and how it deploys 15:15 - Integrations 15:46 - What happens when someone fills out a form 17:02 - What about a CMS? 19:04 - Demo: two changes, one prompt 22:30 - Don't sit and watch your agent 26:05 - Checking the result 27:55 - Try it yourself with my blueprint 29:07 - Want help with this?

Thanks Chris.

People keep asking how I actually work with all this AI stuff day to day. So I just showed it. One window. A chat per job. I talk, it does the work. I don't click around in my own dashboard, I tell it what happened and it updates everything. And when I walk away from my desk, every chat comes with me on my phone. Same files, same context, nothing to set up. Chapters: 0:00 - How I work with AI every day 0:38 - Where we are: VS Code 1:52 - The AIOS in 30 seconds 2:51 - This isn't chat 3:51 - Where to start (the Claude Code app is fine) 5:11 - Why I still use VS Code: Codex as the backup 7:37 - My computer never turns off 9:10 - Where the information lives 9:46 - One window, many chats 11:22 - I talk, it does 13:15 - Why I don't click around in Mission Control 15:11 - I check, then steer 16:04 - Owning my own analytics data 17:25 - Working from my phone with Remote Control 20:28 - VS Code tip: hide the tabs 21:27 - Agents open as tabs 21:52 - Bypass permissions 22:24 - The extensions I use 24:12 - What runs without me 24:55 - Google Chat as a remote 26:49 - Get the free AIOS skeleton 28:25 - Wrap up

Realization of the day: The volume actually works. 2 weeks of talking about the same thing, the same way, every single day. Today somebody I never reached out to messaged me, said my AI content has been helpful, and asked what I charge to review what he built. Will he book it? No idea. Doesn't even matter. It's inbound. 🥳🥳

I record every call and every meeting, and almost all of it goes back into my AI system as context. You don't have to take notes when the system takes them, so your energy goes into asking better questions.

Building little AI apps for yourself is great right now. But a $100 subscription hides what that compute really costs, and at the real price that app gets a lot harder to justify.