Bill Weinman

uncannyuse now has schema pages for Reality Composer Pro components—showing the exact USDA block RCP writes, field-by-field with types and sparse-authoring behavior, plus annotated fixture examples. 20 components covered so far. https://lnkd.in/dpsT2A-8

9

Here's Savannah's first feature in Typer 😎 Suggest commands on error 🙋 Available in Typer 0.20.0 just released 🎉 Read the new docs: https://lnkd.in/d5EtK-9P

365

10 Comments

Web editors shouldn't waste time wrestling with HTML — they should be busy bringing great stories to life. At Smith College, we completely flipped the Drupal experience: 🌟 Editors create visually, joyfully, and in real-time — without developers, HTML, or CSS. 🌟 Content workflows now rival the best consumer-friendly platforms (think Wix and Squarespace), giving editors total creative freedom and control. 🌟 The real innovation wasn't technical — it was strategic. We replaced gatekeepers with trust. Editors went from frustrated to fearless. When you trust your content creators, your website transforms. 👇 Learn how Smith College editors became passionate advocates of their website — and #Drupal: https://4ktch.in/smith #DrupalRevolution #ContentStrategy #EditorExperience #DigitalTransformation #HigherEdWeb

48

4 Comments

If your audience can't do something useful with your product in less than 10 mins, you are at a significant disadvantage. No amount of DevRel will fix this.

4

Software development is shifting so fast. Agent swarms are no longer a “watch this space” area, officially now mainstream in Anthropic.

1

My only mostly unedumacated take on #ViVE vs. #HIMSS press release volume is that waiting until HIMSS gives you one more two-week sprint. I mean, yeah, the audiences at and purposes for the events are different, but pretty much every software developer I know would prefer one more sprint to one fewer sprint, and if you're gonna talk about new stuff, you might as well give yourself juuuust a bit more cover.

6

Have too much fun on your podcast, you do. Yes, co-host Bradley Shimmin and I have no problem mixing fun, tech, cultural references, and commentary into every episode of the Agents of Dev podcast. Ep 8 is no exception. At the risk of being left behind, languishing in the shadows of the open-molt-clawdbot controversies and the run on Apple Mac Mini inventories, we delve into why Clawdbot, then Moltbot, and now OpenClaw lit up the AI, agent, and software development airwaves in a matter of a few days. Yes, it's open source. Yes, it shows how powerful a vibe coding tool can be in the hands of one person with a creative idea. And yes, it shows both how easy it is to create software that is entire unsecure but will spread across the internet anyway, passwords, prompt injection, and a dozen other security issues be-damned. We also talk about the issue of agents and memory, and the interesting, yet simple, ways that OpenClaw handles this. This one open source project has many, many lessons we are already learning from it, and I predict OpenClaw will be teaching lessons about AI agents, good and bad, for a long time to come. That's why you should listen to this episode. (Yes, I buried the lead!) Links to Agents of Dev Ep 8 are in the comments below. Thanks for listening, watching, following, and sharing with your friends. The Futurum Group Techstrong.ai

22

1 Comment

After 20y of building engineering teams, Claude Code has started to mess with my assumptions. What if our next engineer wasn’t an engineer at all?!? Vibe coding is getting really good, and it’s only going to get better. If we skate to where the puck is headed, the hardest part of building software won’t be coding anymore. Boris Cherny from Anthropic recently said it well: “Coding is relatively solved.” So what’s left? The elusive search for product market fit. (The tough stuff) The hardest problem for a tech company has always been figuring out what people want to have built and making sure it’s actually good. Coding used to be the bottleneck, but not for long. The next bottleneck is product judgment. - Roadmap vision - User experience - Understanding the customer So what should the team of tomorrow look like? This sent me back to Team Topologies (Circa 2019) by Matthew Skelton and Manuel Pais, a framework that breaks organizations into a few types of teams: • Stream-Aligned Teams Teams aligned to a flow of business value • Complicated Subsystem Teams Teams building the “special sauce”, like AI model tuning • Platform Teams Teams responsible for internal infrastructure • Enablement Teams Teams that help other teams become more effective Stream-aligned teams is where the game is played. PMs make specs, and engineers implement them. Progress is gated by engineers and coding. But Claude Code (and Codex etc) changes this equation. PMs wrote specs so engineers could understand what to build. Now those same specs can be read by an agent that can implement them. I’ve been feeding Claude direct JIRA tickets and it’s surprisingly good at executing them. Which raises a question. If an AI can implement a well-written spec, do stream-aligned teams actually need to be engineers? As execution becomes commoditized, the real scarcity shifts to understanding the problem well enough to define the right solution. Which makes me wonder if "stream-aligned teams" might increasingly look like people closest to the customer and the problem: • product managers • designers • customer success • marketers • operators When Claude Code becomes the implementation layer, Software Engineers don’t disappear. Their role just shifts. Instead of writing every feature, they become the enablement layer, defining things like: • architecture and guardrails • engineering standards • design systems • product principles Once that layer exists, something interesting happens. A lot more people inside the company can build!!! We activate people’s insights faster, vs having them wait in line. Imagine a world where a support specialist can file a bug and fix it right there! Product-minded engineers will still rock great features, but they will have friends in the trenches. Engineering doesn’t go away. The job shifts from making things, to enabling people to make things. So what if our next engineer wasn't an engineer at all?!? Game on at Arbor - content at scale

510

105 Comments