Skip to content

Commit 3e2de0b

Browse files
evilruevilru
committed
feat: Add new pages for 'What's left when development is autonomous' and 'The terminal never left'
1 parent b9941ae commit 3e2de0b

File tree

3 files changed

+137
-0
lines changed

3 files changed

+137
-0
lines changed

‎thinking/ai-native-sdlc.md‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
---
2+
layout: page
3+
title: What's left when development is autonomous.
4+
---
5+
6+
<section class="nc-hero">
7+
<p class="section-label">thinking / 2026-03-19</p>
8+
<h1>What's left when development is autonomous.</h1>
9+
</section>
10+
11+
<section class="nc-section nc-section-border-top">
12+
<p>Assume the agent handles implementation. Another agent handles operations — Terraform, Kubernetes, configuration, deployment. Both are nearly there today. In 1–2 years, close enough.</p>
13+
14+
<p>What's the loop that remains?</p>
15+
16+
<div class="nc-quote">
17+
<p>Data → Hypothesis → A/B Test → Requirement → Data → ...</p>
18+
</div>
19+
20+
<p>That's it. That's the residual human loop — not because it can't be automated, but because it's the loop where organizational intelligence lives. Where business context meets system signal. Where intent is formed.</p>
21+
</section>
22+
23+
<section class="nc-section nc-section-border-top">
24+
<p class="section-index">The data that drives it</p>
25+
<h2>Requirements are data too.</h2>
26+
27+
<p>Most agentic SDLC thinking focuses on the execution layer: faster code, automated deploys. That's the easy part. The harder insight is that the entire input surface is data:</p>
28+
29+
<div class="nc-compare">
30+
<div class="nc-compare-card">
31+
<p class="label">Infrastructure signals</p>
32+
<p>Terraform state, K8s events, resource metrics, config drift</p>
33+
</div>
34+
<div class="nc-compare-card">
35+
<p class="label">Application signals</p>
36+
<p>Traces, error rates, latency, A/B results, conversion</p>
37+
</div>
38+
<div class="nc-compare-card">
39+
<p class="label">Business signals</p>
40+
<p>KPIs, user behavior, feature requests, support patterns</p>
41+
</div>
42+
<div class="nc-compare-card">
43+
<p class="label">Requirement signals</p>
44+
<p>User feedback, issues, stated needs — <strong>structurally identical to the others</strong></p>
45+
</div>
46+
</div>
47+
48+
<p>When requirements are treated as data, the loop closes. The system can generate hypotheses, run experiments, implement winners, measure outcomes — and feed results back as new signal. At every layer simultaneously.</p>
49+
</section>
50+
51+
<section class="nc-section nc-section-border-top">
52+
<p class="section-index">The wrong question</p>
53+
<h2>Why is everyone building a human process in an agent?</h2>
54+
55+
<p>Current agentic SDLC approaches copy the shape of how humans work: ticket → branch → PR → review → deploy. The same steps, faster. That's not a new process. That's an old process with a faster executor.</p>
56+
57+
<p>The right question isn't "how do we automate what developers do?" It's "what does a process look like that was designed for an agent from the start?"</p>
58+
59+
<p>An agent doesn't need a ticket system. It needs a signal. It doesn't need a sprint. It needs a priority function. It doesn't need a PR. It needs a verification gate.</p>
60+
61+
<div class="nc-quote">
62+
<p>"Fix your fucking processes. Then automate them."</p>
63+
</div>
64+
65+
<p>The sequence matters. AI on top of broken processes doesn't produce better software faster. It produces broken software faster.</p>
66+
</section>
67+
68+
<section class="nc-section nc-section-border-top">
69+
<p class="section-index">Where this is going</p>
70+
<h2>This is a working concept, not a finished argument.</h2>
71+
<p>Some of this I'm exploring with others. What the data loop actually looks like in practice. Where humans stay in the loop not because they have to, but because they add something irreplaceable. What the MCP layer means for frontend — and whether what we call "the web" is about to change shape again.</p>
72+
<p>More as it becomes clearer.</p>
73+
</section>

‎thinking/index.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
layout: home
3+
4+
hero:
5+
name: "//thinking"
6+
text: "Ideas in progress."
7+
tagline: Not finished thoughts. Not polished essays. Things worth writing down before they disappear.
8+
---
9+
10+
## Recent
11+
12+
### [The terminal never left.](/thinking/terminal-cycle)
13+
We spent 40 years building abstractions on top of the command line. The agents run in terminals again. The cycle completed itself.
14+
15+
### [What's left when development is autonomous.](/thinking/ai-native-sdlc)
16+
If an agent handles implementation and another handles operations — what's the loop that remains? And who owns it?

‎thinking/terminal-cycle.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
layout: page
3+
title: The terminal never left.
4+
---
5+
6+
<section class="nc-hero">
7+
<p class="section-label">thinking / 2026-03-19</p>
8+
<h1>The terminal never left.</h1>
9+
</section>
10+
11+
<section class="nc-section nc-section-border-top">
12+
<p>We spent 40 years building abstractions on top of the command line.</p>
13+
14+
<div class="nc-steps">
15+
<div class="nc-step">
16+
<h3>1969 — /usr/bin</h3>
17+
<p>The terminal. Direct contact with the machine. Text in, text out. Everything visible, nothing hidden.</p>
18+
</div>
19+
<div class="nc-step">
20+
<h3>1984 — Desktop</h3>
21+
<p>The GUI. The terminal hidden behind icons. Easier to start. Harder to compose. The interface became the product.</p>
22+
</div>
23+
<div class="nc-step">
24+
<h3>1995 — Browser</h3>
25+
<p>The GUI distributed. Everything becomes a page. The desktop abstracted away. Location replaces command.</p>
26+
</div>
27+
<div class="nc-step">
28+
<h3>2007 — Mobile</h3>
29+
<p>The browser replaced by the app. Tap instead of click. The URL disappears. Direct access to single functions.</p>
30+
</div>
31+
<div class="nc-step">
32+
<h3>2025 — /usr/bin</h3>
33+
<p>The coding agent runs in the terminal. Data lives in text files. TUI is cool again. The abstractions collapsed back to the substrate.</p>
34+
</div>
35+
</div>
36+
37+
<p>Each layer hid the complexity of the one before — until the layer itself became the complexity. When the interface becomes the bottleneck, the system finds a way around it.</p>
38+
39+
<p>AI didn't replace the terminal. It revealed that the terminal was always the honest layer.</p>
40+
41+
<div class="nc-quote">
42+
<p>"The simplest form isn't primitive. It's what remains when everything unnecessary has been removed."</p>
43+
</div>
44+
45+
<p>This is also why <a href="/behaviour.priming/">Behaviour Priming</a> works the way it does. No abstraction over intent. Direct contact with the semantic substrate. The same principle, one level deeper.</p>
46+
47+
<p>And it's why desktop agents that click through GUIs because there's no API are not progress. They're a workaround for systems that should have been designed better. <a href="/thinking/ai-native-sdlc">Fix the processes.</a></p>
48+
</section>

0 commit comments

Comments
 (0)