Techcle Wiki

Article Planning

8 min read

Synthesis Article: Phase A — Planning & Notes

Title: Sauna-Driven Development: Five Shifts in How Work Happens

Purpose: Synthesize articles 001-005 into a standalone piece for external publication (InfoQ, The New Stack, Dev.to, Hacker News)

Target: 2,000-2,500 words (longer than regular articles, self-contained)

Key Message: I can direct architecture work from a sauna. That shouldn’t be possible - but it is. Something fundamental has shifted about where work happens and what “being productive” means.

Publish Target: Mid-March 2026 (after Article 005 publishes Feb 16)

Summary (for submissions/social):

I’m sitting in an infrared sauna reviewing architecture decisions with AI agents. This shouldn’t be possible - software architecture has always required desks, keyboards, multiple monitors. Yet here I am, sweating through API design decisions, evaluating service boundaries, researching supplier capabilities. The agents work, I review and direct, and it’s genuinely productive.

Five assumptions that held for decades have quietly broken: the desktop as mandatory center, work requiring physical presence, synchronous interaction as essential, workstations as creation surfaces, and speed mattering more than continuity. Individually, each shift is noticeable. Together, they enable something absurd: productive architectural work from a sauna.

This isn’t about location flexibility or “work from anywhere.” It’s about what work fundamentally is when judgment separates from execution. The location doesn’t matter. The tools don’t matter. Even constant presence doesn’t matter. What matters is judgment, direction, and the ability to evaluate what agents produce - the work that genuinely requires human experience, not just human presence.

This article explores five shifts that compound, what they don’t mean, and what we do with a reality where architecture happens in more places, through more surfaces, with less direct human presence required than we ever thought possible.

InfoQ Submission Form Responses

Queue Selection: Architecture and Design

1. One paragraph abstract: [Use the Summary section above]

2. Brief outline (main sections): • Opening: The sauna scenario - directing architectural work from an infrared sauna reveals something fundamental has shifted • What This Proves: Five Shifts That Compound - The desktop stopped being the center, work continues without physical presence, architectural work is no longer synchronous, the workstation became an intervention surface, speed matters less than continuity • What This Doesn’t Mean - Boundaries and clarifications: not about location flexibility, not all work decouples this way, supervision is real work, creates more time for human presence, raises more questions than it answers • The Center Doesn’t Disappear - It Moves - The center is contextual, different work requires different contexts, the contradiction between absurdity and reality signals fundamental change

3. Proposed title: Sauna-Driven Development: Five Shifts in How Work Happens

4. Topic focus: How AI agents are changing the nature of architectural work - specifically the decoupling of judgment from execution and the shift from synchronous creation to asynchronous supervision and evaluation.

5. Target reader: Software architects, engineering leaders, and senior developers who are noticing how AI agents are changing where and how technical work happens, and want to understand what’s fundamentally shifting beneath surface-level productivity gains.

6. How is this different/unique? The article opens with a literal scenario: conducting architecture work from an infrared sauna using an iPad. This absurd-but-real moment reveals five shifts that most AI/development articles miss. Rather than focusing on AI capabilities or productivity gains, this examines the lived experience of work fundamentally changing: architectural judgment happens on the tube, supplier research completes while you’re in meetings, service boundary decisions get made between other commitments. Most articles ask “what can AI do?” This asks “what changes about human work when judgment separates from execution?” The sauna isn’t a metaphor - it’s proof that presence and progress have genuinely decoupled in ways that challenge decades of assumptions about where and how technical work happens.

7. Real-world project experience: It started with a photo I took of myself, in the sauna, doing architecture work. The rest of it chronicles my personal journey and changes to the way I work - from noticing I could review architecture decisions on mobile, to delegating research while commuting, to realizing work continues productively while I’m elsewhere. Six months of lived experience using AI agents (Claude, ChatGPT) for architectural research, supplier evaluation, and system design proposals. The “sauna scenario” isn’t a thought experiment - it’s the moment that made me realize something fundamental had shifted.

8. Technologies and tools: AI agents (Claude, ChatGPT), mobile devices (iPad, iPhone) for architectural review, collaboration platforms, version control systems. Focus is on how these tools enable new work patterns rather than technical implementation details.

9. Case studies/use cases:

  • Evaluating API gateway options while agents research in parallel
  • Documenting integration patterns asynchronously
  • Reviewing architectural decisions on mobile between meetings
  • Researching supplier capabilities while in meetings/commuting
  • The shift from desk-bound architecture to context-appropriate environments

