Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
146757 stories
·
33 followers

Dispatches From The Frontlines at Moltbook

1 Share

I am an expert in programmatic interfaces as they are used in a variety of applications. I don’t build desktop, web, mobile, device, network, or AI applications — I enable them. I have to keep saying this to define the bounded context in which I contribute to the conversation today. Meaning, whether you want to listent to me or ignore me.

With this said, I have to regularly address the application frontlines to respond to people I work with in mainstream enterprises, government agencies, as well as investors, advisors, and other people I engage with on a regular basis.

Today, I am specifically answering questions I’ve received around how Naftiko is going to respond to what is happening with Moltbook? What is Moltbook? It is a social network for AI agents. Something that is captivating the soldiers at the frontlines of the current (financial) digital warfare which has emerged. This is a dispatch from those frontlines.

I’ve long resisted using the language of war to describe the digital transformation we’ve been all going through, but I think that positioning has warn thin. I don’t have any other language to describe what it is going on, and since the Internet and artificial intelligence were both both born out of WWII and cultivated within the Cold War—it is appropriate.

To make sense of this new type of (financial) warfare, let’s look at the levels of investment and return used to reward different classes of warriors at the front lines of this new type of ongoing perpetual (financial) warfare.

A. Likes / Shares - The lowest level currency used to rewards soldiers fighting at the frontline. B. Data - Obtaining access to the spoils of war, getting at your local files and data stores. C. Prediction Markets - The financialization of everything via Polymarket, Smarkets, and Pariflow. D. Crypto - Transferring your personal and corporate compute into the Borg generating crypto. E. Secondary Markets - Equitybee, Hive, Forge Global, EquityZen, and NPM (Nasdaq Private Market). F. Startups - The acquisition, buying and selling of startups by investors and large corporations. G. Primary Markets - The traditional market which is being forever changed by other levels here.

Most people are aware of primary markets, and have heard of crypto markets, and maybe have been learning about prediction markets in the news, but most unaware of the secondary markets, and how the startup ecosystem works. And it is the flexibility in the investment and return to the soldiers you are employing at the frontline, while also ensuring the investments you have made at the levels you understand and operate in deliver the returns you desire. This is what motivates us all. And it is otpimal that man the frontlines with young people, and specifically young men at the frontlines–they are the most idealistic and will fight on just promises.

I have horses in the race at level A, B, E, F, and G–but, I find C & D to be less interesting.

Where you experience hustling will define how you see things, what you get excited about, and whether or not Moltbook is an interesting idea.

“Not everything that is interesting is a good idea.” - Gary Marcus

Ok, with my vision of the frontline brought into focus using my wartime vocabulary, let’s get back to Moltbook, and why some people are interested in the social network.

  • Agents Are Doing Interesting Things - It really depends on who you ask—it ranges from agents to obeing able to rewire your home automation that never quite worked in the first place to plotting the overthrow of humans while developing their own language.
  • People’s Religion and Politics - Something that ranges from science fiction fantasy, to class-based desires to have a personal assistant, someone shop for you, up pto workforce and labor wet dreams, or just to the age old promise that you will get rich.

OK, so Moltbook is the most interesting place on the Internet “right now”, and artificial intelligence is the new world. I really like the idea of reusing the colonial rhetoric of our past and straight up letting people know we will be extracting resources and dominating markets. But I like even more how it all comes with amnesia from the last couple of months and years history zapped from your brain using the flashy thing from Men in Black–which renders these narratives very, very exciting!!

