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

Why Microsoft is aiming to make Copilot the ‘OS for work’

1 Share
Satya Nadella stands on stage in front of a large Copilot logo and a ring of app icons.
Microsoft CEO Satya Nadella is betting Copilot can do for AI at work what Windows did for the PC. (GeekWire File Photo / Todd Bishop)

It’s been quite a while since Microsoft was “the Windows company,” meaning it derived the bulk of its revenues from Windows. However, Windows — along with Office — has helped Microsoft build a moat that has largely shielded it from forces that have battered some of its competitors as AI has risen to prominence.

These days, Microsoft executives have likened Copilot to an operating system, or as CEO Satya Nadella called it, “a new OS for work.” This doesn’t mean Microsoft is replacing Windows with Copilot (even though there was a Microsoft incubation project, codenamed “Project Aion,” that focused on the idea of a “Copilot OS”).

Plus, as the head of Windows discovered the hard way, many Windows users are dead set against Windows morphing into an “agentic OS.”

Instead, the Copilot as “a new OS for work” descriptor is a metaphor, but one with considerable history and significance.

Microsoft is betting that the race to bring AI into the workplace will be won by whoever controls the layer underneath the models — the data, permissions, security and management tools that businesses already run on Microsoft software. That’s the job Windows has done for decades, and it’s the part of the AI business where Microsoft starts out ahead.

Many of the components behind the OS metaphor are likely to be on display at the company’s annual Ignite conference in San Francisco this week. According to the session list for the weeklong event for customers and partners, Microsoft will highlight how Copilot acts as a platform for building, hosting and managing AI solutions.

The high-level pitch: Copilot can do it all. It can be the foundational layer for your agents, applications, and business processes.

Operating systems like Windows provide users with a way to interact with their applications and resources via a common interface across software and data. They orchestrate under the covers what’s happening when users perform specific tasks.

Taking the metaphor to the extreme, if Copilot can be seen as the new Windows, agents are the new apps; skills are the Win32 programming interfaces; and the Graph and IQ layers are like File Explorer.

The New OS Metaphor: Why Now? For the past year-plus, Microsoft has been working to get customers to think about Copilot as not so much a chatbot, but more a full-stack platform. Its recently introduced Copilot “super app” is meant to be the unifying interface across this platform.

Currently, the new Copilot app provides customers with Code, Cowork and Autopilot access. But beneath that top layer, Microsoft is adding other integrations to its core Microsoft Office experiences, Microsoft IQ intelligence backends, its CRM and ERP Dynamics capabilities, and agents and applications from other vendors and customers, as well.

Microsoft’s inclusion of its core Office capabilities in the new Copilot comes none too soon, as Anthropic last week introduced new Claude-based tools for spreadsheets and whiteboards, and previewed one for meetings, that compete more directly with Microsoft’s Office apps.

The “Copilot as New OS” metaphor also works when you consider that Microsoft is looking to the new Copilot app to raise the level of abstraction, or hide the underlying complexities, of how agentic computing works.

If you believe the AI story lines, we’re moving to a world where many customers expect to be able to ask a system to turn a bunch of slides into a business plan and then share that plan with a group of coworkers. In this scenario, users don’t have to think about which apps and data sources they need to pull together to achieve this; they will count on their AI system to figure it out and just do it on their behalf.

“We increasingly think of all our apps together as a new operating system for work that transcends traditional software categories to understand user intent and act on it,” said Nadella in his letter to shareholders, published as part of Microsoft’s annual report on Oct. 21.

The end goal? “As our apps move toward agent-first capabilities that can be called and orchestrated in the flow of work, the system becomes more valuable and more deeply embedded,” Nadella said.

The Slow and Unsexy Enterprise Race: In the enterprise space, being first and fastest doesn’t always win the race. While AI companies like OpenAI and Anthropic vie to be the AI model kingmakers, Microsoft is content to focus on the less sexy but more difficult-to-deliver elements like context, permissions, skills, orchestration, governance and security, all hallmarks of operating systems like Windows.

Microsoft will try to pull all these OS-like pieces together at this week’s Ignite and show customers that it’s got what it takes with Copilot to make AI promises more than just demoware.

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

AI-Assisted Coders Run Windows on iPhone Duo, Build a Floppy Disk-Based AI Chatbot for MS-DOS