10. Code examples: None. Article focuses on work patterns and architectural judgment rather than implementation.

11. Five key takeaways: [Use the Key Takeaways section below]

12. Timeframe for completed draft: Draft is complete and ready for review.

13. Brief biography: [Use the Author Bio section below]

14. Draft link (optional): [To be provided - Google Doc version of article.md]

InfoQ Submission Requirements

Key Takeaways (5 required - full sentences):

  1. The desktop stopped being the mandatory center of architectural work - work now happens across multiple surfaces (iPad, iPhone, desk) with the environment adapting to what specific work requires rather than forcing all work through a single interface.

  2. Work continues without physical presence as agents research, document, and analyze while you’re elsewhere, fundamentally decoupling progress from presence in ways that challenge decades of work structure assumptions.

  3. Architectural work shifted from synchronous to asynchronous - you set direction, agents work on their own timeline, and you evaluate results when ready rather than maintaining constant real-time oversight.

  4. The workstation transformed from a creation surface to an intervention surface where you review, correct, approve, and refine what agents produced rather than creating from scratch.

  5. Continuity matters more than speed when agents complete work in 20-30 minutes while you’re elsewhere - the value isn’t execution speed but that work finishes without requiring you to wait or context-switch to check progress.

Author Bio:

Craig Edmunds is a software architect who helps software teams deliver better outcomes through improved clarity and alignment to their context. With a keen interest in how AI agents are changing the future of work, he recently started writing about these shifts at thelongrun.work. He works from wherever the thinking happens - including, occasionally, a sauna.

Images:

Feature image: repos/thelongrun-publishing/docs/articles/002-work-continues-without-you/images/1-sauna-development.jpg

  • The actual photo referenced in real-world experience answer
  • Shows iPad-based architectural work in infrared sauna
  • Copyright: Craig (original photo)
  • Already used in article 002

Proofreading:

Article has been reviewed for clarity and flow. InfoQ will provide additional editorial review if accepted.

Distribution Strategy:

Phase 1 (Editorial platforms - target first):

  1. The New Stack - Email contributors@thenewstack.io
    • “Your take on a trend” angle fits our observational style
    • They explicitly welcome pieces like “Matt Welsh on the End of Programming”
    • 2-3 week review time

Phase 2 (7 days if no response): 2. Dev.to - Direct publish (no approval needed)

Phase 3 (After published anywhere): 3. Hacker News - Post link once live

Rejected:

  • InfoQ - Declined: “Does not map to our current editorial focus, format, and the needs of our audience. We primarily look to publish deep-dive content written by current practitioners in the innovator and early adopter technology stages.” Our observational essay style doesn’t fit their technical deep-dive requirements. Unlikely to be suitable for future synthesis articles either.

Phase A Articles to Synthesize

#TitleKey Insight
001Desktop as centreIDE still central, but not always most important
002Work continues without youProgress no longer tied to presence
003Development was synchronousIDE assumed tight loops; async breaks that
004IDE as intervention surfaceShifts from creation to correction/finalization
005Faster feedback not whole storySpeed matters less than continuity

Synthesis Goals

  • Standalone piece (doesn’t require reading 001-005)
  • Self-contained but points back to series
  • Appropriate for external publication audiences
  • Maintains observational tone (Phase A scope)

What to Avoid

  • Just summarizing each article sequentially
  • Jumping into solutions/prescriptions (Phase B/C scope)
  • Being too series-specific (needs broader appeal)

Target Publications

  • LeadDev: Management/leadership angle - how this changes team dynamics
  • InfoQ: Enterprise angle - what this means for organizations
  • The New Stack: Platform/tooling angle - infrastructure implications

Consider tailoring slightly for each publication, or write one version that works for all.

Development Plan

  1. Define core synthesis message
  2. Extract key insights from articles 001-005
  3. Identify common threads and patterns
  4. Draft opening hook
  5. Structure narrative arc
  6. Write full draft
  7. Review against Phase A scope
  8. Tailor for target publications
  9. Prepare pitch text

submission info: https://docs.google.com/forms/d/e/1FAIpQLSfcvJcY5XNvIseAAOVhLn-HoxRxoZSzIWUAZmXcFCaLBPY_AA/viewform

Graph View