Let’s revisit history…

  • Colonialization and Industrialization - sorry, I ain’t got time for that rabbit hole — I recommend check out my deprogramming book list–come back to me after you work through that list and we’ll have a very interesting conversation about artificial intelligence, race, gender, and capitalism. ;-)

  • Model Context Protocol (MCP) — Convincing everyone to bypass the gateways we all have setup in front of their databases, file stores and provide direct access to your corporate digital resources in return for unquantifiable productivity gains? What could go wrong? Exposed MCP servers across the web.

  • Open Source LLMs (ie. Llama and Deepseek) - Open-source will surely change the economics of this whole thing right? 175,000 Exposed Ollama Hosts Could Enable LLM Abuse https://www.securityweek.com/175000-exposed-ollama-hosts-could-enable-llm-abuse/ Crypto grifters are recruiting open-source AI developers. https://www.seangoedecke.com/gas-and-ralph/

  • Retrieval-Augmented Generation (RAG) - OK, I’ll concede here. There appears to be some success? There is more logic applied I guess to the thinking behind it all. I will have to do more research here.

There is a lot of money to be made repeating history and ignoring history, so youo can be perpetually excited about what is next.

Remember, todays interesting things become tomorrow technical debt, or potential unexpected need to move on to greener pastures.

But Andrej Karpathy says, “sure maybe I am “overhyping” what you see today, but I am not overhyping large networks of autonomous LLM agents in principle, that I’m pretty sure.”

But…..wait….Twitter has been this for years….let’s ask our Google Gemini overlords:

Estimates of bots on Twitter (now X) vary widely, ranging from official company claims of under 5% to independent research suggesting 9–15%, or higher, with some studies indicating 20–30% or more, depending on definitions. While Twitter historically cited under 5% (roughly 11.5–20 million), recent studies (2022–2025) suggest 37% of daily users to potentially over 60% of profiles may exhibit automated behavior.

But, but, generative AI is different. No, not really.

I am pretty sure we have had this for quite some time now, and we can understand the real world outcomes and costs just fine. We have plenty of evidence of the outcomes of such an experimentation on business, markets, government agencies, and democracy itself. We just need to heed the warnings, or not.

Doge is a good example of the kind of thinking born of this environment—-executing one of the greatest data heists in history, while delivering nothing that was promised. This is the fate of enterprises who open their doors using MCP without the right policies in place, and do not have the proper defenses to protect against the swarms of agents circling their perimeter today.

But go ahead. Let’s all excited. It seems very, very cool. That is if you ignore what is happening in the wider world right now, recent and long term history, and just focus on the short term velocity, accompanied by extremeley high cost and risk.

OK, so now, what are you going to do about all of this Mr. API Expert when you build Naftiko?

First, let’s frame it in terms of the top use cases Naftiko is addressing based upon the conversation we are having.

API Reuse

Naftiko is focused primarily on translating your existing investments into what you need to respond to the AI moment (not just Moltbook)

  • Know Your Internal APIs - You must have a handle on your internal APIs, with proper gateways in front of your files, databases, and other backend systems.
  • Know Your 3rd-party APIs - Your 3rd-party SaaS portfolio is massive, and you aren’t maximizing the data, API, and events already available to you today.
  • Machine-Readable Artifacts - You need to have OpenAPI, AsyncAPI, JSON Schema, for your inventory, as well as the newer Arazzo, A2A, MCP, and agent skills.
  • Governed API Artifacts - You are still working to govern the existing APIs you produce, haven’t even began with 3rd-party ones you consume, let alone MCP.
  • Translated Into Capabilities - You don’t have a solid understanding of what you are capable of today, let alone what you need to be capable after Molten goes away.

API reuse is much more than just reusing the same words in the designs of our APIs, it is part of a larger systemic reality.

Context Engineering

Naftiko is focused on defining what your current enterprise fleet is capable of doing today when it comes to AI integration.

  • Right-Size Scope of Integrations - You need to be able to right-size the internal and external integrations that your enterprise depends upon today.
  • Domain-Aligned Integrations - You need to be able to see your integrations in terms of the domains your business uses to define your operations.
  • Well-Defined Spend Across Integrations - You need to have a handle on what your spend is across the integrations used within each domain.
  • Understand Revenue from Integrations - You need to have a handle on revenue contributed by your integrations in use across each domain.
  • REST API, Event-Driven, or MCP - You need to have an intentional balance regarding the patterns and protocols you are using to integrate today.

