This is the website I created for them — pikolhaus.com. Small start, but officially my first real client project. More to come.

Finally giving my view on JEV in my classic history and fundamentals fashion but... This one is a little different. It's my first time making a fully animated, pixel art video, and I'd honestly love to know what you think of the style. Should I make more like this? I made an ICM that fully automates most of the process i was able to get this video built in about three or four hours. Talk about a fun animation style right? Might redo a bunch of the videos in the classroom with this.

🎁 $1,000 IN EDUBAWARE CREDITS 🎁 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI translator that takes one kind of work and turns it into another kind of work. Same shape in, same shape out, every time. Not a summarizer. Not a writer. A converter with a contract. This week's deliverable is one translator folder that someone could drop into a Claude project, feed it the input it expects, and get back the output it promises. Every time. Without surprises. 🎯 PICK YOUR CONVERSION The conversion is yours. Pick one you do by hand right now and hate. A few sparks to get you thinking: - 📞 Sales call transcript → CRM notes in your team's exact fields - 📝 Long-form essay → LinkedIn carousel, slide by slide - 🎙️ Meeting recording → product requirements doc - 🔬 Research paper → investor one-pager - 🐛 Bug report thread → Jira ticket with repro steps - 📧 Customer email → support ticket with severity and category - 📊 Spreadsheet export → weekly status update - 📖 Interview transcript → case study draft - 🧾 Receipt photos described in text → expense report line items - 📋 Discovery call notes → SOW first draft The more locked-down the output, the better. "Turns notes into a doc" is not a contract. "Turns discovery call notes into a five-section SOW where section 3 is always scope exclusions" is. 🔥 THE ANGLE THIS WEEK Last comp was The Auditor. Every finding cited a provision so a reader could open the standard and check. The comp before that was The Cartographer. Every card cited a file and a line so a reader could open the source and check. The Translator is the same discipline, one more time. Every line in the output traces to a line in the input. ↔️ A translator has three properties that a summarizer does not: 1. The output has a fixed shape. Same fields, same order, same format, regardless of what the input looked like. If the input was messy, the output is still clean. If the input was short, the output still has every field, marked empty where there was nothing to fill it.

This is happening to me all the time now, and either I wasn't catching it before, or something changed. I do realize that this might be operator error, which is why I'm asking for help. Have you been able to wrangle the "hallucinations" which let's just call them what they are, fiction and/or lies. One request: please don't blindly copy/paste outputs if you run this post with AI. I'm not saying don't do that, just politely asking if you could give it a read and if the output makes sense to you, drop it in the comments. Here are two examples: --------------- Example #1 --------------- Had Claude draft this up, and in the process it created a rule for it without me asking. What's frustrating about this is that now I have to read through another markdown file to ensure accuracy and consistency to how I do things, and I still have doubt that it'll even honor the rule it wrote for itself. The admission: 1. What I did. Credited three voice rules to NAME, and wrote that he flagged them in a comment on your Voiceprint LinkedIn post. The comment doesn't exist. I checked his comments feed, his posts, Gmail, Slack, and Skool. The earliest trace is my own /session capture on 8/29, with nothing upstream of it. I can't reconstruct where the name came from, and I didn't invent a story for how I invented it. 2. It happened twice. Yesterday I told you the attribution had reached the public repo. It hadn't. I repeated the session log's "added all three to..." line without opening the file. That second one is the more useful failure, because it shows the actual mechanism: an unsourced sentence in a workspace file gets read as a source by whoever comes next, including me. 3. Six guardrails were loaded and all six missed. constraints.md bans invented attributions by name. Its final scan says every claim traces to a source. Shared rule 0 forces that file to load every EOD run. Root map rule 5 says verify the live system. Digirol bans "I think" and demands a real search before calling a contact new.

@Ry Mac has been absolutely amazing this week! From the continuous engagement to the value packed videos he's been posting, a position well deserved. ⏰ The 7-day clock resets. Next Monday someone new takes the top spot. 🎯 How it works: - 📝 Post things worth reading - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with what others are putting out there The leaderboard tracks all of it. 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying. Amazing value you're sharing Ry, congrats!