{ "version": "https://jsonfeed.org/version/1", "title": "Coté", "icon": "https://avatars.micro.blog/avatars/2025/42/8457.jpg", "home_page_url": "https://cote.io/", "feed_url": "https://cote.io/feed.json", "items": [ { "id": "http://cote.micro.blog/2026/03/21/garbage-chairs-of-amsterdam.html", "title": "Garbage Chairs of Amsterdam", "content_html": "

\"Underground

Hidden, but seen.

\n", "date_published": "2026-03-21T08:11:20+01:00", "url": "https://cote.io/2026/03/21/garbage-chairs-of-amsterdam.html", "tags": ["pictures","Relative to your interests"] }, { "id": "http://cote.micro.blog/2026/03/20/opinionated-platforms-private-models-essential.html", "title": "Opinionated Platforms, Private Models, \u0026 Essential Dev Tooling", "content_html": "
\"Meta's

Related to your interests

\"\"

Wastebook

ICYMI

Logoff

See you next time!

\n", "date_published": "2026-03-20T19:46:51+01:00", "url": "https://cote.io/2026/03/20/opinionated-platforms-private-models-essential.html", "tags": ["newsletter"] }, { "id": "http://cote.micro.blog/2026/03/20/its-real-enterprises-just-need.html", "title": "It's real, enterprises just need to do the CISO work and SRE work", "content_html": "

After using Claude more and more for task in my personal life, my current zinger analyst take on the Squawk Box would be: “OpenAI talks about business strategy, Anthropic just does it.” It’s really getting close to a sci-fi personal assistant. It takes A LOT of work to get your rig (or “harness”) setup, and to continually tune it, but it’s amazing.

\n

Once CEO’s get their hands on this for a week, and the IT departments and CISOs figure it out, it’ll be amazing in enterprise life…again, not just for programmers, but for everyone.

\n

The biggest benefit will be less meetings, less having to be a meat-mouse for executives who can’t or won’t make their own slides, and finally getting CRM and ERP “business analytics” nailed.

\n

You know, until we get used to productivity benefits in 6 months and then just hate it like we do all enterprise software, because we want the next impossible thing.

\n", "date_published": "2026-03-20T09:14:31+01:00", "url": "https://cote.io/2026/03/20/its-real-enterprises-just-need.html" }, { "id": "http://cote.micro.blog/2026/03/19/it-was-a-rather-stressful.html", "title": "It was a rather stressful period", "content_html": "

Related to your interests

Wastebook

Logoff

See you next time!

\n", "date_published": "2026-03-19T20:06:10+01:00", "url": "https://cote.io/2026/03/19/it-was-a-rather-stressful.html" }, { "id": "http://cote.micro.blog/2026/03/18/internet-coinop.html", "content_html": "

Internet Coin-op

\"Internet

\n", "date_published": "2026-03-18T22:43:41+01:00", "url": "https://cote.io/2026/03/18/internet-coinop.html", "tags": ["Relative to your interests"] }, { "id": "http://cote.micro.blog/2026/03/17/ai-brain-fry-zombie-projects.html", "title": "AI Brain Fry, Zombie Projects, and Gentleman Vibe Coders - Related to your interests, Monday", "content_html": "

KubeCon EU is next week, in Amsterdam, and I’m talking at VMUG Amsterdam tomorrow about what private equity does to enterprise software companies. If you’re at RAI, come say hi. AI might have written some of the below; we’re still working on keeping it under control for “helpful” content generation.

Related to your interests

Wastebook

ICYMI

Logoff

See you next time!

\n", "date_published": "2026-03-17T09:31:11+01:00", "url": "https://cote.io/2026/03/17/ai-brain-fry-zombie-projects.html" }, { "id": "http://cote.micro.blog/2026/03/12/my-grandfather-was-mildly-obsessed.html", "content_html": "

My grandfather was mildly obsessed with organizing and documenting the history of his life: a memoir about a career in the military from 1938 to ~1975, growing up in a Depression era Oklahoma “dirt farm.”

\n

There was also geology. I think all old people have that project. Us soon to be old Gen-X’ers have more records around than probably any human in history, especially the nerds. Soon, we’ll all be obsessively organizing the equivalent of our 40 year slides and boxes of receipts. Personal digital gnolling.

\n", "date_published": "2026-03-12T22:24:17+01:00", "url": "https://cote.io/2026/03/12/my-grandfather-was-mildly-obsessed.html" }, { "id": "http://cote.micro.blog/2026/03/12/ai-use-isnt-about-firing.html", "content_html": "

AI use isn’t about firing people, it’s about making the people you already have more productive. You have to change your corporate system/culture to adapt to that:

\n
\n

However, when finance leaders seek to identify where this return appears in terms of headcount shifts or cycle-time compression, the answers are less clear. These gains remain trapped inside individual workflows unless leadership intentionally redesigns roles and budgets to capture the reclaimed time. This occurs because saved time is often re-absorbed into low-value activities—like more internal meetings or unnecessary emails—rather than being structurally harvested through role reclassification or a mandate and clearance to shift time toward higher-value strategic work.

\n
\n

From: The “Last Mile” Problem Slowing AI Transformation

\n", "date_published": "2026-03-12T22:08:11+01:00", "url": "https://cote.io/2026/03/12/ai-use-isnt-about-firing.html" }, { "id": "http://cote.micro.blog/2026/03/11/feminization-and-deming.html", "title": "\"Feminization\" and Deming", "content_html": "

The term “feminization” is, as the kids used to say, “suss,"[^1] but this reminds me of one of the points John Willis made in his Deming work.

\n

There was a huge influx of women in corporate work/factories during WWII, and also lots of rapid process change. It was all wildly successful - proven by a clear outcome of winning the war! Then the men came back, patted the women (and Deming-ites) on the head and said “that’s nice, now back to normal…”

\n

Original: Money, Talent, and the War Test: What WWII’s Female Labor Surge Says About “Feminization”

\n

[1]: It usually, effectively, ends up meaning “being better,” or, at the very least “stop being so boorish.”

\n", "date_published": "2026-03-11T07:13:03+01:00", "url": "https://cote.io/2026/03/11/feminization-and-deming.html" }, { "id": "http://cote.micro.blog/2026/03/10/when-developer-workflow-discipline-isnt.html", "content_html": "

When Developer Workflow Discipline Isn’t Enough\nthectoadvisor.com/blog/2026…\nSelling cross-silo enterprise infrastructure stuff is very difficult:

\n
\n

These are platform engineering objections. And they’re coming from a team the vendor never talked to. Because the vendor optimized their story for developer adoption. They have research that tells them developers love this. What they don’t have is a conversation with the platform team that has to decide whether this can actually be operationalized inside a real enterprise environment."

\n
\n

It’s pretty much always devs versus ops in enterprises. They need organizational therapy from the top, and then the tools.

\n\n\n", "date_published": "2026-03-10T11:36:56+01:00", "url": "https://cote.io/2026/03/10/when-developer-workflow-discipline-isnt.html", "tags": ["links"] }, { "id": "http://cote.micro.blog/2026/03/09/fully-synergized-paradigms-related-to.html", "title": "Fully Synergized Paradigms - Related to your interests, Monday sweep", "content_html": "

The Links

\"Spear_Rock\"
A Menhir.

Wastebook

Logoff

I am getting some real applied learning on applying agentic to enterprise-y things that are not programming. It is amazing with the right rig.

\n", "date_published": "2026-03-09T17:45:17+01:00", "url": "https://cote.io/2026/03/09/fully-synergized-paradigms-related-to.html", "tags": ["newsletter"] }, { "id": "http://cote.micro.blog/2026/03/07/related-to-your-interests-week.html", "title": "Related to your interests - Week of March 2nd, 2025", "content_html": "

The Links

Claude, without me asking, rewrote many of my original description below. Enjoy!

Wastebook

ICYMI

Logoff

I’ve started to use Claude Core for non-programming agentic stuff. Once you set up the memory system (just storing context in various ways), it is, indeed, amazing.

\n", "date_published": "2026-03-07T20:00:41+01:00", "url": "https://cote.io/2026/03/07/related-to-your-interests-week.html" }, { "id": "http://cote.micro.blog/2026/03/06/when-to-use-ai-for.html", "title": "When to use AI for writing, and when it's totally acceptable ", "content_html": "
\n

If you’re dyslexic and just trying to communicate more clearly in writing, or you’ve got a bullshit job and you just want to get your bullshit job’s bullshit tasks out of the way so you can move on to more meaningful endeavors, or at least move past the day-to-day slog that permeates your workday and serves no real purpose other than to pay the bills, then I cede; I cannot fault you.

\n
\n

From: “LLMs Are Antithetical to Writing and Humanity”

\n

As I like to say, if it’s bullshit work, let the bullshit artist do it.

\n

I think we can all agree on cheese on that one.

\n

How about work that isn’t bullshit?

\n

One objection to AI driven writing and learning is that it’s too easy. I’m leering of the Protestant take on work and learning: if it’s not painful (“struggle”), it’s not worthy. The worth of something is proportional to how much suffering it requires.

\n

With writing, I favor a more pragmatic approach: did people read it? Did they like it? Then it “works.” The quality of writing is proportional to the reader’s acceptance of it.

\n

There are many aesthetics for that, many audiences. If your readers like to know - even hear tales of - your suffering to make it, then that is success. For example, Joan Dideon and Hunter Thompson evidence this pain of writing and the process - that is part of the gonzo aesthetic. Susan Sontag has a different kind of suffering aesthetic in her writing.

\n

Hemingway has a machismo version of good writing is suffering: I bled this out, aren’t I man? Fitzgerald effortlessly hides it, and it’s all as much a part of Sarah Manguso’s writing as the actual suffering she is writing about and vibing.

\n

As reader, knowing that those writers suffered to give you this text is part of the enjoyment, the essence of the writing, how it makes the reader react and feel, and with the best of that writing, how it changes the reader.1

\n

For most readers…some don’t care, they just want to laugh at Hunter Thompson talking to Nixon at the urinals or feel a kindred spirit as Joan Didion processes slow death of her daughter and husband. Or thrill in the cleverness of Sontag.

\n

If you saw the suffering of writing Dungeon Crawler Carl, it would ruin the awesomeness of that series.

\n

Similarly, when you read The Economist or an AP report, you don’t want to know about the suffering. You want to get information as clearly and quickly as possible. If you’re a writer, you may know that much suffering was done; more precisely, you know how incredibly skilled those writers are to avoid suffering and work quickly.

\n

So, when it comes to using LLM’s for writing, my criteria is “did it work?” Defining “work” there is the real question because it’s defined by your goals and readers, and also your constraints (time, ability, cost, etc.)

\n

In the original, dyslexia is used as a justification for writing. I’d add something more widespread: not being trained - not having suffered to learn! - how to write. If you need to write something and you “don’t know” how to write, to get accomplish your goal, to get on with life, use AI. That won’t always be “bullshit” work.

\n

I think that’s one thing that’s driving writers and readers crazy. Similarly, professional programmers are (rightly) freaking out that with code generators more people can now code. They are having an aesthetic reaction: coding should require suffering. Now: no suffering required, and that’s fine.

\n

To that end, the original piece; lays out excellent advice on how to integrate AI, as a tool, into what you do. More like a philosophy of how to do it.

\n

Also, highly related is this take on MrBeast. Clearly, the author does not like the aesthetics of MrBeast’s work. But, civilization has shown that it “works.” I don’t like Shakespeare (at all) and I find Victorian literature tiresome. I much prefer still lifes with huge chunks of cheese and shucked oysters over pictures of soup cans. People have different aesthetics, so it goes.

\n
\n
\n
    \n
  1. \n

    In another domain, the need to suffer for quality content (“art,” even) is core to Hip Hop. The difficultly of life, to get the ink to sink into the paper, the struggle to get in the booth night after night to record becomes part of the work itself, the lyrics and even the sound. The artists’ blood sinks into the song. Courtney Barnett (there’s a whole movie on her suffering!), sure, but not really Khruangbin. ↩︎

    \n
  2. \n
\n
\n", "date_published": "2026-03-06T07:37:25+01:00", "url": "https://cote.io/2026/03/06/when-to-use-ai-for.html" }, { "id": "http://cote.micro.blog/2026/03/04/art-degrees-sun-microsystems-and.html", "title": "Art Degrees, Sun Microsystems, and How Kubernetes Scales Contributions, with Josh Berkus - Software Defined Interviews #121", "content_html": "\n

Our interview for this week is up, it’s with Josh Berkus:

\n
\n

Whitney and Coté discuss with Josh Berkus (Red Hat, Kubernetes contributor) how liberal and fine arts degrees (philosophy, photography, sculpture, pottery) apply to tech careers. Berkus details how early hardware experience influenced his database performance work, noting hardware’s renewed relevance with AI and multi-arch computing. The conversation covers Sun Microsystems’ 1990s internet role, internal politics, and its MySQL/Postgres strategy. They examine open source’s shift from end-user to vendor-driven models, foundations' roles, and contributor incentives. Berkus describes Kubernetes release processes, contributor-experience programs, and its resilience to low-quality AI contributions.

\n
\n

Listen to the traditional podcast format, or watch the video if you prefer.

\n", "date_published": "2026-03-04T11:21:55+01:00", "url": "https://cote.io/2026/03/04/art-degrees-sun-microsystems-and.html", "tags": ["videos","tech","podcasts"] }, { "id": "http://cote.micro.blog/2026/03/03/related-to-your-interests-tuesday.html", "title": "Related to your interests, Tuesday", "content_html": "

The Links

\n\"\"\n

Wastebook

\n\"\"\n

Logoff

I’ve had a hodgepodge of things to do of late, during the day and the evening. It’s most satisfying to do one thing, a big unit of work. But, thankfully, the hodgepodge is usually just due to me not arranging my time well. Productivity gas-lighting!

On second thought, moving the newsletter to micro.blog isn’t exactly what I want to do.

\n", "summary": "CFOs boost tech budgets and squeeze headcount, AI art may not be copyrightable, and agents expose your structural chaos. Also, slide fails, secret soap operas, and surviving BigCo absurdity.", "date_published": "2026-03-03T16:03:12+01:00", "url": "https://cote.io/2026/03/03/related-to-your-interests-tuesday.html", "tags": ["newsletter"] }, { "id": "http://cote.micro.blog/2026/03/02/diy-stacks-agent-memory-and.html", "title": "DIY Stacks, Agent Memory, and the Great Migration - Related to your interests, Monday", "content_html": "

Links! Wastebook! Background changes afoot!

\"A
Potsdamer Platz bei Nacht, Paul Paeschke, ca. 1929.

Related to your interests

\"Auto-generated

Wastebook

ICYMI

Logoff

We were at the beach for the past week. Always nice, the beach.

If all goes to plan, this will be the last newsletter I send with substack. I’ll move all the email addresses over, so if you’re. current subscriber, nothing to worry about, it’ll just happen. Tell me if it goes bonkers somehow.

I have a bad habit of migrating stuff without much care for preserving existing links. ¯_(ツ)_/¯

I think having everything here at the blog will be good.

The plan is: any blog post that’s in the “Related to your interests” category will be sent as a newsletter email. I shall do just one of those a day. This means there is some duplication if you read my blog and subscribe to the newsletter. But how many people do that? I’ve accidentally-cleverly changed the link section title to “Related to your interests” (instead of “Relative”). There’s some fun “this is the new thing” signaling. And, I think instead of “Original Content,” I’ll use the section title “ICYMI” to be self-promotional material.

We’ll see.

\n", "date_published": "2026-03-02T15:17:53+01:00", "url": "https://cote.io/2026/03/02/diy-stacks-agent-memory-and.html", "tags": ["newsletter"] }, { "id": "http://cote.micro.blog/2026/03/02/related-to-your-interests-monday.html", "title": "Related to your interests, Monday", "content_html": "
\n\n\"A\n
\n\nPotsdamer Platz bei Nacht, Paul Paeschke, ca. 1929.\n
\n
\n

Related to your interests

\n\n
\n\"Auto-generated\n
\n

Wastebook

\n\n

ICYMI

\n\n

Logoff

\n

We were at the beach for the past week. Always nice, the beach.

\n

If all goes to plan, this will be the last newsletter I send with substack. I’ll move all the email addresses over, so if you’re. current subscriber, nothing to worry about, it’ll just happen. Tell me if it goes bonkers somehow.

\n

I have a bad habit of migrating stuff without much care for preserving existing links. ¯_(ツ)_/¯

\n

I think having everything here at the blog will be good.

\n

The plan is: any blog post that’s in the “Related to your interests” category will be sent as a newsletter email. I shall do just one of those a day. This means there is some duplication if you read my blog and subscribe to the newsletter. But how many people do that? I’ve accidentally-cleverly changed the link section title to “Related to your interests” (instead of “Relative”). There’s some fun “this is the new thing” signaling. And, I think instead of “Original Content,” I’ll use the section title “ICYMI” to be self-promotional material.

\n

We’ll see.

\n", "date_published": "2026-03-02T15:12:41+01:00", "url": "https://cote.io/2026/03/02/related-to-your-interests-monday.html", "tags": ["links","Related to Your Interests"] }, { "id": "http://cote.micro.blog/2026/03/02/kubernetes-alone-does-not-a.html", "title": "Kubernetes alone does not a platform make", "content_html": "

Even the platform engineers need to hide Kubernetes to get their job done:

\n
\n

Kubernetes adds another layer of complexity for platform engineering teams, introducing architectural complexities that require a deep understanding of containers, networking, storage, and cluster security protocols. While it has become the default runtime for modern applications, managing Kubernetes at scale alongside existing VM‑based workloads can overwhelm platform engineering teams. YAML sprawl, cluster life-cycle management, networking dependencies, and security controls consume time that should be spent improving the developer experience and can lead to costly human error.

\n

As a result, many platform engineering teams find themselves serving as infrastructure integrators rather than product engineering teams. They spend cycles wiring systems together, maintaining custom automation, and resolving edge cases between environments. What’s needed is access to solutions that provide an automated infrastructure layer, allowing platform engineers to focus on productizing the platform rather than assembling it.

\n
\n

From “Platform Engineering Needs a Cloud Engine," Taka Uenishi.

\n", "date_published": "2026-03-02T14:56:53+01:00", "url": "https://cote.io/2026/03/02/kubernetes-alone-does-not-a.html" }, { "id": "http://cote.micro.blog/2026/02/22/does-platform-product-management-design.html", "title": "Does Platform Product Management \u0026 Design Really Happen? Or is it all just platform engineering? - Tanzu Catsup", "content_html": "\n

Most organizations treat infrastructure as a series of projects to be “completed,” but successful platform engineering requires a permanent product mindset. In this episode, we explore why platform teams need dedicated product management to balance competing priorities—like security, cost, and developer experience—and why the “why” scales much better than the “what” in large enterprises. We also dive into the often-overlooked role of designers in creating platform tools that developers actually want to use.

\n

Tanzu Catsup is a weekly conversation about platform engineering, cloud-native operations, and building software in large organizations. We follow the work wherever it actually leads.

\n

And, see the archives for Tanzu Catsup.

\n", "date_published": "2026-02-22T10:22:00+01:00", "url": "https://cote.io/2026/02/22/does-platform-product-management-design.html", "tags": ["videos","Tanzu"] }, { "id": "http://cote.micro.blog/2026/02/22/094400.html", "content_html": "\n

Developers crave AI tools for various tasks beyond coding, but that’s only about 20% of their work. But, ops people freak out about security and control challenges, like cost, regulatory compliance, and usage tracking.

\n", "date_published": "2026-02-22T09:44:00+01:00", "url": "https://cote.io/2026/02/22/094400.html", "tags": ["videos","tech","Tanzu"] }, { "id": "http://cote.micro.blog/2026/02/21/094200.html", "content_html": "\n

Bad advice from Wall Street on enterprise AI.

\n", "date_published": "2026-02-21T09:42:00+01:00", "url": "https://cote.io/2026/02/21/094200.html", "tags": ["videos","tech","Tanzu"] }, { "id": "http://cote.micro.blog/2026/02/20/automating-everything-but-changing-how.html", "title": "Automating everything but changing how people work - Relative to your interests, Friday", "content_html": "

Enterprise AI apps (or lack thereof), ROI surveys, CFO budget pivots, agile’s stubborn relevance, platform engineering vs. private cloud, Heroku’s freeze, IRS tech cuts, and Europe hedging on AI tools

\n
\n\n\"Auto-generated\n
\nPeter Klúcik's The Hobbit illustrations.\n\n
\n
\n

Related to your interests

\n\n
\n\"A\n
The Creative Power of the Spirit, No. 31 of A Goodly Company series, Ethel le Rossignol.
\n
\n\n

ICYMI

\n\n
\n\n\"A\n
\nMelany Lane typeface.\n
\n
\n

Logoff

\n

I’m still figuring out how to setup my newsletter at micro.blog, and move off substack. It doesn’t work yet, so I’m posting this manually to the newsletter list (via substack, sure). But, this means, though, if you’re reading the newsletter that you missed the episode from earlier this week. You can check it out here if you like links and original content.

\n\n", "date_published": "2026-02-20T11:30:30+01:00", "url": "https://cote.io/2026/02/20/automating-everything-but-changing-how.html", "tags": ["Related to Your Interests"] }, { "id": "http://cote.micro.blog/2026/02/20/you-can-feel-it-coming.html", "title": "You Can Feel It Coming - Software Defined Talk", "content_html": "\n

This week, we discuss personal AI hype cycles, bottoms-up adoption, and “The Modern Stack” simplifying cloud. Plus, thoughts on new cars and the dogs that ride in them.

\n

See the traditional podcast listing for links and more.

\n", "date_published": "2026-02-20T09:53:00+01:00", "url": "https://cote.io/2026/02/20/you-can-feel-it-coming.html", "tags": ["tech","podcasts"] }, { "id": "http://cote.micro.blog/2026/02/20/progressive-delivery-with-heidi-waterhouse.html", "title": "Progressive Delivery, with Heidi Waterhouse - Software Defined Interviews", "content_html": "\n

See the traditional podcast version for more and Heidi links.

\n", "date_published": "2026-02-20T09:51:19+01:00", "url": "https://cote.io/2026/02/20/progressive-delivery-with-heidi-waterhouse.html", "tags": ["tech","podcasts"] }, { "id": "http://cote.micro.blog/2026/02/20/why-its-great-to-be.html", "title": "Why it's great to be a Spring developer now, and how to make it even better - State of Spring, 2026", "content_html": "\n

This is a talk I give at the start of Spring workshops we do. Here is the recording. The point is to show people that being a Java and Spring developers is fantastic right now. Here’s the description:

\n

Spring developers are in a strange position in 2026: everything is changing: AI, platform engineering, enterprise architecture. And yet Spring keeps getting stronger.

\n

In this talk, Coté walks through why this is actually a great moment to be a Spring developer, especially in large organizations. He looks at:

\n\n

If you’re building enterprise application, working on internal platforms, or wondering how AI changes your day job, this is a grounded, pragmatic look at where Spring fits in 2026, and how to push it further.

\n

And here’s the slides.

\n", "date_published": "2026-02-20T09:09:38+01:00", "url": "https://cote.io/2026/02/20/why-its-great-to-be.html", "tags": ["videos","tech","Tanzu"] } ] }