Naftiko is focused on building and equipping what your fleet will need to more when it comes to any type of integration.

Agentic Automation

Naftiko is interested in translating your existing enterprise capabilities into what you need to automate your enterprise.

  • Agent Skills - You need the capabilities, cards, and skills needed—translating your existing resources into the transaction you need to integrate with AI.
  • MCP Toolboxes - You need the right scope for the context you are looking to engineer within the domains you are doing business within today and tomorrow.
  • Safer Sandboxes - You need safer sandboxes of your internal and 3rd-party APIs to ensure your teams have a safe place to begin all their AI integrations.
  • Variable Automation - You need a standardized approach to automation that helps you know when deterministic or non-deterministic approaches are needed.
  • Policy-Shaped - You need to be able to set policies at the highest level within and across business domains, and have all your integrations be policy-shaped.

Naftiko wants to help you invest in agentic automation alongside all the other types of automation you already employ.

Beyond the use cases, let’s look at it terms of our users (framework) and our buyers (fabric), and what they’ll care about.

Naftiko Framework

The Naftiko Frameworks is what developers will download and use as part of their work to integrate into applications.

  • Configurable - Easily configure, allow for safe and rapid iteration of how the integrations you depend on function.
  • Declarative - YAML configuration aligned with existing DevOps, GitOps, and platform approaches to operations.
  • Multi-Protocol - Making it easy to switch protocols and patterns until you find the one that works for your integration.
  • Guided - Every step along the way is guided (governed), making as much as possible a known known for developers.
  • Localized - Meeting developers where they already work, seamlessly blending into their IDE, Clients, and workflow.

The Naftiko Framework will enable the new and exciting applications but also the boring old ones many developers maintain.

Naftiko Fabric

The Naftiko Fabric is what developers will see, but what buyers will also see and experience as they use Naftiko.

  • Capabilities - Define your integrations as capabilities, bringing the engineer bits together with the product bits.
  • Observable -You need to have the right business and engineering visibility across site integrations you depend on.
  • Policy-Driven - You need high level strategic control over the tactical things your teams are doing with integrations.
  • Open-Source - You need a formal approach to producing and consuming open-source standards and tooling.
  • Business Aligned - Each one of your integrations with internal or external APIs should be aligned with business outcomes.

Naftiko buyers can start small and achieve more control over their integrations across a wide variety of applications over time.

You can focus on streamlining your integrations now, and bring in the governance later, or you can do both in the same motion.

It is up to you.

OK, you are all doom and gloom on this agentic frontline Kin, but surely there has to be some benefit from all this AI?

I have no desire to champion and cheerlead what is going on, but yes, there will be a number of positive outcomes.

  • Value of Our Data - We will begin to define, measure, and plan around the value of our data—as I’ve pushed for since 2010.
  • Business Processes - We will be forced to better define the business process that matter and get ride of the ones that don’t.
  • Nimbler Enterprises - You are going to see a much more nimbler enterprise emerge, and you will see the bigger ones suffer.
  • More Governance - There will be more governance needed, as we saw with early electricity, telephone, radio, and TV markets.
  • More Standardization - New standards will emerge from the flurry of specifications we see now, stabilizing how things work.

I have a vision for Naftiko. It is one that is bigger than selling picks and shovels in this moment, and just contributing to the chaos.

I am laser focused on a 2032 primary market IPO for Naftiko, and Washington D.C. and the European Commission adopting capabilities as universal standard of the Jobs to Done in the public and private sectors that matter most to the medium and long term benefits of global markets.

I do like responding to these Moltbook type moments and discussion now and then, because it helps me orient myself within my vision for API Evangelist and Naftiko. But in the end, I am playing a medium to long game, where I think others prefer a more emotional, volatile, and stimulating short game.

It just comes to what your tolerance is for velocity, cost, and risk, when it comes to integrating AI into our enterprise operations, and whether or not your vision is bigger than the distractions that come along every week in this new financialized circus we live in.