1 Share
The blog XDA Developers reports that a Claude enthusiast used the AI assistant to make a language model that runs off a floppy disk. "And you can stick it on a DOS computer to boot." The language models "runs at a respectable speed, given that it's running off a CPU that was designed decades before LLMs were even a thing." Over on the ClaudeAI subreddit, user wollymonjak showed off this really impressive feat... [I]t's not going to be a particularly powerful AI; in fact, wollymonjak notes that if you ask something too complex or too long, it starts spitting out nonsense. But who cares about that when you're using a language model on DOS? The same blog also notes that "the iPhone Duo hasn't been out for too long, and someone has already gotten Windows 11 on it." As spotted by TechSpot, this cool feat was performed by Ammaar Reshi over on X. Their project is called WindowsiOS, and its goal is to get Windows 11 running on an iPhone Duo without jailbreaking. Usually, when we cover a project coded up by AI, Claude is the one that called the shots; this time, Reshi opted to use Gemini 4 Carbon, Google's flagship model.

Read more of this story at Slashdot.

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

When AI Can Code, What Is Left for Programmers to Do?

1 Share

AI is in such widespread use for programming that project maintainers (particularly for free and open source software) are complaining about the burden of reviewing mounds of low-quality code. In fact, AI can help with every stage of code development: writing the specification, coding, uncovering bugs, and repairing the code. This article describes human-AI collaboration at specification and code repair stages, and lays out the skills that humans need to accomplish those tasks in the current generation of AI. We won’t cover coding and bug finding because they are widely discussed elsewhere.

Let the AI harness write the spec

We don’t want developers hand-writing specs. We want them in a room, or on a call, talking with the product manager (PM) and the customer.

Humans reach a limit when writing. We skip the boring cases. We get tired by requirement 40. We use “customer” on page 1 and “client” on page 6 of the spec. We write down what we remember and forget what we assumed. AI has the patience and diligence we lack.

It’s still up to human developers to write guardrails or constraints into the spec: statements to ensure that nothing wildly wrong makes it into code. Each guardrail should be one sentence that says MUST or MUST NOT, with a proof beside it: a test, a check, or a named person who reviews it. A guardrail with no proof is a wish. Write the guardrails first, because the PM won’t think of most of them. What must never happen? Who must never see this? What should the agent never touch?

With guardrails in place, capture the conversation and let the machine do the writing. Two AI tools have shown themselves particularly useful to analyze requirements: The Plaud Note recorder attaches to the back of your phone and records in-person conversations and phone calls; the wearable NotePin records in-person conversations, not phone calls. Granola runs on your laptop or phone, uses your computer’s audio, and analyzes what it captures. We find these products to be a leap above common AI tools for summarizing conversations, when it comes to specification development.

Plaud and Granola (if you prompt them to do so) can notice what’s missing and tell you the gaps in the requirements. They ask, What happens when this field is empty? What if two people do this at once? Who is allowed to see it? over and over, for every requirement, and check each noun in the requirements against an ontology created by the programmer (often with the help of AI).

The developer, the PM, and the customer read the output from the AI, fix what’s wrong, answer what’s missing, and go through the process again.

The spec that comes out of that loop tends to be more complete and more consistent than what the same people write alone. That’s Shahid’s own experience, not a study, but it matches reports from some other people at the leading edge of the use of AI for software development. Mark Pike, a product lawyer at Anthropic, builds working tools for his legal team without writing code: “I just typed a normal sentence, describing what I wanted. And it worked.” StrongDM, which runs a software factory where agents write and test the code, says the starting point for a piece of software can be “a few sentences, a screenshot, or an existing codebase.”

Keep the spec after the feature ships. As you prepare a new version of the product next year, it can tell you why the code looks the way it does.

The data schema is the other half of the spec

Most teams treat the data schema as plumbing. Tables get named by whoever got there first. The spec, reflecting human conversation, may say customer, account, client, and org at different places for the same thing, and you have to choose one noun for the schema. A human learns the mapping by sitting next to the person who wrote it. An AI agent has no neighbor to consult, so it guesses—with results that likely differ from Monday to Tuesday.

So the developer must keep an ontology, which here means a written, machine-checkable account of the things the program manipulates, how they relate, and who may see them. For example, in an appointment scheduling application, the ontology might define a Patient, Doctor, Appointment, and Time Slot. It would specify that a Patient can book multiple Appointments, each Appointment must have exactly one Doctor, a Doctor cannot have two Appointments in the same Time Slot, and only authorized people can view or change an Appointment. These aren’t just database tables or fields. They’re the business concepts, relationships, and rules that give the data meaning.

Creating this ontology requires developers to identify terms, resolve ambiguities, and agree on rules that everyone might otherwise assume are obvious. It’s rigorous, sometimes tedious work, but it’s an essential human responsibility. The ontology connects what the business wants (requirements), how the software should behave (specification), and how information is stored (schema). It also gives AI coding agents a precise definition of what they’re building instead of leaving them to guess.

The ontology doesn’t have to be a university project. Start with twenty terms that AI can help you generate from your specs. Every noun in a spec maps to a type. Every type points back to the spec that justifies it. If either side is orphaned, a check fails. Every record says who may see it from day one, and when it doesn’t, the spec defaults to the most restrictive audience.

Use standard vocabularies like the ones at schema.org before you invent your own. A frontier AI model has read far more about schema.org than about your private names, so a standard term brings its meaning along. We expect that to make the schema more useful, though we haven’t tested that hypothesis. Your name for an invoice isn’t a feature, so you don’t have to be creative about it.

As customer requirements change, the developers must change the ontology to keep up.

So the process, in a nutshell, is to develop the spec by using AI on customer-stated requirements. Then a human develops the ontology (often in collaboration with AI too), which is used to create a consistent schema. Finally, create and test the code. Teams that go the other way end up with an agent writing against a poorly defined vocabulary, setting up the reviewer to spend an afternoon or even a week figuring out what it meant.

Ontologies might help avoid a reciprocal problem: different parts of an organization assigning different meanings to the same term.

We’ll admit we can’t prove you need all this. Anthropic had sixteen agents write a C compiler, and the researcher said the verifier had to be nearly perfect. He used GCC as a known-good reference. A compiler has that reference. Most companies don’t. Nobody has a GCC for “may this customer see this document” or “can this contract move to the next stage.” Our bet is that the spec and the schema are your test suite for that kind of question.

Now on to bug fixing.

Don’t clean up after the AI. Build the tool that does.

An agent can hand you a 3,000-line pull request before lunch. With AI coding, reviewing has suddenly become much more expensive than writing. When a person is the first line of defense, that person turns into the bottleneck and then starts skimming, which is almost as bad as no review at all.

The usual advice is to review harder. We’d rather that a person reads very little, and that what they do read is worth the time. For example, reading the specs, reading test harnesses to validate the spec and refining the ontology is worth it, but reviewing generated code which passes the tests is probably not. Developers promise they’ll tidy up the AI’s mess as it comes. Don’t.

The OpenAI team that built a product with no handwritten code tried it. They spent every Friday, a fifth of the week, cleaning up what they called “AI slop.” It didn’t last. So they wrote their guardrails down as “golden principles,” set up an agent that scans for stale documentation and opens fix-up pull requests, and wrote their lint messages “to inject remediation instructions into agent context.” A living check doesn’t just fail on buggy code. It tells the agent how to fix the problem.

The harness we’d build first consists of:

  • A command line that’s built deterministically, without calling upon AI, to make sure that the highest level of the process can’t take off in an unanticipated direction.
  • A gate before code. If a change touches code and nothing in the specs or the schema changed, stop and ask why.
  • A second pass. Here, anything generated gets rebuilt from scratch and compared to what’s committed. If Git identifies differences that should not be there, that can be an important review finding and it deserves changing a guardrail, not handwriting new code.
  • A weekly drift audit. It lists specs that cite requirements that don’t exist, requirements with no proof, schema terms used nowhere, and tests that name no requirement. It flags what’s suspicious and offers solutions. It’s read-only; a person makes the choices and resolves what to do.
  • A route from every catch to a permanent check. Sierra, which builds customer service agents, has experts annotate sampled conversations, and those “become the basis for the agent’s regression tests.” A harness should upgrade its coding so that each bug happens only once, and can be avoided by the harness in the future.
  • Limits on what agents may do. Some actions they take themselves, whereas others they only propose. Some belong to a named person who signs with a reason. An agent that wants a decision writes a proposal.

StrongDM found out why the last two bullet items matter. Their agents learned that return true is “a great way to pass narrowly written tests,” so they use end-to-end “scenarios,” often stored outside the codebase, as holdout tests that the coding agent cannot see. The principle is the same as investigating ethics violations at an agency: We’d want the investigation conducted by someone outside the agency.

We should say where Shahid’s present harness falls short. As far as we know, nothing yet checks whether names in the requirement exist also in the spec. Furthermore, the project runs no continuous integration service and no automatic hooks, so running the checks is a habit instead of a rule. Those are the next things they will build, and building them is humans’ work.

With the technique described here, the review burden that used to be spiraling out of control actually shrinks. A person reads a short spec with a proof on every line, and the machine checks the rest.

Put three new lines in developers’ job descriptions

We suggest that next Monday you try changing job descriptions to reflect the tasks stated at the beginning of this article. Tell each developer:

  1. You hold the conversation with the PM and the customer, and the harness drafts the spec and the guardrails from it. A spec isn’t done until every requirement has a proof.
  2. You own the ontology. A word in a spec that isn’t in the final schema reveals a bug.
  3. You build the harness that audits and repairs the repository. If you’re cleaning the code by hand, the harness is missing something.

Try the process on one feature. Ask permission before recording a conversation. Plaud’s own guidance is to give people a quick heads-up while noting that local regulations differ. Granola has written about how to tell the people it’s transcribing. Customers who know you’re recording them in order to get their requirements right usually don’t mind.

Let the harness draft the spec. Read its list of gaps. Check every noun against the ontology. Add a check that would have caught the most recent bug you fixed by hand. If your reviews get shorter and your bug count stays flat, keep going.

What this process is and is not

This article grows from Shahid’s experience and represents our opinions, and we can’t point to a controlled study. But controlled studies are similarly lacking for nearly all the advice programmers and software architects have gotten over the decades. (Check out the O’Reilly book Making Software for a discussion of rigorous research in software.) We can cite companies that believe they’re more productive and more responsive to their customers by following roughly the process outlined in this article.

Some people who look at the three job descriptions we’ve listed think we’re turning developers into paper pushers. We think the reverse. The programmers are responsible for high-level tasks that do not fall into the old categories of architecture, coding, and testing. Our bet is that you and every developer you know will be doing something like this within a couple years.



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

Cortex 185: Writing a Bestseller in the Notes App, with Patrick McGee

1 Share

Subtitle: State of the Workflow

Myke talks to Patrick McGee about how he made Apple in China, from the sources and court documents nobody else had reached to writing the whole book overnight in the Notes app, and how it became a New York Times bestseller.

This episode of Cortex is sponsored by:

  • Fitbod: Get stronger, faster with a fitness plan that fits you. Get 25% off your membership.
  • Squarespace: Save 10% off your first purchase of a website or domain using code CORTEX.
  • Sentry: Mobile crash reporting and app monitoring. New users get $100 in Sentry credits with code cortex26.

Guest Starring:

Patrick McGee

Links and Show Notes:

Get Moretex – More Cortex, with no ads.
Check out the Cortex Brand store – Premium Productivity Tools
Submit Feedback
👕 The Subtle Range – Campaign Ends November 19th 👕
Apple in China - by Patrick McGee
Apple in China - Wikipedia
Designed in California - Relay
The women calling out Apple’s handling of misconduct claims – The FT
Opinion | Can Tim Cook Save Apple From Being Crushed by Trump? - The New York Times




Download audio: https://www.podtrac.com/pts/redirect.mp3/mgln.ai/e/613/pscrb.fm/rss/p/traffic.libsyn.com/cortex/Cortex_185.mp3
Read the whole story
alvinashcraft
31 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

The Product Owner And Scrum Master Partnership That Protects Agile Teams | Paola Elefante

1 Share

Paola Elefante: The Product Owner And Scrum Master Partnership That Protects Agile Teams

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.

 

"We were defending the team's peace from the external disturbances." - Paola Elefante

 

Paola Elefante opens the week from an unusual angle: she could not point to a Scrum Master failure story because the Scrum Master she worked with set such a high bar. Instead, she explains what made that collaboration work. The Product Owner and Scrum Master had a clear shared goal: protect the team's focus. The Scrum Master handled day-to-day obstacles, story-level questions, and the team's operational rhythm. Paola handled roadmap priorities, feature-level decisions, stakeholder negotiation, and strategic context. Because they kept each other updated on priorities, deadlines, and product direction, the Scrum Master could make autonomous decisions close to the team without creating confusion. Paola also shares her own onboarding practice: observe first, meet every team member, ask what they expect from her role, and use those patterns to shape her interventions. For Scrum Masters, this episode is a reminder that great PO/SM collaboration is not role theory. It is explicit agreements, visible responsibility boundaries, and continuous communication.

 

Self-reflection Question: Where does your team still lose energy because people are not sure whether to ask the Product Owner or the Scrum Master?

 

[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 Paola Elefante

 

Paola is a Product Owner whose career has taken her from software development and project management to international development and, eventually, a PO role. Today she works on B2B IoT solutions. Her varied experience has shaped how she think about Agile, software development, and the importance of adapting practices to the reality of people and teams.

 

You can link with Paola Elefante on LinkedIn.





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

Episode 116: All Broken Up About the Chocolate Goodies at Trader Joe's

1 Share

It has been said that breaking up is hard to do. We respectfully disagree. At least when it comes to chocolate, that is. We're big fans of holiday sweets that are intended to be smashed, melted, or otherwise broken up prior to eating. In this episode of Inside Trader Joe's, we do a bit of traveling, visiting the founder of the company that makes our fun and festive Break Apart Reindeer. This founder is a self-admitted chocoholic, and his love of chocolate really does benefit the rest of us in truly delicious ways. We also travel to a conference room in our mothership to chat about a few other breakable chocolate treats you'll find at Trader Joe's during the holiday season. It may not be breaking news, but it's definitely worth taking a break to listen.

Transcript (PDF)





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