Markizano.NET

Massage Website Updates AI Rant As I work on my massage website I figured I’d share some insights into why I do some of the things I do when it comes to building out the website. AI Has No Sense of DRY I’ve been using coding agents like Claude , OpenCode , Pi and whatever else tickles my fancy to get the job done. I also heavily review and manually edit a lot of this site and fundamentally disagree with just letting agents run rampant on my website and turn it into slop. Let’s take an example from some of my recent commits. diff --git a/shared/massage/types.ts b/shared/massage/types.ts index 9112b14..ef5198c 100644 --- a/shared/massage/types.ts +++ b/shared/massage/types.ts @@ -372,32 +372,6 @@ export interface TherapistClient { > | null; } -/** A booking as the therapist panel shows it. */ -export interface TherapistBooking extends BookingDetails { - _id: string; - client: TherapistClient | null; - soapStatus: SoapStatus; -} - -/** Response of `GET /ap...

Software Architecture and why this is still important in 2026 and beyond. Understanding the architecture and the "why" of your app especially if vibe coded, is still a valid skill in 2026 because you still need to understand what is the overall direction and general function of your app. If you sloppily throw stuff together, the context will rot and you won't know enough to see/say what broke, why or how to reproduce the issue in a non-production environment. So, having certain functionalities like logging, metrics, Microservices , Separation of Concerns , DRY , and other principles are still important and significant for your app. These patterns and principles just makes it easier to debug when things go wrong. AI may be able to type code really fast, but it struggles to keep all that context in mind when your app gets to a certain level. SDLC is also important but I will have a video dedicated to that. Let's dive into some things about architecture that still...