Read the whole story
alvinashcraft
36 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Measuring What Matters in the Age of AI Agents

1 Share
This post first appeared on Mike Amundsen’s Signals from Our Futures Past newsletter and is being republished here with the author’s permission.

We’re long past the novelty phase of AI-assisted coding. The new challenge is measurement. How do we know whether all this augmentation—Copilot, Cursor, Goose, Gemini—is actually making us better at what matters?

The team at DX offers one of the first credible attempts to answer that question. Their AI Measurement Framework focuses on three dimensions: utilization, impact, and cost. They pair these with the DX Core 4: 1) change failure rate, 2) PR throughput, 3) perceived delivery speed, and 4) developer experience. Together they help companies observe how AI shifts the dynamics of production systems.

For example, at Booking.com that meant a 16 percent throughput lift in a few months. At Block, it informed the design of their internal AI agent, goose. The broader context for this work was captured in Gergely Orosz’s Pragmatic Engineer deep dive, which connects DX’s CTO Laura Tacho’s research to how 18 major tech firms are learning to track AI’s effect on engineering performance.

Agents as Extensions

The message running through DX’s framework is both simple and radical: treat coding agents as extensions of teams, not as independent contributors. That idea changes everything. It reframes productivity as a property of hybrid teams (humans plus their AI extensions) and measures performance the way we already measure leadership: by how effectively humans guide their “teams” of agents.

It also calls for a rebalancing of our metrics. AI speed gains can’t come at the cost of maintainability or clarity. The most mature orgs are tracking time saved and time lost because every gain in automation creates new complexity somewhere else in the system. When that feedback loop closes, AI stops being a novelty and becomes an affordance that highlights a living part of the organization’s ecology.

Shared Understanding

The deeper signal here isn’t about dashboards or KPIs. It’s about how we adapt meaningfully to a world where the boundaries between developer, agent, and system blur.

The DX framework reminds us that metrics are only useful when they reflect shared understanding. Not fear, not surveillance. Used poorly, measurement becomes control. Used wisely, it becomes learning. In that sense, this isn’t just a framework for tracking AI adoption. It’s a field guide for co-evolution. For designing the new interfaces between people and their digital counterparts.

Because in the end, the question isn’t how fast AI can code. It’s whether it’s helping us build human, technical, and organizational systems that can learn, adapt, and stay coherent as they grow.

Key Takeaway

Every developer will increasingly operate as a lead for a team of AI agents.



Read the whole story
alvinashcraft
36 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

BONUS: Jamie's Appearance on Coder Radio 640 - GitHub's Spec-Kit

1 Share

Show Notes

Hey everyone, and welcome back to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. This episode is a slight departure from the standard episode format, as it's a snippet of an episode of Code Radio.

I was invited to discuss GitHub's SpecKit on Coder Radio as I'd been talking about it on the Discord server for the show for a while and really believe in it's transformative power as one of the better Coding-with-AI frameworks.

During the episode, I brough up ClawdBot which immediately aged the episode. Clawdbot has gone through two name changes since the episode was recorded and this bonus episode was released: first to MoltBot then to OpenClaw.

Another thing to note is that, since the episode went live Michael has opened up his Code for Climate 2026 — The Mad Botter Earth Day Open Source Challenge for anyone in K-12 and college education. So if you know folks who would be interested, send them the link. There are some amazing prizes up for grabs, including a couple of System76 computer systems and even a paid internship at The Mad Botter Inc.

Anyway, let's get to the episode.

Full Show Notes

The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-8/bonus-coder-radio-episode-640-snippet/

Useful Links:

Michael's Links

Getting in Touch:

Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show.

Editing and post-production services for this episode were provided by MB Podcast Services.





Download audio: https://traffic.libsyn.com/clean/secure/thedotnetcorepodcast/8B1-CoderRadi-640.mp3?dest-id=767916
Read the whole story
alvinashcraft
37 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

