David ten Have

I've added an interactive version of the new C4 model diagrams to the website (link in the comments), allowing you to start at the landscape/context and double-click to zoom-in to the detail. It's built using the Structurizr DSL, and exported as a static website using the Structurizr CLI. Think of it as a lighter version of Structurizr Lite, with no server required.

278

10 Comments

Ok now I feel bad about bashing on Industrie 4.0 a couple of posts back ... 🙈 A German friend just pointed out there's an MIT licensed AAS Repository available for anyone to play with. (AAS = Asset Administration Shell. Basically the thing that will move us from siloed systems to an open ecosystem. Single data entry. Only Once. Streamlined engineering. Maybe the github for industrial engineering ...?) And they have SDK's in Python, TypeScript, Java, .Net and Rust! 👀 Web UI built with Vue.js 💚 And cool demo's for converting old pdf data-sheets to AAS using LLMs 🥷 And all running in Docker 🚢 . (Yes this is unfortunately still special in industry ...) github: https://lnkd.in/gaFanfPa Like and share to create much more awareness for this cool work! 🫵

97

56 Comments

So which models produce HTML that has the least accessibility errors, and at what cost? Mapped it out here (bottom left is the best). This is helpful for understanding which models are most compliant for those with disabilities and do it efficiently. Qwen and Gemini 2.5 Flash lead the pack. Hat tip to Ben Ogilvie for pointing me to this: aimac.ai

53

2 Comments

"Vibe Coding" tools like Cursor, Windsurf are great at getting a prototype up fast, but they’re also the perfect illustration of the Dunning-Kruger effect: the moment where you go from “I built an app in a weekend!” to “Oh… distributed systems are hard.” Everyone’s a 10x engineer… until they meet their first data inconsistency and CAP Theorem issues in production. Here is the reality that every entrepreneur learned the hard way: A prototype is not a product. A product is not a platform. And an app is definitely not a company. High-quality engineers don’t just write code — they build systems that scale, they elevate everyone around them into teams that ship, and companies that endure. AI tools will keep accelerating the start. That's a great thing for the software industry. But turning a prototype into a business? That still takes real product thinking, technical depth, and an all-star teams. Appreciate your great engineers. Especially the ones who say “no” before everything crashes. #Startups #Engineering #AI #VibeCoding #TechLeadership

2,757

253 Comments

What's more useful right now - having a radar pointing up looking for signals from deep space, or having your ear to the ground. When we started building functionality on top of gen AI, the first few iterations were built based on the noise around us. What AI is 'capable' of. What other companies are doing. What investors think companies should be building. What is exciting to us as builders. Essentially noise, and it didn't work. Hardly any adoption. Then, we started to truly listen, and customers told us what we needed to build. Over the last 6 months, we have been building in fast iterations with customers very closely in the loop, and we've seen faster adoption for our AI functionality than we've seen for anything we've built till date. So this is what I've learnt - in a noisy environment, have your ear to the ground. Deep space astronomy with a cluttered sky is a bad idea. Also, great work by our AI team led by Anurag Maherchandani, Kumar Shailove and Avijit Nanda!

38

2 Comments

It’s time for some straight talk. No hype, no press release optimism, no corporate spin. Just two guys with some scar tissue—and a lot of history—talking about what’s really happening in the world of spatial computing/XR. In this episode, I sit down with Kharis O'Connell O’Connell—former design leader at AR headset startup: Meta (the original Meta), Google, and Amazon. Kharis has been in the XR arena since before the game began. From early experiments with Nokia's Point & Find in 2007 to helping define zero-learning-curve design principles at (OG) Meta, he’s seen the promise, the collapse, and the recycled hype cycles firsthand. But this isn’t just a walk down memory lane. It’s a reckoning. Kharis recently left the XR industry. He’s no longer building AR glasses or pitching immersive futures to execs in Silicon Valley boardrooms. And that’s what makes this conversation special. He’s honest. Candid. Unfiltered. It’s the kind of clarity you only get once you’re no longer trying to raise funding or ship a prototype. We cover: - The philosophical vision behind the original Meta and why it failed - Why “zero learning curve” design is mostly a myth - What really happened at Google’s stealth AR program (and why it shut down) - The failure of imagination across today’s use cases (yes, cooking demos again)- Whether Apple Vision Pro was our “iPhone moment” (spoiler: it wasn’t) - How the obsession with technology becomes an echo chamber—and how Kharis broke out - The one big question every builder should ask themselves: Who is this for—and at what cost? This episode won’t give you all the neat answers. But it will definitely give you better questions. And if you’re like me—still carrying a flicker of belief that this tech can nourish the soul, not just the shareholder—then maybe that’s enough to keep going. Full episode + podcast links here: https://lnkd.in/g43gtsJX And if you enjoy, be sure to subscribe! Much more to come on spatial computing, AI, and the future of being human.

32

3 Comments