Forcing Myself to Vibe Code

I’ve noticed two things recently: People’s skepticism of “what AI-based coding is good for” is inversely proportional to how good they are at it. I am skeptical of AI-based coding. So: epistemologically speaking, I think my best path towards having a well-informed opinion about what AI-based coding is and is not good for is to “Get Gud” as the kids would say. kttt.io is my first pass at that. In the interest of pushing my boundaries, I set myself the following constraints: I will write no code. I will read no code. I will lean on the AI for anything I’ve heard people say AIs can be helpful for (thinking through things, requirements gathering, design, debugging, etc) I will avoid, as much as possible, leaning on my decade or two of experience as a software engineer to drive this process. What I built Because I have AI trust issues, I wanted something low-stakes. I’m not ready to let an AI handle auth code sight-unseen, for example. Looking through my pile of half-baked project ideas…