Coté

The LinksWorkers who love ‘synergizing paradigms’ might be bad at their jobs - “The results revealed a troubling paradox. Workers who were more susceptible to corporate BS rated their supervisors as more charismatic and ‘visionary,’ but also displayed lower scores on a portion of the study that tested analytic thinking, cognitive reflection and fluid intelligence. Those more receptive to corporate BS also scored significantly worse on a test of effective workplace decision-making.

The LinksClaude, without me asking, rewrote many of my original description below. Enjoy! Pentagon Leverages AI in Iran Strikes Amid Feud With Anthropic - One artillery unit doing the work of 2,000 staff with a team of just 20 people. Anthropic didn’t want their model used for this; the Pentagon used it anyway. The future is here, it’s just unevenly distributed between PR statements and actual weapons targeting. Anthropic’s Pentagon Feud Accelerates Push Into Consumer Market - Claude’s free active users grew 60%+ and daily signups grew 4x since the start of the year.

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.

Our interview for this week is up, it’s with Josh Berkus: 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.

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.

Links! Wastebook! Background changes afoot! Potsdamer Platz bei Nacht, Paul Paeschke, ca. 1929.Related to your interestsWhy your DIY Kubernetes stack won’t survive the era of agentic AI How tech chiefs gauge ROI on AI - AI uses: better search, preparing leases, and this: “When the system senses that ice is running low, it fires off an order to AI agents, which begin routing trucks to fulfill orders. The system also takes into account historical sales trends, weather analytics and other factors to anticipate each route’s ice requirements.

Potsdamer Platz bei Nacht, Paul Paeschke, ca. 1929. Related to your interests Why your DIY Kubernetes stack won’t survive the era of agentic AI How tech chiefs gauge ROI on AI - AI uses: better search, preparing leases, and this: “When the system senses that ice is running low, it fires off an order to AI agents, which begin routing trucks to fulfill orders. The system also takes into account historical sales trends, weather analytics and other factors to anticipate each route’s ice requirements.

Even the platform engineers need to hide Kubernetes to get their job done: 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.

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.