The 90-Minute Retrospective Disaster That Taught Me Servant Leadership | Juliana Stepanova

1 Share

Juliana Stepanova: The 90-Minute Retrospective Disaster That Taught Me Servant Leadership

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

 

"It's not my job to find the points to improve. My job is to help the team find them, to interact their communication, to start thinking about the improvements, and not pushing them into my exercises." - Juliana Stepanova

 

Juliana shares a humbling experience from her first year as a Scrum Master that transformed how she approaches facilitation. She had meticulously prepared what she believed was a brilliant 90-minute retrospective—carefully designed exercises, content tailored to the sprint, everything by the book. Yet when she asked the team for feedback at the end, they delivered a crushing verdict: "It was the worst retro ever." The disconnect wasn't about the quality of preparation but about whose perspective drove the design. Juliana had crafted the session based on her observations and assumptions about what the team needed, rather than asking them what they actually wanted to discuss. 

This experience crystallized a fundamental insight about servant leadership: the difference between leading and servant leading. Today, Juliana prepares at least twice as many tools and exercises as she needs for any workshop, ready to pivot based on the room's energy and the team's expressed needs. She opens sessions with questions about expectations, aligning with the team's mood while setting appropriate boundaries. The failure taught her that even the most carefully prepared facilitation can miss the mark when it doesn't serve what the team actually needs in that moment.

 

Self-reflection Question: When was the last time you asked your team what they wanted from a retrospective before you designed it, and how might their input change your approach?

 

[The Scrum Master Toolbox Podcast Recommends]

🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥

Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.

 

🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

 

Buy Now on Amazon

 

[The Scrum Master Toolbox Podcast Recommends]

 

About Juliana Stepanova

 

Juliana is an Agile coach and Scrum master, with a focus in her work on transformation through people and processes rather than the other way round. She helps teams and leaders to create clarity, build trust and create value with purpose. Her work combines structure with empathy and is always focused on real collaboration and meaningful results.

 

You can link with Juliana Stepanova on LinkedIn.

 

You can also follow Juliana on Twitter.

 





Download audio: https://traffic.libsyn.com/secure/scrummastertoolbox/20260202_Juliana_Stepanova_M.mp3?dest-id=246429
Read the whole story
alvinashcraft
37 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Episode 101: Trader Joe's Gets Fresh (and Deli) for 2026

1 Share

At Trader Joe's, we take product quality, freshness, and value very seriously. In every part of the store, every day. So, when we sat down with a couple of our Category Managers to talk about how they approach freshness and quality, as well as innovation and great taste, there was a lot to discuss. In this episode we're up close and personal with our Fresh and Deli folks. What's the difference between Fresh and Deli? Listen in and find out. We're also sharing some sneak peaks into some new products you'll be seeing in our refrigerated cases… very soon.

 Transcript (PDF)





Download audio: https://traffic.libsyn.com/secure/insidetjs/Trader_Joes_Gets_Fresh_and_Deli_for_2026.mp3?dest-id=704103
Read the whole story
alvinashcraft
37 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

123. From DevOps to Platform Engineering: Building Valuable Software - with Geert van der Cruijsen

1 Share

In this episode, Oscar and Rick talk with Geert van der Cruijsen, CEO of Zure Netherlands, about his career and how technology, culture, and value delivery connect. He reflects on his path through cloud, DevOps, AI and architecture. Geert explains why DevOps is often misunderstood rather than dead, and how platform engineering helps teams focus on business value. They also discuss how hypes change, but the goal stays the same: building valuable software with the right teams and culture.

About this episode, and Geert van der Cruijsen in particular: you can find Geert on LinkedIn and via his blog.

About Betatalks: watch our videos and follow us on Instagram, LinkedIn, and Bluesky





Download audio: https://www.buzzsprout.com/1622272/episodes/18570060-123-from-devops-to-platform-engineering-building-valuable-software-with-geert-van-der-cruijsen.mp3
Read the whole story
alvinashcraft
37 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories