Coté

“A man who had over the course of a week absorbed, as by osmosis, the Spirit of the Internet. And that is a foul, foul thing.” a slightly embarrassed announcement

Slowing Down - How to avoid burnout as you get more successful at life.

Gartner predicts 40% of enterprise apps will feature AI agents by 2026 - “Enterprise applications are entering a new phase of automation, with Gartner forecasting that 40 percent of them will include task-specific AI agents by 2026 – up from less than 5 percent today.” And: “By 2035, the firm predicts, agentic AI will account for nearly $450 billion in enterprise software revenue, or 30 percent of the market.” // Some predictions about broad uses as well. The uses are mostly (all?) the idea of having an assistant in your tasks, yes, a “copilot."

Migas from another mother

I have been trying to figure out fatteh. Here are some recent attempts.

A plate of food features toasted bread topped with avocado, yogurt, and a generous amount of pine nuts.

A bowl of creamy hummus topped with pine nuts, chickpeas, and fresh herbs.

A plate of food features toasted bread topped with avocado, yogurt, and a generous amount of pine nuts.

I still don’t know if I actually like this dish, but it is super fun to make. It’s sort of - and pardon any cultural offense here, I don’t even know what the aesthetic-mores of this food culture are - like Lebanese migas.

School phone policies and their association with mental wellbeing, phone use, and social media use (SMART Schools): a cross-sectional observational study - Update on the young people and those damn video games. // “There is no evidence that restrictive school policies are associated with overall phone and social media use or better mental wellbeing in adolescents. The findings do not provide evidence to support the use of school policies that prohibit phone use during the school day in their current form, and indicate that these policies require further development.” // See Tyler Cowen’s disclaimer. // I mean, it could be one of those “phones don’t ruin kids lives, kids using phones to ruin their lives ruins their lives” situations.

Funny Podcast Titles

We come up with some pretty fantastic titles for Software Defined Talk. And you should see the five to ten other possible ones we note down each episode.

One of the best ones is truncated in the screenshot: “You can’t spell Clippy without CLI.”

A list of articles with titles, slug numbers, and published dates is displayed in a table format.A table displays blog titles, slugs, and publication dates from 2022 to 2025.

How to use Tahoe's new Use Model shortcut to summarize articles

The new Use Model shortcut in Apple Shortcuts opens up a lot of possibilities. For example, I like to summarize a lot of pages. Sometimes, ChatGPT can’t get the text for those pages, or I don’t trust the text it retrieves. There’s a shortcut that will retrieve the cleaned up text of a page (as markdown). So, you can get that markdown, and with the new Use Model shortcut, you can summarize it and then send the markdown summary to Drafts. You could open the text up in another app to view, whatever you like, but as you can imagine, I like to catalog this stuff. Also, it can generate a little link to include for my newsletters link list.

You put this in your Sharesheet, and now when you’re reading the World Wide Web, you can get summaries real quick-like.

Here is the shortcut:

I left in the stop and output for debugging, but I’d take that out.

Here is output from one of my articles:

Developers Aren’t Using Your Platform? Marketing Might Be the Missing Link

Source summarized: Driving Platform Adoption: The Missed Opportunity of Marketing.

Internal Developer Platforms (IDPs) often fail to gain traction despite delivering exactly what engineers request. This piece argues that platform marketing—alongside product management and community building—is the missing discipline most teams ignore, and offers a systematic approach to drive developer adoption.

Key Insights

  • Define your developer audience narrowly before pushing adoption efforts.
  • Craft messaging that focuses on developer benefits, not platform features.
  • Position your platform in clear, specific contexts (cloud-native apps, AI workloads, regulated environments).
  • Lead with value propositions that are measurable, like time savings and frictionless onboarding.
  • Avoid the “platform for everything” trap; targeted positioning accelerates adoption.
  • Integrate marketing with product management for tighter feedback loops.
  • Use developer-friendly proof points (fast deployments, pre-approved services, reduced ticketing).
  • Iterate adoption starting with a few archetypical teams before scaling org-wide.

Most organizations spend years building internal platforms that meet developers’ stated needs, only to watch usage stagnate. Teams often assume technical excellence alone will win hearts and minds. The authors note that marketing—treated as a rigorous engineering-like discipline—can bridge that gap by creating awareness, clarity, and trust. The first step is laser-focusing on the actual developer persona who will use the platform. “Developers” is too broad; target application developers in specific business domains and technology stacks to avoid generic messaging.

Messaging, positioning, and value propositions form the backbone of platform marketing. Messaging should translate features into developer-relevant benefits: zero setup time, fewer meetings, and faster deployments. Positioning narrows the platform’s role in the ecosystem—rather than claiming to be universal, identify where the platform delivers the most leverage, from legacy modernization to AI-driven applications. Value propositions then provide concrete, provable outcomes, like cutting deployment cycles from days to minutes or eliminating 80% of security review meetings.

Finally, the authors emphasize that platform marketing is not fluff—it’s how you engineer adoption as deliberately as you design pipelines. By starting small, learning from early adopter teams, and communicating benefits in precise, outcome-driven language, organizations can finally capture the ROI on their internal platform investments. Marketing is not a side hustle; it’s the connective tissue that transforms a platform from shelfware into a strategic asset.

Summarized by ChatGPT on Sep 16, 2025 at 1:09 PM.

Fantastic! I used to have to do this manually.

And, are the summaries good? They’re not always perfect, but I’m often looking to see if I should spend the time to read the whole thing, especially if it’s long and…not the best of writing.

All of the nerd content I've made this fiscal year, so far

This is “content” I’ve made from November, 2024 to today that has something to do with my work. Mostly “to do with” means “talks about the tech world,” if not directly about the concerns and products we have and do at Tanzu.

Items include videos, podcasts, white papers, published recordings of conference talks, guesting on other things, etc.

That’s 141 items of “content.” The robot helped me generate this, so pardon any linking or date errors. And, I didn’t go back and fetch the exact Software Defined Talk URLs. Boo!

There’s also a list of conferences I’ve spoken at, which has some cross over if there is a published recording of the talk. You can see my selection of those recordings, over the years, over in YouTube.

Export markdown from Apple Notes, even in bulk...almost works.

In macOS Tahoe, you can finally export Apple Notes in markdown. This is great, and even exports images and handwriting from the Apple Pencil. You can also bulk export, which is great! Sadly, bulk exporting images and handwriting doesn’t work. It saves the images and handwriting in a file called Attachements, but then in the actual note markdown, all references to images are to a file called FallbackImage.png. Also, it exports an sqlite database. I’m not sure what’s in there, it’s all gobbledygook to me.

How To Build Agentic AI That Ships - The New Stack - “Ninety-five percent of AI initiatives should be expected to fail as long as we ignore these pitfalls: Models are generic. Enterprises are unique. Ideal use cases aren’t flashy. Coordination across teams is hard.” // Lots of other good executive think too, especially being blind to how complex the overall system is w/r/t dependencies. // Also notable is that, technology aside, these are all the concerns of “digital transformation."

@cote@cote.io, @cote@cote.io @cote, @cote.io https://proven.lol/a60da7,