---
id: post/waldo-be/318627
type: post
title: “the waldo way”
summary: A CTO reflects on building a pre-packaged agentic development harness for the team to accelerate adoption, but questions whether removing setup friction also eliminates valuable learning opportunities. The post explores the tradeoff between speed-and-consistency versus developer ownership and skill-building.
tier: community
language: en
tags:
  - agentic development
  - team adoption
  - developer skills
  - setup friction
  - learning curve
  - vscode extension
  - company guidelines
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:54:45.108Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: f0420fe4655425f341c0a225c9c510d648667dbaa3cdb5c5cf23af4d97e8d669
evidence:
  - kind: blog
    url: https://waldo.be/2026/06/29/the-waldo-way/
    title: “the waldo way”
    date: "2026-06-29"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://waldo.be/2026/06/29/the-waldo-way/
    title: “the waldo way”
    date: "2026-06-29"
    commit: null
    t: null
    quote: By taking away all the friction .. did we also take away the learning?
  - kind: blog
    url: https://waldo.be/2026/06/29/the-waldo-way/
    title: “the waldo way”
    date: "2026-06-29"
    commit: null
    t: null
    quote: We traded depth-of-ownership for speed-and-consistency.
  - kind: blog
    url: https://waldo.be/2026/06/29/the-waldo-way/
    title: “the waldo way”
    date: "2026-06-29"
    commit: null
    t: null
    quote: You can't evolve a harness you've never even touched, right?
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "318627"
source_id: waldo-be
source_name: waldo's blog
url: https://waldo.be/2026/06/29/the-waldo-way/
published_at: "2026-06-29T21:51:44.000Z"
author: waldo (Eric Wauters)
full_text: true
words: 975
quotes:
  - text: By taking away all the friction .. did we also take away the learning?
    why_it_matters: Captures the core dilemma of whether removing setup complexity eliminates the educational value that comes from struggling through technical challenges
  - text: We traded depth-of-ownership for speed-and-consistency.
    why_it_matters: Summarizes the fundamental tradeoff between immediate team uniformity and developers' long-term ability to independently evolve solutions
  - text: You can't evolve a harness you've never even touched, right?
    why_it_matters: Presents the counter-argument that providing a working foundation first allows developers to improve it later, suggesting a phased approach to skill development
code_objects_mentioned: []
systems:
  - development
  - copilot
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://waldo.be/2026/06/29/the-waldo-way/embed/
  image: https://waldo.be/wp-content/uploads/2026/06/image.png
  image_alt: null
  image_w: 629
  image_h: 657
  site_name: null
  favicon: https://waldo.be/wp-content/uploads/2019/06/waldo_logo_final_symbol_icon_Revised-150x150.ico
  probed_at: "2026-10-07T11:50:15.533Z"
---

# “the waldo way”

[Read the post](https://waldo.be/2026/06/29/the-waldo-way/) · waldo's blog (waldo (Eric Wauters), MVP) · 2026-06-29 · 975 words · tier community · reviewed (checked by Opus)

> A CTO reflects on building a pre-packaged agentic development harness for the team to accelerate adoption, but questions whether removing setup friction also eliminates valuable learning opportunities. The post explores the tradeoff between speed-and-consistency versus developer ownership and skill-building.

## Key points

- A ready-made VSCode extension with agents, guidelines, and MCPs was created to lower adoption barriers and ensure uniform practices across the team
- Removing friction from setup may simultaneously remove the learning that happens when developers struggle through configuration and problem-solving
- The approach achieved fast, consistent adoption with no complaints, but potentially at the cost of developers learning to build and evolve their own solutions
- Other CTOs typically favor organic adoption by providing tools and direction, while this approach enforces uniformity upfront
- The core tension is whether to prioritize immediate capability (head start) or long-term ownership (deep learning)

## Quotes

- "By taking away all the friction .. did we also take away the learning?" (Captures the core dilemma of whether removing setup complexity eliminates the educational value that comes from struggling through technical challenges)
- "We traded depth-of-ownership for speed-and-consistency." (Summarizes the fundamental tradeoff between immediate team uniformity and developers' long-term ability to independently evolve solutions)
- "You can't evolve a harness you've never even touched, right?" (Presents the counter-argument that providing a working foundation first allows developers to improve it later, suggesting a phased approach to skill development)

## Context

- Features: VSCode extension, agents, MCP integration, company guidelines automation, wizard setup, playbook

Source: waldo's blog, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.