Trusted Shops

Ci vediamo domani a Milano!

Absolutely blown away by the feedback from Thursday's Claude Community meetup in Nürnberg 🤯 Here's the thing: in Germany, people tend to hold back on 5 stars unless something really earns it. People here are brutally honest with their feedback, no sugar coating, no being nice for the sake of it. So to see this many 5 star ratings come in? That means a lot. Huge thanks to everyone who showed up, engaged, and shared their experience. The energy in the Claude community here is real and it's only getting started. More coming soon 👀

Have you ever had a situation where a prompt gave an exceptionally good answer? Chance are that there was a semantic anchor in the prompt. Semantic … what? What it’s about and many more we talked with Ralf D. Müller in the current episode of the HMZE - Beyond Vibe Coding podcast.

Highly recommend applying to this if you have a truly exceptional idea! Think "this technology should not exist yet" type idea, because there will be 10s of thousands of applications and only 500 get chosen. Trying to put together a local hackathon in Nürnberg and also Stadt München (together with Dr. Florian Steiner, M.B.R. ) in the near term too.

A day in the life of a Software Engineer once your company has actually gone AI-native: You wake up and check Teams/Slack. A Claude Routine has already posted a summary of what it built overnight. You spend an hour reviewing code, handing things back to the agents that aren’t quite right, and refine / tighten workflows so the same mistakes don’t happen again. (Even this will probably be fully automated soon) You open your ticket board and get a rundown of where your sprint stands. If sprints even still make sense anymore. Daily standup becomes what it probably always should have been: a purely social check-in with your teammates. Planning and refinement? Already done. A Claude Routine has curated and prioritized your backlog overnight. Your PM has built a working prototype of the next feature directly with Claude, handed it off to an agent that turned it into an Epic, and that Epic has already been through a full refinement pipeline before it lands on your desk. Your main job here is to give it your stamp of approval or raise any points the agent missed. You review it co-operatively with your own agent. Everything updates in place on the ticket system. Tickets are written for agents now, not humans. Every time new models are released you rerun your evals and rethink/reorganize your entire agentic pipeline. (This and double-checking code reviews are probably your primary job function now) Designers have mostly left Figma behind. It's faster to prototype directly with Claude and bring the result back into Figma for final tweaks. The agent then breaks the design down into tickets optimized for agentic workflows. And everyone in the company, from engineering to marketing, has at least half their monthly salary allocated in AI tokens to burn each month. If you're not spending it, you're falling behind. The interesting question isn't whether this happens. It’s already possible today. And it's which parts your company is already 6 months away from, and which parts you haven't even started thinking about. Where is your team on this curve? And if you’re curious to know more DM me and let’s chat.

Reading this this morning hit me quite personally. I’ve been down this road before… The result? Hardcore burnout that took me 3+ years to recover from. The past couple of weeks I’ve been seeing non-stop hate on these guys literally working around the clock to solve people’s problems and bring a better service to their customers. Being a Claude Ambassador I’ve had the privilege to speak to Thariq live more than most people and I can tell you he’s one of the most genuine and caring devs I’ve met, even giving us extra time to ask questions when he must be on an insane schedule. I wish people would stop taking for granted what these guys are doing. Wishing everyone a good start into the week, let’s be kinder to each other.

Today I’m launching Famili.one Famili.one did not start as a startup idea, a pitch deck, or a market trend. It started at home. My wife and I have shared care work for years. A couple of years back, I reduced my working hours so that work and family life could actually function together. And like many families, we learned that the hardest part is often not willingness. It is everything around it. Who remembers the appointments? Who knows the contact details? Who keeps track of gifts, forms, clothes, documents, and all the little things that make family life work? That is where so much mental load lives. Not only in doing things, but in carrying the responsibility of remembering, planning, and making sure nothing gets dropped. So I approached the problem the way I approach product work. Understand what is actually missing. Then build it. What we did not need was just another calendar. Or just another to-do app. What we needed was a shared family space. One place for calendar, tasks, reminders, contacts, and documents—a place where responsibility becomes visible and shareable, instead of quietly living in one person’s head. That is why I built Famili. And the part I love most about this launch is this: Famili.one was built solo by me. No team. No agency. No extra development resources. Just me, Claude, Codex, and an AI-native way of building products. A one-person product team, going from idea to real product with agentic development as a true multiplier. To me, that is part of the story too. Famili is about making invisible work visible inside families. But it is also proof of how much one person can now build when product thinking and AI-native development come together. It is live now, and I’m incredibly excited to see where it goes from here. If you have thoughts on mental load, shared responsibility, family organization, or AI-native product building, I’d love to hear them. #Launch #Product #Startup #MentalLoad #CareWork #FamilyLife #AIDevelopment #AgenticDevelopment #BuildInPublic