<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Tim Benniks</title><description>Writing on developer experience, AI-accelerated engineering, and composable platforms.</description><link>https://timbenniks.dev</link><language>en-us</language><item><title>I thought everyone was building tools for themselves</title><link>https://timbenniks.dev/writing/i-thought-everyone-was-building-tools-for-themselves</link><guid isPermaLink="true">https://timbenniks.dev/writing/i-thought-everyone-was-building-tools-for-themselves</guid><description>At ContentCon, I realised building tools for yourself still feels unfamiliar to many developers. Coding agents help, but finding a starting point matters too.</description><pubDate>Mon, 05 Oct 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>craft</category><category>developer-experience</category><category>devrel</category></item><item><title>Building MCP Profile Hub part 3, when more reasoning makes the agent worse</title><link>https://timbenniks.dev/writing/building-mcp-profile-hub-part-3-when-more-reasoning-makes-the-agent-worse</link><guid isPermaLink="true">https://timbenniks.dev/writing/building-mcp-profile-hub-part-3-when-more-reasoning-makes-the-agent-worse</guid><description>This article explores an unexpected result from evaluating Contentstack’s MCP Profile Hub, where increasing a model’s reasoning effort made straightforward CMS agent tasks slower and less reliable. While enriching tool definitions with account-specific context clearly reduced tool calls, latency, and reasoning tokens, turning up the reasoning setting caused the model to distrust simple, correct tool responses and invent extra work. A control task listing global fields showed high-effort runs repeatedly ignoring a perfect API answer and exhausting their turn budget. The piece argues that reasoning effort must match the shape of the work, that bounded API operations often benefit from lower reasoning, and that agent evaluations should measure behaviour—calls, latency, traces, and early stopping—rather than abstract “intelligence” alone.</description><pubDate>Wed, 09 Sep 2026 10:00:00 GMT</pubDate><category>ai</category><category>api</category><category>cms</category><category>composable</category><category>architecture</category><category>webdev</category><category>performance</category></item><item><title>Skills over MCP explained: how the new extension delivers workflows alongside tools</title><link>https://timbenniks.dev/writing/skills-over-mcp-explained</link><guid isPermaLink="true">https://timbenniks.dev/writing/skills-over-mcp-explained</guid><description>How the new MCP Skills Extension works, from skill discovery and on-demand loading to content verification, workflow guidance, and managed profiles.</description><pubDate>Mon, 07 Sep 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>developer-experience</category><category>product-strategy</category></item><item><title>Building MCP Profile Hub part 2, one MCP server is the wrong abstraction</title><link>https://timbenniks.dev/writing/building-mcp-profile-hub-part-2-one-mcp-server-is-the-wrong-abstraction</link><guid isPermaLink="true">https://timbenniks.dev/writing/building-mcp-profile-hub-part-2-one-mcp-server-is-the-wrong-abstraction</guid><description>This article argues that a single, monolithic MCP server per platform is the wrong abstraction, especially for complex systems like Contentstack. Instead, it introduces managed profiles as the right unit of configuration, aligned to jobs, teams, or access boundaries rather than product catalogs. Each managed profile bundles a curated set of tools, Automations, and agents, enriched with account context, while still respecting individual user identities and permissions. Profiles can only narrow what a user can do, never expand their underlying platform permissions. This makes configurations easier to reason about, review, audit, and replicate across environments, and offers a scalable pattern for enterprise platforms with many roles and capabilities.</description><pubDate>Fri, 04 Sep 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>frontend</category><category>product-strategy</category></item><item><title>Building MCP Profile Hub, part 1: Stop making the agent ask</title><link>https://timbenniks.dev/writing/building-mcp-profile-hub-part-1-stop-making-the-agent-ask</link><guid isPermaLink="true">https://timbenniks.dev/writing/building-mcp-profile-hub-part-1-stop-making-the-agent-ask</guid><description>Introducing MCP Profile Hub. I explain why enriching tool definitions with tenant-specific context dramatically improves agent performance. Instead of exposing generic CMS tools that force models to discover content types, environments, locales, and branches through multiple lookup calls, Profile Hub injects real account data directly into JSON Schemas as enums, defaults, and descriptions. This reduces tool calls, latency, and reasoning tokens while avoiding misleading examples and invalid defaults. The piece also covers the production engineering behind enrichment, how Automations and Agent OS agents are exposed as high-level deterministic tools, and why reusable HTTP-based tool definitions let teams run their own MCP runtimes. The core takeaway is that fewer, richer, context-aware tools beat large generic catalogs for real-world agent workflows.</description><pubDate>Mon, 31 Aug 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>frontend</category><category>product-strategy</category></item><item><title>Claude Desktop MCP lifecycle is broken</title><link>https://timbenniks.dev/writing/claude-desktop-mcp-lifecycle-is-broken</link><guid isPermaLink="true">https://timbenniks.dev/writing/claude-desktop-mcp-lifecycle-is-broken</guid><description>Claude Desktop currently launches duplicate local MCP stdio servers for a single configuration, causing two independent OAuth flows, extra browser tabs, and unnecessary resource usage. The bug is masked once credentials are cached, so it silently persists in production while still spawning two processes every time. This is not an mcp-remote or external service issue but a host-level lifecycle problem, likely caused by overlapping legacy and new MCP managers and poor observability for one of the processes. Workarounds like pre-authenticating with mcp-remote mitigate UX pain but do not fix the duplication. The article argues that open-source tools should not shoulder complex coordination logic just to survive a major desktop app’s sloppy process management.</description><pubDate>Mon, 24 Aug 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>performance</category><category>cloud-infra</category><category>frontend</category></item><item><title>Buy the plumbing, vibe the rest</title><link>https://timbenniks.dev/writing/buy-the-plumbing-vibe-the-rest</link><guid isPermaLink="true">https://timbenniks.dev/writing/buy-the-plumbing-vibe-the-rest</guid><description>AI makes it tempting to cancel SaaS tools and prompt your own internal platforms into existence, but that often creates brittle systems that are “a mile wide and an inch deep.” Performance, security, and edge cases quickly become serious problems, and suddenly your team is doing database administration and security engineering instead of solving business problems. A better pattern is to buy robust, headless infrastructure for the hard, invisible parts (content, data, security, scaling) and then use AI to build bespoke experiences on top. With a solid SDK and stable backend services, AI tools like Claude can safely orchestrate UI and workflows instead of guessing at architecture. Pay for the plumbing, and vibe on the interface layer where your differentiation really lives.</description><pubDate>Sat, 22 Aug 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>developer-experience</category></item><item><title>The Doer Economy - we are killing the translator class</title><link>https://timbenniks.dev/writing/the-doer-economy-we-are-killing-the-translator-class</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-doer-economy-we-are-killing-the-translator-class</guid><description>This article argues that AI is collapsing the distance between vision and execution, ushering in a Doer Economy where the primary winners are those who can both imagine and build. The traditional corporate stack of translators (product managers, marketers, and multiple layers of management) is shrinking because executional tasks are increasingly handled by AI. Founders and CEOs are moving closer to product, validating ideas directly with AI-generated scaffolds and modern SaaS primitives. For individuals, the value has shifted from narrow, ticket-driven skills to end-to-end ownership, product thinking, and understanding users. The future belongs to people who ship, iterate quickly, and leverage AI and SaaS platforms to focus on business logic and user experience, rather than those who only manage the builders.</description><pubDate>Mon, 17 Aug 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>frontend</category><category>developer-experience</category></item><item><title>Ten AI security problems hiding in plain text</title><link>https://timbenniks.dev/writing/ten-ai-security-problems-hiding-in-plain-text</link><guid isPermaLink="true">https://timbenniks.dev/writing/ten-ai-security-problems-hiding-in-plain-text</guid><description>This article argues that AI security risks extend far beyond model jailbreaks and prompt engineering, into every piece of text an AI can read. Natural language now behaves like soft code, where logs, documentation, commit messages, wikis, support tickets, web pages, PDFs, and search results can all carry hidden instructions for agents. The author walks through ten concrete scenarios where ordinary text fields become attack surfaces, often with delayed or indirect activation through internal tools and multi agent pipelines. The core message is that information and instruction have blurred, and any text accessible to AI must be treated as part of the security model. Teams need to rethink access, editing rights, retrieval, and agent capabilities accordingly.</description><pubDate>Wed, 05 Aug 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>frontend</category><category>product-strategy</category></item><item><title>The biggest risk to AI is the enterprise org chart</title><link>https://timbenniks.dev/writing/the-biggest-risk-to-ai-is-the-enterprise-org-chart</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-biggest-risk-to-ai-is-the-enterprise-org-chart</guid><description>This article argues that the real risk of corporate AI is not rogue superintelligence but how large organizations deploy it, usually in service of cost-cutting rather than creating new value. Big enterprises buy AI like office furniture, wrapped in committees, procurement, and risk matrices, so it ends up optimizing ticket deflection and headcount instead of enabling innovation. The real bottleneck is bureaucracy, not intelligence. In contrast, a roughly 500-person company has enough depth to build serious systems but short enough communication paths that the person with the problem can help build the solution. AI lets domain experts prototype directly, shortening the loop between friction and fix. The key is governance that enables safe experimentation instead of vetoing it, using AI to expand reach rather than just reduce costs.</description><pubDate>Fri, 24 Jul 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>product-strategy</category><category>career</category></item><item><title>Your LinkedIn reads like a robot wrote it</title><link>https://timbenniks.dev/writing/your-linkedin-reads-like-a-robot</link><guid isPermaLink="true">https://timbenniks.dev/writing/your-linkedin-reads-like-a-robot</guid><description>Two free skills can strip the AI tells out of your writing in seconds. Nobody uses them. So every feed is now a slop fest of em dashes, rule-of-three lists, and It&apos;s not just X, it&apos;s Y. Here is how to spot the patterns and stop shipping them.</description><pubDate>Mon, 22 Jun 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>craft</category><category>product-strategy</category><category>career</category></item><item><title>We are thinking too small</title><link>https://timbenniks.dev/writing/we-are-thinking-too-small</link><guid isPermaLink="true">https://timbenniks.dev/writing/we-are-thinking-too-small</guid><description>AI coding agents are not a threat to developer jobs, they are a fundamental shift in the economics of software creation. Just as the cloud removed the risk and capital cost of infrastructure, AI is removing the cost of writing and refactoring code. This kills the old moats that protected horizontal enterprise platforms and makes rebuilding wide, deeply integrated stacks viable. Instead of spending years stitching together narrow SaaS tools and APIs, teams can let agents generate bespoke services quickly and cheaply. The real risk is using AI only to speed up legacy glue work. Developers who win will treat the cost of reinventing the wheel as effectively zero and pursue much larger, previously impossible product ideas.</description><pubDate>Sat, 20 Jun 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>frontend</category></item><item><title>Cursor&apos;s moat</title><link>https://timbenniks.dev/writing/cursors-moat</link><guid isPermaLink="true">https://timbenniks.dev/writing/cursors-moat</guid><description>The interesting story about Cursor is not which base model it uses, but how deeply it sits inside real software development workflows. Unlike model labs trained only on finished code artifacts, Cursor’s IDE sees every attempt, failure, context switch, and accepted edit as developers ship real software. That environment, with multiple models competing on the same tasks, produces rich feedback signals that are closer to “which path got the work done” than traditional preference data. The piece generalizes this idea beyond coding tools, suggesting that any serious AI product should focus on generating observable traces of work, outcomes, and corrections, and treat the product workflow itself as part of the training system and long-term moat.</description><pubDate>Wed, 17 Jun 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>devrel</category></item><item><title>Contentstack launched Agent OS, AXP, and the dev tools I have been itching to talk about</title><link>https://timbenniks.dev/writing/contentstack-launched-agent-os-axp-and-the-dev-tools</link><guid isPermaLink="true">https://timbenniks.dev/writing/contentstack-launched-agent-os-axp-and-the-dev-tools</guid><description>Contentstack just made Agent OS generally available, renamed the platform to AXP, and shipped a pile of developer tooling. I helped build the AI side, and I am happily biased about why this one is different.</description><pubDate>Tue, 09 Jun 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>developer-experience</category></item><item><title>The agentic spectrum: stop burning tokens on what a script can do</title><link>https://timbenniks.dev/writing/the-agentic-spectrum-stop-burning-tokens-on-what-a-script-can-do</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-agentic-spectrum-stop-burning-tokens-on-what-a-script-can-do</guid><description>AI workflows sit on a spectrum, from a single LLM-assisted task to a fully autonomous agent. Most real content work belongs near the low end, yet people keep reaching for the autonomous end and paying for it in tokens.</description><pubDate>Thu, 04 Jun 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>content-ops</category><category>cloud-infra</category></item><item><title>The tool catalog is the product</title><link>https://timbenniks.dev/writing/the-tool-catalog-is-the-product</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-tool-catalog-is-the-product</guid><description>We exposed Contentstack MCP tool definitions through a server endpoint as JSON. That sounds small, but it changes the product shape. The hosted MCP server becomes one official implementation of a reusable tool catalog, while developers can build their own MCPs with their own auth, hosting, filtering, and governance. This is what AI-first developer tooling should feel like: polished defaults on top of portable primitives.</description><pubDate>Wed, 27 May 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>api-design</category><category>developer-experience</category></item><item><title>AI will not live in one place, but trust has to</title><link>https://timbenniks.dev/writing/ai-will-not-live-in-one-place-but-trust-has-to</link><guid isPermaLink="true">https://timbenniks.dev/writing/ai-will-not-live-in-one-place-but-trust-has-to</guid><description>Enterprise AI is spreading into every tool where work happens, from IDE agents to browser assistants, but governance, spend control, and brand safety are lagging behind. This article explains a two-layer architecture for solving that tension. Off-platform AI, powered by APIs, MCP, and agent skills, acts as the reach layer that lets developers and teams experiment, prototype, and orchestrate across systems from within their preferred tools. On-platform AI, delivered through Agent OS, Polaris, and AI Credits, is the trust layer that handles permissions, spend visibility, brand context, review workflows, and auditability. Rather than choosing between open access and tight governance, enterprises should use both layers together so external AI gathers context while governed on-platform capabilities execute business-critical work safely.</description><pubDate>Mon, 18 May 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>content-ops</category><category>frontend</category></item><item><title>The Mini Shai-Hulud supply chain backlash will create worse software</title><link>https://timbenniks.dev/writing/the-supply-chain-backlash-will-create-worse-software</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-supply-chain-backlash-will-create-worse-software</guid><description>Supply-chain attacks like Mini Shai-Hulud will make teams distrust third-party packages. AI makes it easy to react by generating internal replacements for dependencies, SDK helpers, workflow tools, and glue code. That feels safer, but a lot of that code will be vibe coded without threat models, tests, update paths, or security review.</description><pubDate>Wed, 13 May 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>frontend</category><category>product-strategy</category></item><item><title>Development 101 for non-technical vibe coders</title><link>https://timbenniks.dev/writing/development-101-for-non-technical-vibe-coders</link><guid isPermaLink="true">https://timbenniks.dev/writing/development-101-for-non-technical-vibe-coders</guid><description>When folks think they&apos;re failing at AI coding, they&apos;re usually failing at their laptop. Before you brief an agent well, your machine has to be a predictable place.</description><pubDate>Mon, 04 May 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>craft</category><category>developer-experience</category></item><item><title>The case for boring setups</title><link>https://timbenniks.dev/writing/the-case-for-boring-setups</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-case-for-boring-setups</guid><description>Most developers overconfigure their machines and pay for it in ways they don&apos;t notice. Every custom alias, every remapped key, every hand-rolled config file is a small tax on your ability to work anywhere other than your own laptop. The same pattern is repeating right now with AI tooling, dozens of MCP servers and stacked skill files that look like leverage and behave like drag. After getting stranded by my own setups more times than I&apos;d like to admit, I&apos;ve come around to a quieter belief: portability is a skill, and defaults are how you practice it.</description><pubDate>Mon, 20 Apr 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>frontend</category><category>developer-experience</category></item><item><title>The vibe-coded app architecture guide</title><link>https://timbenniks.dev/writing/the-vibe-coded-app-architecture-guide</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-vibe-coded-app-architecture-guide</guid><description>The AI builds what you describe, not what you need in production. This guide covers the full architecture stack for vibe-coded apps - auth, database security, secrets, GDPR, audit logging, rate limiting, and dependencies - so you can ship fast and stay solid.</description><pubDate>Thu, 16 Apr 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>developer-experience</category></item><item><title>I will not log into your vibe coded app</title><link>https://timbenniks.dev/writing/i-will-not-log-into-your-vibe-coded-app</link><guid isPermaLink="true">https://timbenniks.dev/writing/i-will-not-log-into-your-vibe-coded-app</guid><description>Vibe coding has made it trivially easy to spin up apps that collect user data, handle logins, and store sensitive information. The problem is that most people building these apps have no idea how authentication, database security, or data protection actually work. Defaults on services like Supabase and Firebase are dangerously permissive, GDPR obligations are being ignored entirely, and users are handing credentials to apps built by people who have never heard of row level security. My personal rule now is simple. If it looks vibe coded and asks for username and password, I walk away.</description><pubDate>Tue, 14 Apr 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cloud-infra</category><category>frontend</category><category>product-strategy</category></item><item><title>Most CMS migrations fail before the first record moves</title><link>https://timbenniks.dev/writing/most-cms-migrations-fail-before-the-first-record-moves</link><guid isPermaLink="true">https://timbenniks.dev/writing/most-cms-migrations-fail-before-the-first-record-moves</guid><description>CMS migrations fail not because of the new platform but because nobody cleaned up the mess before packing it into boxes. Bad content models get locked in, integrations get reverse-engineered at midnight, legacy logic resurfaces as unexplainable bugs, and composable architecture without discipline becomes distributed chaos. The only thing worse than a painful migration is a successful one that preserved all your worst decisions.</description><pubDate>Mon, 30 Mar 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>frontend</category><category>product-strategy</category></item><item><title>The future of software is bespoke</title><link>https://timbenniks.dev/writing/the-future-of-software-is-bespoke</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-future-of-software-is-bespoke</guid><description>This article argues that generic SaaS dashboards are a legacy compromise from a time when custom software was expensive and slow to build. With modern APIs, solid SDKs, scaffolding, and AI-assisted development, teams can now create focused, bespoke interfaces in days that match their exact workflows, instead of fighting through one-size-fits-all UIs. The platform should be treated as the engine providing authentication, permissions, content modeling, and governance, while product teams own the experience layer tailored to their people. The piece also examines trade-offs like maintenance burden, skills gaps, and fragility, and explains how good scaffolding, community patterns, and developer education can mitigate these risks and make custom tooling a pragmatic default.</description><pubDate>Thu, 26 Mar 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category><category>developer-experience</category></item><item><title>We moved the difficulty. We didn&apos;t make it disappear.</title><link>https://timbenniks.dev/writing/we-moved-the-difficulty</link><guid isPermaLink="true">https://timbenniks.dev/writing/we-moved-the-difficulty</guid><description>In 2013 I built the Need for Speed Rivals launch site from scratch in five weeks - custom router, custom state, custom tweening engine, 35 languages, no framework worth mentioning. I rebuilt it recently for my Vue.js Amsterdam 2026 talk. The contrast broke my brain in the best way, and it clarified something I&apos;ve been trying to articulate about AI, abstraction, and what &quot;craft&quot; actually means now.</description><pubDate>Tue, 17 Mar 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>craft</category><category>career</category></item><item><title>Intuition and the real cost of research</title><link>https://timbenniks.dev/writing/the-best-product-decisions-were-never-analytical</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-best-product-decisions-were-never-analytical</guid><description>This article explores how AI changes the balance between research-heavy processes and intuition-driven building, especially in product and technical work. The author reflects on a career of moving faster than surrounding teams, where strong intuition (really compressed experience from shipping many similar things) often clashed with expectations for lengthy research and documentation. As AI makes implementation and iteration dramatically cheaper and faster, the true bottleneck shifts from building to deciding what is worth building. Research still matters for those without established mental models, and for environments where stakeholders need evidence and paper trails. But when iteration costs hours instead of weeks, over-indexing on analysis can become the real drag. The piece argues that, in an AI-enabled world, experienced intuition is not anti-process; for the right people and problems, it is the process.</description><pubDate>Tue, 10 Mar 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>product-strategy</category><category>career</category></item><item><title>Code is craft now, not labor</title><link>https://timbenniks.dev/writing/code-is-craft-now-not-labor</link><guid isPermaLink="true">https://timbenniks.dev/writing/code-is-craft-now-not-labor</guid><description>Coding is largely solved. Agents with a great product vision can produce what used to take teams weeks. But the act of writing code by hand isn&apos;t dying - it&apos;s transforming from a necessity into a craft. Like knitting, you won&apos;t need to do it. You&apos;ll choose to.</description><pubDate>Wed, 25 Feb 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>craft</category><category>career</category><category>personal</category></item><item><title>Codex built a skill with custom CLI for itself. Is MCP even a thing anymore?</title><link>https://timbenniks.dev/writing/openai-codex-built-a-skill-for-itself-is-mcp-even-a-thing-anymore</link><guid isPermaLink="true">https://timbenniks.dev/writing/openai-codex-built-a-skill-for-itself-is-mcp-even-a-thing-anymore</guid><description>I gave OpenAI Codex a management token, an API key, some YouTube IDs, and my Contentstack TypeScript schema. It imported all my content flawlessly, then wrote a custom CLI and a skill to do it again. I did not ask it to do that. Now I&apos;m wondering if we&apos;ve been overcomplicating everything.</description><pubDate>Fri, 20 Feb 2026 14:30:22 GMT</pubDate><category>ai-engineering</category><category>developer-experience</category></item><item><title>I&apos;m cosplaying as a Product Manager, and I think I&apos;m onto something</title><link>https://timbenniks.dev/writing/cosplaying-as-a-product-manager-and-i-think-im-onto-something</link><guid isPermaLink="true">https://timbenniks.dev/writing/cosplaying-as-a-product-manager-and-i-think-im-onto-something</guid><description>After twenty years of engineering, I accidentally ended up running multiple product lines. My approach (build first, spec later, let AI handle the translation) isn&apos;t traditional PM work. But it might be where the role is heading. Here&apos;s why engineers who produce before they plan might have an unfair advantage in the age of AI.</description><pubDate>Sat, 14 Feb 2026 10:00:00 GMT</pubDate><category>craft</category><category>product-strategy</category><category>career</category></item><item><title>TDD finally makes sense</title><link>https://timbenniks.dev/writing/tdd-finally-makes-sense</link><guid isPermaLink="true">https://timbenniks.dev/writing/tdd-finally-makes-sense</guid><description>AI coding tools have removed the old excuse that test driven development is too slow or too costly. When AI can generate both implementation and test scaffolding in minutes, the time cost of writing tests first collapses, turning TDD into an obvious quality and productivity win. The real risk now is vibe coding, where developers ship AI generated code that looks fine but crumbles under real edge cases. By using AI for planning, then encoding that thinking as tests and letting the AI implement against them, teams get faster feedback, more reliable code, and fewer hotfixes. In an AI assisted world, the competitive advantage shifts to defining behavior and edge cases up front, and TDD becomes the discipline that makes that thinking explicit.</description><pubDate>Wed, 11 Feb 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>frontend</category><category>product-strategy</category><category>career</category></item><item><title>When Output Is Cheap, Taste Is Everything</title><link>https://timbenniks.dev/writing/when-output-is-cheap-taste-is-everything</link><guid isPermaLink="true">https://timbenniks.dev/writing/when-output-is-cheap-taste-is-everything</guid><description>This article explores how AI has radically reduced the cost of producing things, creating an intoxicating sense of limitless output for ambitious people. But when building becomes almost frictionless, the real bottleneck shifts from implementation to judgment. The author argues that taste (the ability to choose what is worth building) and genuine rest become the true sources of leverage. AI is an exceptional how engine, but deciding what and why remains a deeply human responsibility. Without rest, our judgment degrades, and we risk building more but meaning less. The piece encourages pairing curiosity and experimentation with discipline, restraint, and strategic downtime.</description><pubDate>Sun, 08 Feb 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>product-strategy</category><category>career</category><category>personal</category></item><item><title>Plot twist! AI made developers more valuable.</title><link>https://timbenniks.dev/writing/ai-is-not-replacing-developers-it-is-exposing-everyone-else</link><guid isPermaLink="true">https://timbenniks.dev/writing/ai-is-not-replacing-developers-it-is-exposing-everyone-else</guid><description>For the last year, the dominant narrative has been that AI will replace developers. I think that narrative has it backwards. AI doesn&apos;t replace developers - it raises the bar for everyone else to justify their seat next to someone who can now ship at absurd velocity.</description><pubDate>Wed, 04 Feb 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>developer-experience</category></item><item><title>Do we still need SDKs in the age of AI agents?</title><link>https://timbenniks.dev/writing/do-we-still-need-sdks-in-the-age-of-ai-agents</link><guid isPermaLink="true">https://timbenniks.dev/writing/do-we-still-need-sdks-in-the-age-of-ai-agents</guid><description>With good APIs and OpenAPI specs, AI agents can generate production-ready clients in seconds. This challenges everything we know about SDK development and distribution. But are we ready to let go?</description><pubDate>Thu, 29 Jan 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>api-design</category><category>developer-experience</category></item><item><title>DevRel success metrics that actually matter</title><link>https://timbenniks.dev/writing/devrel-success-metrics-that-actually-matter</link><guid isPermaLink="true">https://timbenniks.dev/writing/devrel-success-metrics-that-actually-matter</guid><description>When the market stops buying, vanity metrics stop mattering. Here&apos;s how to measure DevRel impact in ways that executives understand and that correlate with real business outcomes like ARR growth.</description><pubDate>Tue, 27 Jan 2026 10:00:00 GMT</pubDate><category>developer-experience</category><category>devrel</category></item><item><title>Your legacy patterns are technical debt in modern architecture</title><link>https://timbenniks.dev/writing/your-legacy-patterns-are-technical-debt-in-modern-architecture</link><guid isPermaLink="true">https://timbenniks.dev/writing/your-legacy-patterns-are-technical-debt-in-modern-architecture</guid><description>Developer teams migrating from legacy to modern architecture often bring old habits that become technical debt. Executive pressure and budget constraints drive rushed migrations without adapting to new paradigms. Success requires stopping to discover how modern systems actually work, designing ideal workflows without legacy constraints, and recognizing that migration is about transforming how you model and manage content, not just moving it between systems.</description><pubDate>Mon, 26 Jan 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>craft</category></item><item><title>The pragmatic guide to coding with AI agents</title><link>https://timbenniks.dev/writing/the-pragmatic-guide-to-coding-with-ai-agents</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-pragmatic-guide-to-coding-with-ai-agents</guid><description>AI agents are extremely capable coding assistants, but they are not magical autonomous engineers. Treat them like very fast junior developers who need clear scope, clean environments, and strong guardrails. Avoid context gluttony by limiting inputs to only the files and details needed for the task, and rely on search instead of dumping entire repositories. Skip over engineered MCP setups and excessive plugins in favor of simple, well understood tools. Fix your project environment so builds and checks run cleanly from the root. Use planning steps, a project specific “gotchas” file, tests as guardrails, and tightly scoped tasks to keep agents effective, predictable, and safe in real-world production work.</description><pubDate>Sun, 25 Jan 2026 10:00:00 GMT</pubDate><category>ai-engineering</category><category>frontend</category></item><item><title>Want to be better at vibe coding? Become a better coder</title><link>https://timbenniks.dev/writing/want-to-be-better-at-vibe-coding-become-a-better-coder</link><guid isPermaLink="true">https://timbenniks.dev/writing/want-to-be-better-at-vibe-coding-become-a-better-coder</guid><description>The promise of AI-powered development is seductive, but here&apos;s the reality check nobody&apos;s talking about - the better you understand code, the better your AI-generated results will be. LLMs code like humans with high IQs and unstoppable work ethic. Treat them as junior developers and learn the fundamentals to multiply your vibe coding power.</description><pubDate>Mon, 12 Jan 2026 15:00:00 GMT</pubDate><category>ai-engineering</category><category>api-design</category><category>cloud-infra</category><category>craft</category><category>developer-experience</category></item><item><title>MCP fragmentation, context efficiency, and the rise of curated skills</title><link>https://timbenniks.dev/writing/mcp-fragmentation-context-efficiency-and-the-rise-of-curated-skills</link><guid isPermaLink="true">https://timbenniks.dev/writing/mcp-fragmentation-context-efficiency-and-the-rise-of-curated-skills</guid><description>The Model Context Protocol (MCP) was supposed to be a universal way to connect AI models to tools, but in practice it is fragmenting fast across vendors and implementations. Tool catalogs are extremely context-hungry, making naive MCP setups expensive, slow, and unreliable, especially with cheaper models. Developers are compensating with application-layer tricks like curated tool subsets, OAuth-based selection, Claude Skills style abstractions, and wrapping deterministic automation platforms such as Contentstack Automate. These patterns improve cost, reliability, and debuggability but highlight protocol-level gaps in context efficiency, determinism, and interoperability. The ecosystem is replaying past standards wars, and no clear winner is visible yet. The pragmatic move is to design flexible systems that can adapt when consolidation and better standards eventually emerge.</description><pubDate>Fri, 09 Jan 2026 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>performance</category><category>cloud-infra</category></item><item><title>Cursor, rules, and my vibe engineer workflow</title><link>https://timbenniks.dev/writing/cursor-rules-and-my-vibe-engineer-workflow</link><guid isPermaLink="true">https://timbenniks.dev/writing/cursor-rules-and-my-vibe-engineer-workflow</guid><description>I released my Cursor rules and commands as a public repo because Cursor is not magic, it is leverage. By turning it into a constrained system with explicit rules, reusable commands, and real project context, you can make it behave like a senior engineer on SaaS projects. The real win is not speed, but trust at speed.</description><pubDate>Tue, 16 Dec 2025 10:00:00 GMT</pubDate><category>ai-engineering</category><category>frontend</category><category>developer-experience</category><category>product-strategy</category></item><item><title>AI integrations expose platforms without headless DNA</title><link>https://timbenniks.dev/writing/ai-native-composability-needs-real-api-first-dna</link><guid isPermaLink="true">https://timbenniks.dev/writing/ai-native-composability-needs-real-api-first-dna</guid><description>AI exposes which platforms were truly built API first and which ones only marketed it. As brands move into AI native workflows, the only viable path is a system that treats agents, events, and automation as composable building blocks. Contentstack&apos;s agentOS shows what happens when you start with API first DNA instead of bolting AI onto a monolithic core. This piece explains why AI native composability is the next logical layer of MACH and why brands should judge vendors by the architecture of their agents, not the slideware that surrounds them.</description><pubDate>Tue, 02 Dec 2025 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cms</category><category>api-design</category><category>content-ops</category></item><item><title>The Experience Factory why experience is the real flagship</title><link>https://timbenniks.dev/writing/the-experience-factory-01-why-experience-is-the-real-flagship</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-experience-factory-01-why-experience-is-the-real-flagship</guid><description>Many brands think they&apos;re digitally mature, yet their experience operations are fragmented. Here&apos;s how to spot it and start orchestrating.</description><pubDate>Mon, 01 Dec 2025 10:00:00 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>content-ops</category><category>frontend</category></item><item><title>The MACH monolith in 2026</title><link>https://timbenniks.dev/writing/the-mach-monolith-in-2026</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-mach-monolith-in-2026</guid><description>The 2022 diagnosis was right. Composable architectures need orchestration or they collapse. But the form factor was wrong. Teams rejected standalone orchestration layers as too heavy, another vendor, contract, and critical path. The 2026 reality is platforms that integrate orchestration directly, staying API-first and modular while providing built-in coordination. The shift isn&apos;t about more tools, but smarter platforms that reduce complexity fatigue without losing flexibility.</description><pubDate>Mon, 17 Nov 2025 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cms</category><category>api-design</category><category>content-ops</category></item><item><title>The DevRel Operating System</title><link>https://timbenniks.dev/writing/devrel-os</link><guid isPermaLink="true">https://timbenniks.dev/writing/devrel-os</guid><description>Developer Relations is most effective when treated not as marketing, not as community management, and not as evangelism, but as a disciplined operating system for improving the developer journey. DevRel succeeds when it brings clarity to complexity, reduces cognitive load, and creates repeatable success for developers. To do that, teams need frameworks, not just intentions.</description><pubDate>Sat, 08 Nov 2025 10:00:00 GMT</pubDate><category>devrel</category></item><item><title>It&apos;s time to think of LLMs as having abilities, not protocols</title><link>https://timbenniks.dev/writing/its-time-to-think-of-llms-as-having-abilities-not-protocols</link><guid isPermaLink="true">https://timbenniks.dev/writing/its-time-to-think-of-llms-as-having-abilities-not-protocols</guid><description>TL;DR Don&apos;t over-engineer standards around protocols. Instead, treat your large-language-model as a toolbox of abilities (like search, translate, query, generate) that you plug into your system. By thinking of LLMs as modular and composable abilities rather than monolithic protocols, AI becomes accessible, practical and aligned with how engineering and product teams already build.</description><pubDate>Fri, 07 Nov 2025 10:00:00 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cms</category><category>api-design</category><category>content-ops</category></item><item><title>The Age of the &quot;Super-T&quot; Product Person</title><link>https://timbenniks.dev/writing/the-age-of-the-super-t-product-person</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-age-of-the-super-t-product-person</guid><description>AI is dissolving silos and creating a new kind of product person who thinks like a system, connects disciplines, and prototypes ideas before lunch.</description><pubDate>Tue, 07 Oct 2025 10:00:00 GMT</pubDate><category>ai-engineering</category><category>product-strategy</category></item><item><title>The Future of CMS. It&apos;s dying.</title><link>https://timbenniks.dev/writing/the-future-of-cms-from-content-management-to-context-management</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-future-of-cms-from-content-management-to-context-management</guid><description>The CMS is evolving from static publishing to dynamic context management, where AI agents adapt every experience in real time. Welcome to the Context Economy.</description><pubDate>Sun, 05 Oct 2025 20:37:36 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cms</category><category>personalization</category><category>content-ops</category></item><item><title>AI chat interfaces will replace web apps</title><link>https://timbenniks.dev/writing/ai-chat-interfaces-will-replace-web-apps</link><guid isPermaLink="true">https://timbenniks.dev/writing/ai-chat-interfaces-will-replace-web-apps</guid><description>A firsthand look at how AI-driven chat interfaces could reshape SaaS and user interaction.</description><pubDate>Sat, 04 Oct 2025 20:37:36 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>cms</category><category>api-design</category><category>content-ops</category></item><item><title>Build context-aware MCPs, not API wrappers</title><link>https://timbenniks.dev/writing/build-context-aware-mcp-not-api-wrappers</link><guid isPermaLink="true">https://timbenniks.dev/writing/build-context-aware-mcp-not-api-wrappers</guid><description>MCP servers shouldn&apos;t just expose endpoints, they should adapt to their environment, using project context to guide AI reasoning and execution.</description><pubDate>Sat, 04 Oct 2025 20:37:36 GMT</pubDate><category>composable-architecture</category><category>ai-engineering</category><category>api-design</category><category>performance</category><category>developer-experience</category></item><item><title>The nuanced impact of AI we should not overlook</title><link>https://timbenniks.dev/writing/the-nuanced-impact-of-ai-we-should-not-overlook</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-nuanced-impact-of-ai-we-should-not-overlook</guid><description>AI&apos;s impact on the tech industry is more nuanced than often claimed, offering modest productivity improvements while blurring role specializations and fostering a more versatile, holistic approach to development.</description><pubDate>Tue, 04 Feb 2025 13:05:48 GMT</pubDate><category>ai-engineering</category><category>career</category></item><item><title>We have collectively forgotten what monoliths are</title><link>https://timbenniks.dev/writing/we-have-collectively-forgotten-what-monoliths-are</link><guid isPermaLink="true">https://timbenniks.dev/writing/we-have-collectively-forgotten-what-monoliths-are</guid><description>Exploring the misconception of modern CMS platforms as monoliths and clarifying the distinctions between true monolithic systems and today&apos;s flexible, API-driven content management solutions.</description><pubDate>Fri, 10 Jan 2025 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category><category>product-strategy</category></item><item><title>Universal CMS the wheel we&apos;re reinventing</title><link>https://timbenniks.dev/writing/universal-cms-the-wheel-we-are-reinventing</link><guid isPermaLink="true">https://timbenniks.dev/writing/universal-cms-the-wheel-we-are-reinventing</guid><description>Universal CMS reshapes CMS by blending headless and traditional, empowering developers and content creators. But are we reinventing the wheel here?</description><pubDate>Wed, 13 Nov 2024 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category><category>developer-experience</category></item><item><title>SDKs are everywhere. But should you use them?</title><link>https://timbenniks.dev/writing/sdks-use-them-or-not</link><guid isPermaLink="true">https://timbenniks.dev/writing/sdks-use-them-or-not</guid><description>Explore the significance of Software Development Toolkits (SDKs) in modern development, their advantages, and when you might want to skip them. From enhancing productivity to integrating complex functionalities seamlessly, the right SDK can accelerate your projects. But what about GraphQL-based systems or the flexibility of headless architectures? Dive into the pros and cons to make an informed decision.</description><pubDate>Sun, 29 Sep 2024 12:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>performance</category><category>frontend</category></item><item><title>The different approaches to visual editing in headless CMS</title><link>https://timbenniks.dev/writing/different-approaches-to-visual-editing</link><guid isPermaLink="true">https://timbenniks.dev/writing/different-approaches-to-visual-editing</guid><description>This article compares different approaches to visual editing in headless CMS platforms, outlining the benefits and tradeoffs of options ranging from basic previews to full WYSIWYG editors.</description><pubDate>Thu, 25 Jul 2024 10:32:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category></item><item><title>How I supercharched my website&apos;s speed</title><link>https://timbenniks.dev/writing/how-i-supercharched-my-websites-speed</link><guid isPermaLink="true">https://timbenniks.dev/writing/how-i-supercharched-my-websites-speed</guid><description>In this blog post, I want to share how I transformed my website into the fastest site I&apos;ve ever built. I&apos;ll walk you through the steps, my unconventional decisions, and the tools I used to achieve this feat.</description><pubDate>Mon, 01 Jul 2024 13:05:48 GMT</pubDate><category>performance</category><category>cloud-infra</category><category>frontend</category></item><item><title>Choosing the right visual editor for your website Platform-First vs. Code-First</title><link>https://timbenniks.dev/writing/choosing-the-right-visual-editor</link><guid isPermaLink="true">https://timbenniks.dev/writing/choosing-the-right-visual-editor</guid><description>This post explores two main types of visual editors platform-first and code-first. I compare their functionalities, pros, and cons to help you choose the right solution for your development needs.</description><pubDate>Fri, 28 Jun 2024 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category><category>developer-experience</category></item><item><title>Your team is the key to success when going headless</title><link>https://timbenniks.dev/writing/team-is-key-when-going-headless</link><guid isPermaLink="true">https://timbenniks.dev/writing/team-is-key-when-going-headless</guid><description>People&apos;s choices, ability to roll with the punches, and how well they play in the sandbox together bring the magic of headless technology to life.</description><pubDate>Mon, 29 Apr 2024 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>frontend</category><category>product-strategy</category></item><item><title>CMS Showdown do you need a page builder or a data modeler?</title><link>https://timbenniks.dev/writing/page-builder-cms-vs-data-modeler-cms</link><guid isPermaLink="true">https://timbenniks.dev/writing/page-builder-cms-vs-data-modeler-cms</guid><description>Explore the differences between page builder and data modeler CMSs, their unique features, and how they cater to varying organizational needs.</description><pubDate>Tue, 12 Mar 2024 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>content-ops</category><category>frontend</category><category>product-strategy</category></item><item><title>The content Graph is the future</title><link>https://timbenniks.dev/writing/the-content-graph-is-the-future</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-content-graph-is-the-future</guid><description>Content management is as essential as it is complex, especially at scale. As brands grow, they often...</description><pubDate>Tue, 05 Dec 2023 10:40:00 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>performance</category><category>frontend</category></item><item><title>What type of content organization do you need?</title><link>https://timbenniks.dev/writing/what-type-of-content-organization-do-you-need</link><guid isPermaLink="true">https://timbenniks.dev/writing/what-type-of-content-organization-do-you-need</guid><description>Different ways of working require different approaches to content design. In this post, I will...</description><pubDate>Sun, 12 Nov 2023 09:03:33 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>content-ops</category><category>frontend</category></item><item><title>The real deal about content management buzzwords</title><link>https://timbenniks.dev/writing/the-real-deal-about-content-management-buzzword</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-real-deal-about-content-management-buzzword</guid><description>Buzzwords are labels that describe tech approaches that become so commonplace over time that the...</description><pubDate>Thu, 28 Sep 2023 14:43:37 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>cloud-infra</category><category>frontend</category></item><item><title>The future of headless CMS Content Federation with GraphQL</title><link>https://timbenniks.dev/writing/the-future-of-headless-cms-content-federation-with-graphql</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-future-of-headless-cms-content-federation-with-graphql</guid><description>Federation is a popular topic of conversation these days, and for good reason. With the ever-growing...</description><pubDate>Thu, 28 Sep 2023 14:39:16 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>content-ops</category><category>cloud-infra</category></item><item><title>New job alert - Hygraph 2023</title><link>https://timbenniks.dev/writing/new-job-alert</link><guid isPermaLink="true">https://timbenniks.dev/writing/new-job-alert</guid><description>After an exciting journey at Uniform, it&apos;s time for a new adventure. At Uniform, we thrived during...</description><pubDate>Wed, 16 Aug 2023 13:42:10 GMT</pubDate><category>cms</category><category>product-strategy</category><category>devrel</category></item><item><title>This is headless 2.0</title><link>https://timbenniks.dev/writing/this-is-headless-20</link><guid isPermaLink="true">https://timbenniks.dev/writing/this-is-headless-20</guid><description>That’s a bold title, but it’s high time to change how we work with headless technology. I wrote about...</description><pubDate>Tue, 11 Jul 2023 07:48:19 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>performance</category><category>frontend</category></item><item><title>The lost promise of headless</title><link>https://timbenniks.dev/writing/the-lost-promise-of-headless</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-lost-promise-of-headless</guid><description>In recent years, headless technology, which boosts performance, developer experience, and...</description><pubDate>Mon, 26 Jun 2023 18:18:19 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>performance</category><category>frontend</category></item><item><title>Level up your collaboration game Developer insights for winning with marketing pros</title><link>https://timbenniks.dev/writing/level-up-your-collaboration-game-developer-insights-for-winning-with-marketing-pro</link><guid isPermaLink="true">https://timbenniks.dev/writing/level-up-your-collaboration-game-developer-insights-for-winning-with-marketing-pro</guid><description>Building outstanding user experiences takes, first and foremost, effective collaboration between...</description><pubDate>Wed, 03 May 2023 15:49:29 GMT</pubDate><category>performance</category><category>product-strategy</category><category>devrel</category></item><item><title>How to get your webcam to look decent in a few simple steps</title><link>https://timbenniks.dev/writing/how-to-get-your-webcam-to-look-decent-in-a-few-simple-steps</link><guid isPermaLink="true">https://timbenniks.dev/writing/how-to-get-your-webcam-to-look-decent-in-a-few-simple-steps</guid><description>If you have used a webcam before you know what it means to look like shit on camera. Even the most...</description><pubDate>Mon, 20 Mar 2023 13:01:35 GMT</pubDate><category>content-ops</category><category>developer-experience</category><category>devrel</category><category>media-production</category></item><item><title>Why I didn&apos;t run the 2016 marathon</title><link>https://timbenniks.dev/writing/why-i-didnt-run-the-2016-marathon</link><guid isPermaLink="true">https://timbenniks.dev/writing/why-i-didnt-run-the-2016-marathon</guid><description>After four and a half months of full on training I’ve decided not to run the Amsterdam marathon on...</description><pubDate>Sat, 18 Mar 2023 22:52:37 GMT</pubDate><category>personal</category></item><item><title>The 2015 Paris marathon</title><link>https://timbenniks.dev/writing/the-2015-paris-maratho</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-2015-paris-maratho</guid><description>Exactly one year ago, when we had just moved to Paris, the marathon passed by our apartment in Rue...</description><pubDate>Sat, 18 Mar 2023 22:45:48 GMT</pubDate><category>personal</category></item><item><title>My Fitness Story</title><link>https://timbenniks.dev/writing/my-fitness-story</link><guid isPermaLink="true">https://timbenniks.dev/writing/my-fitness-story</guid><description>From fat and sick to slim and happy   Aside from a short period in high school I have always...</description><pubDate>Sat, 18 Mar 2023 22:39:46 GMT</pubDate><category>personal</category></item><item><title>Make the Web Greener, Luxury Edition</title><link>https://timbenniks.dev/writing/make-the-web-greener-luxury-edition</link><guid isPermaLink="true">https://timbenniks.dev/writing/make-the-web-greener-luxury-edition</guid><description>If the internet were a country, it would be the world’s sixth biggest polluter.   The...</description><pubDate>Sat, 18 Mar 2023 22:30:27 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>performance</category><category>cloud-infra</category><category>frontend</category></item><item><title>How to dynamically stream video</title><link>https://timbenniks.dev/writing/how-to-dynamically-stream-video</link><guid isPermaLink="true">https://timbenniks.dev/writing/how-to-dynamically-stream-video</guid><description>Build it yourself or use Cloudinary   Dynamic video streaming is a video delivery technique...</description><pubDate>Sat, 18 Mar 2023 21:56:45 GMT</pubDate><category>performance</category><category>cloud-infra</category><category>frontend</category><category>developer-experience</category><category>devrel</category></item><item><title>Uniform is Nuxt 3 ready</title><link>https://timbenniks.dev/writing/uniform-is-nuxt-3-read</link><guid isPermaLink="true">https://timbenniks.dev/writing/uniform-is-nuxt-3-read</guid><description>We are excited to announce that the latest iteration of the Uniform SDK is fully compatible with Vue...</description><pubDate>Sat, 18 Mar 2023 13:10:06 GMT</pubDate><category>frontend</category></item><item><title>Digital experience platforms the old versus the new</title><link>https://timbenniks.dev/writing/digital-experience-platforms-the-old-versus-the-new</link><guid isPermaLink="true">https://timbenniks.dev/writing/digital-experience-platforms-the-old-versus-the-new</guid><description>Digital experience platforms (DXPs) and the more modern digital experience composition platforms...</description><pubDate>Sat, 18 Mar 2023 13:05:48 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>content-ops</category><category>cloud-infra</category></item><item><title>Uniform DXCP the what, why, and how</title><link>https://timbenniks.dev/writing/uniform-dxcp-the-what-why-and-how</link><guid isPermaLink="true">https://timbenniks.dev/writing/uniform-dxcp-the-what-why-and-how</guid><description>Nowadays, you’re hard pressed to find an application with all the functionalities you need for...</description><pubDate>Sat, 18 Mar 2023 13:03:16 GMT</pubDate><category>composable-architecture</category><category>performance</category></item><item><title>How to sniff out the Glue Monster</title><link>https://timbenniks.dev/writing/how-to-sniff-out-the-glue-monster</link><guid isPermaLink="true">https://timbenniks.dev/writing/how-to-sniff-out-the-glue-monster</guid><description>Even though you don’t see it, glue code is everywhere. Since the pendulum swung from monolithic...</description><pubDate>Sat, 18 Mar 2023 13:00:21 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>performance</category><category>frontend</category></item><item><title>The future of managing projects at agencies</title><link>https://timbenniks.dev/writing/the-future-of-managing-projects-at-agencie</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-future-of-managing-projects-at-agencie</guid><description>Calling for a revolution in how agencies run tech projects   I spent a lot of time working...</description><pubDate>Sat, 18 Mar 2023 12:56:10 GMT</pubDate><category>composable-architecture</category><category>product-strategy</category></item><item><title>Fast, personalized pages with Vercel Edge Middleware and Uniform</title><link>https://timbenniks.dev/writing/fast-personalized-pages-with-vercel-edge-middleware-and-uniform</link><guid isPermaLink="true">https://timbenniks.dev/writing/fast-personalized-pages-with-vercel-edge-middleware-and-uniform</guid><description>To maintain an engaging relationship with your audience and increase conversions to your site, you...</description><pubDate>Sat, 18 Mar 2023 12:49:56 GMT</pubDate><category>composable-architecture</category><category>cms</category><category>api-design</category><category>personalization</category><category>performance</category></item><item><title>The move from monolithic to composable architectures</title><link>https://timbenniks.dev/writing/the-move-from-monolithic-to-composable-architectures</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-move-from-monolithic-to-composable-architectures</guid><description>Success in business can be attributed to many factors, notably team talent and efficacy of products...</description><pubDate>Mon, 13 Mar 2023 20:42:55 GMT</pubDate><category>composable-architecture</category><category>frontend</category></item><item><title>MACH versus monolithic suites</title><link>https://timbenniks.dev/writing/mach-versus-monolithic-suites</link><guid isPermaLink="true">https://timbenniks.dev/writing/mach-versus-monolithic-suites</guid><description>Today, with consumers fast becoming digitally advanced, companies realize that old technologies are...</description><pubDate>Mon, 13 Mar 2023 20:37:36 GMT</pubDate><category>composable-architecture</category><category>frontend</category></item><item><title>The MACH monolith</title><link>https://timbenniks.dev/writing/the-mach-monolith</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-mach-monolith</guid><description>For years, the headless concept went through the nerd vine at boardrooms, pushing execs to take...</description><pubDate>Mon, 13 Mar 2023 20:20:45 GMT</pubDate><category>composable-architecture</category><category>frontend</category></item><item><title>The future of jamstack is composable</title><link>https://timbenniks.dev/writing/the-future-of-jamstack-is-composable</link><guid isPermaLink="true">https://timbenniks.dev/writing/the-future-of-jamstack-is-composable</guid><description>This post is either for developers who want an “at-scale” overview of modern architecture or for...</description><pubDate>Wed, 23 Feb 2022 13:04:08 GMT</pubDate><category>composable-architecture</category><category>content-ops</category></item><item><title>Create a performant YouTube embed with a native web component</title><link>https://timbenniks.dev/writing/create-a-performant-youtube-embed-with-a-native-web-component</link><guid isPermaLink="true">https://timbenniks.dev/writing/create-a-performant-youtube-embed-with-a-native-web-component</guid><description>In this Media Jam you will learn how to create a native web component that replaces the default YouTube iframe embed.</description><pubDate>Thu, 20 May 2021 13:05:48 GMT</pubDate><category>frontend</category><category>media-production</category></item><item><title>Creating a custom video player in Vue.js</title><link>https://timbenniks.dev/writing/creating-a-custom-video-player-in-vue</link><guid isPermaLink="true">https://timbenniks.dev/writing/creating-a-custom-video-player-in-vue</guid><description>In this Media Jam you will learn how to create a video player with custom controls and event handling in Vue.js.</description><pubDate>Tue, 18 May 2021 13:05:48 GMT</pubDate><category>frontend</category><category>media-production</category></item></channel></rss>