Skip to content

Commit 2202845

Browse files
committed
docs: add new entries and updates to AI coding history and concepts
- Introduced new journal entry for "Agentic AI Coding" with updates on related topics. - Added detailed pages for phases 5 of AI coding, including "Context Engineering" and its sub-phases. - Created new entries for "Vibe Coding" and clarified its distinction from traditional coding practices. - Updated references and embedded links for better navigation and context within the AI coding documentation.
1 parent 371560f commit 2202845

21 files changed

+104
-18
lines changed

journals/2025_10_19.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
- [[Agentic AI Coding]]
2+
- #Updated
3+
- [[AI/Coding/History]] and subpages
4+
- #Filed
5+
- [[Person/Simon Willison/Blog/25/10/Claude Skills]]
6+
- [[LobsteRS]]
7+
- [[Person/Peter Steinberger/Blog/25/10/Just Talk to It - no-bs Agentic Engineering]]
8+
- [[Person/Peter Steinberger/GitHub/Gist/Agent.md]]

pages/AI___Coding___Agentic.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,5 @@ alias:: [[Agentic AI Coding]]
22
tags:: [[Term]]
33

44
- # Agentic AI Coding
5-
- AI coding has evolved in phases
6-
- Phase 1 -
7-
- Phase 2 - using [[ChatGPT]] with [[Copy/and Paste]] - a step beyond,
8-
- Phase 3 - single-file editing in [[IDE]]
9-
- Phase 4 - multi-file editing in [[IDE]]
10-
- Phase 5 - [[Vibe Coding]] becomes possible with agentic multi-file editing both in [[IDE]] and with tools like [[BoltAI]] and [[LoveableAI]]
11-
- Phase 6 - bringing remote context into coding agents with [[MCP]]
12-
- Phase 7 - dynamic context engineering with [[Claude Code Skills]]
5+
- An LLM running in a loop with tools to create code.
6+
- See [[AI/Coding/History/Phase/4 - Basic Autonomous Coding]] and subsequent phases like [[AI/Coding/History/Phase/5 - Context Engineering]]

pages/AI___Coding___History.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,4 @@
33
-
44
- {{embed [[AI/Coding/History/Phase/3 - Direct Agentic Coding]]}}
55
- {{embed [[AI/Coding/History/Phase/4 - Basic Autonomous Coding]]}}
6-
- [[AI/Coding/History/Phase/5 - Context Engineering/MCP Servers]]
7-
- [[AI/Coding/History/Phase/5 - Context Engineering/Skill Bundles]]
6+
- {{embed [[AI/Coding/History/Phase/5 - Context Engineering]]}}
Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
- Ushered in by [[Claude Code]], in phase four, a developer could give an [[LLM]] an instruction, and an [[Agentic System]] would iterate on it for some time, sometimes 3-5 minutes, other times 5-10 minutes.
2-
- [[Person/Andrej Karpathy]] coined the term [[Vibe Coding]]
2+
- {{embed [[AI/Coding/Vibe/25/02/Karpathy Coins Term]]}}
3+
- {{embed [[AI/Coding/Vibe/25/03/Willison Clarifies as Not Reviewing Code]]}}
34
- Sub-Phases
45
- {{embed [[AI/Coding/History/Phase/4 - Basic Autonomous Coding/Web-based Vibe Coding]]}}
56
- {{embed [[AI/Coding/History/Phase/4 - Basic Autonomous Coding/CLI-based]]}}
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
- After agentic coding became the dominant paradigm, it took a while for engineers to understand how to let the agentic coding tools take actions in outside of the local filesystem, such as checking CI logs, reading JIRA or GitHub tickets, or opening PRs. After the introduction of [[MCP]] made this possible, there was a period of time where developers struggled to understand how agentic tools quickly filled up the [[AI/Context/Window]] and led to [[Context Rot]]. The term [[Context Engineering]] emerged as a way to signal the importance for minimizing the context needed to solve the problem at hand while still providing access to powerful tools.
2+
- Sub-Phases
3+
- {{embed [[AI/Coding/History/Phase/5 - Context Engineering/MCP Servers]]}}
4+
- {{embed [[AI/Coding/History/Phase/5 - Context Engineering/Skill Bundles]]}}
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
- After March 2025, many [[IDE]]s such as [[CursorAI]] and some [[CLI]]s such as [[Claude Code]] implemented an [[MCP/Client]] into the agentic coding chat interface, so developers could give AI [[MCP Servers]] to which enabled them to ask the AI to both sense and act on external context, for example
2+
- [[GitHub/MCP]] included the ability open and update [[PR]]s, to read [[CICD]] logs and [[GitHub/Issue]]s
3+
- [[Atlassian/MCP]] included the ability to edit and read [[Confluence]], [[JIRA]]
4+
- [[Playwright/MCP]] included the ability to check out a web application's display looked like in the browser, giving it the ability to "see"
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
- [[Person/Simon Willison/Blog/25/10/Claude Skills]]

