Ask AI for the final output and it almost works. Then you need a change, and you rerun the entire thing. I break every workflow into stages where each stage's output becomes the next stage's input. Video looks like this: 1. Write the prompts → QC the prompts 2. Generate images from the prompts → QC the images 3. Generate clips from the images → QC the clips 4. Write the script over the clips → QC the script 5. Collate into the final cut Every gate is a folder. Every folder is recoverable. If the script's wrong, I don't regenerate clips. If a clip's wrong, I don't rewrite the prompt. The system around the AI is the intelligence. The folder structure is the system. The cost of going back becomes the cost of one stage, not the cost of one workflow. Read the deep-dive: https://www.aris-space.com/documents/workflows/every-stage-its-own-folder //A<3

Hello everyone! My name is Bas and I am a 46 year old Dad, Husband, IT Leader, IT Manger, and Engineer by day and an AI engineer, builder and collaborator by night. I have been working with AI for around 3ish years now. I have been “lurking” in the community for a bit and reading comments and interactions, from what I have read I’m really excited to be joining this community. If you ever want to chat just drop me a message and say Hi!

I was going way too hard and staying up way too late and totally crashed on Friday and was out of commission for about 2.5 days.... it's easy to get amped up here and drive yourself too hard to keep up. But gotta remember everyone's journey is their own even if the world seems like its speeding by. If not you may end up taking a detour instead of continuing on the path. But now back in business and gonna try to pace myself a little better..

Before I get to the who and why, I want to say this plainly. Picking a winner this round was genuinely hard. I went through every submission. Pulled repos. Read identity files. Compared rules.md sections. Every entry did real work. A lot of you shipped something I would happily use, sell, or hand a client tomorrow. I can NOT explain to you how proud I am of everyone participating in these, you make this community worth and it and there is SO much potential for the future from just ONE competition let alone future ones. 💼 That part matters more than the prize. The $325 covers a year of Premium and that's great but... The portfolio piece is the real value here. A public repo of a working folder-based AI specialist with a clean README and receipts is a resume line that hiring managers can clone and test cold in five minutes. It is also something you can charge for. If you built a specialist that solves a real problem in a real domain, you already have most of what you need to license it to a peer in your industry, sell it as a service, or package it as a Done-with-You engagement. A few quick notes on that, because most of you did not realize what you actually built and I want to Highlight a few of you: 💸 @Nicolas Patron Uriburu USD Routing Coach AR could be sold to every Argentine indie consultor I know. Same playbook works for any country with FX restrictions. Subscription service, recalibrated annually, audit-pack included. It is a product. 🔗 https://github.com/Nicopatron/usd-routing-coach-ar 🔧 @Jannetje van Leeuwen RAMS specialist is a service business in waiting. Irish signage contractors will pay for this. Same model works for any trade with a regulatory documentation burden. Plumbing, electrical, fit-out, demolition. Each one needs its own folder. 🔗 https://github.com/JannetjeIQ/rams-irish-signage-installer

📝 What this is: A brief warning about AI coding agents eroding engineering comprehension and reviving the cowboy coder anti-pattern at scale 💡 Why it matters: Without comprehension guards, teams accumulate invisible technical debt that breaks systems with no human expert to fix it 🏷️ Tags: ai-philosophy, engineering-practices, technical-debt, ai-agents ⏱️ 2 min read | 🔓 Free Hey Cursor/Claude loyalists – yes, this is from Kilo Code (our open-source rivals). But their take on AI agents reviving the cowboy coder anti-pattern? Unfortunately correct. Let's not let brand loyalty blind us to the comprehension erosion happening in our PRs. I think this is a great article and perspective https://blog.kilo.ai/p/cowboy-coder-is-back-this-time-they?publication_id=4363009&post_id=196901382&isFreemail=true&r=3nz730&triedRedirect=true&utm_source=substack&utm_medium=email