pages/AI___Coding___Vibe.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,9 @@ tags:: [[Term]]
33

44
- # Vibe Coding
55
- ## #History of Vibe Coding as a Term and an Idea
6-
- On [[2025-10-02 Thu]], [[Person/Andrej Karpathy]] coined the term "Vibe Coding" in a [tweet](https://x.com/karpathy/status/1886192184808149383).
7-
- > There’s a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and **forget that the code even exists**. It’s possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard.
8-
- > I ask for the dumbest things like “decrease the padding on the sidebar by half” because I’m too lazy to find it. I “Accept All” always, I don’t read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I’d have to really read through it for a while. Sometimes the LLMs can’t fix a bug so I just work around it or ask for random changes until it goes away.
9-
- > **It’s not too bad for throwaway weekend projects, but still quite amusing**. I’m building a project or webapp, but it’s not really coding—I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
6+
- {{embed [[AI/Coding/Vibe/25/02/Karpathy Coins Term]]}}
107
- On [[2025-02-25 Tue]], I had my first real feeling of this [[CursorAI]], downstream from [[Person/Harper Reed/Blog/25/02/My LLM codegen workflow atm]].
11-
- On [[2025-03-19 Wed]], [[Person/Simon Willison/Blog/25/03/Not all AI-assisted programming is vibe coding]], clarified
12-
- > When I talk about vibe coding I mean **building software with an LLM without reviewing the code it writes**
8+
- {{embed [[AI/Coding/Vibe/25/03/Willison Clarifies as Not Reviewing Code]]}}
139
- On [[2025-10-08 Wed]], [[Person/Simon Willison/Blog/25/10/Vibe Engineering]] suggested that [[Vibe Coding]] is the opposite of a new term [[Vibe Engineering]]:
1410
- > the other end of the spectrum from [[Vibe Coding]], where **seasoned professionals accelerate their work with LLMs while staying proudly and confidently accountable for the software they produce**
1511
- Related Concepts:
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
- On [[2025-10-02 Thu]], [[Person/Andrej Karpathy]] coined the term "Vibe Coding" in a [tweet](https://x.com/karpathy/status/1886192184808149383).
2+
- > There’s a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and **forget that the code even exists**. It’s possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard.
3+
- > I ask for the dumbest things like “decrease the padding on the sidebar by half” because I’m too lazy to find it. I “Accept All” always, I don’t read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I’d have to really read through it for a while. Sometimes the LLMs can’t fix a bug so I just work around it or ask for random changes until it goes away.
4+
- > **It’s not too bad for throwaway weekend projects, but still quite amusing**. I’m building a project or webapp, but it’s not really coding—I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
- On [[2025-03-19 Wed]], [[Person/Simon Willison/Blog/25/03/Not all AI-assisted programming is vibe coding]], clarified
2+
- > When I talk about vibe coding I mean **building software with an LLM without reviewing the code it writes**

0 commit comments

Comments
 (0)