Adds stub for vibe-coding article
This commit is contained in:
23
src/content/blog/vibe-coding-debt.md
Normal file
23
src/content/blog/vibe-coding-debt.md
Normal file
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
title: "5 Types of AI Coding Tech Debt"
|
||||||
|
description: "AI coding assistants, or even vibe-coding agents, can create a lot of code very quickly and get features done fast. However, there are a few common ways in which vibe-coding projects tend to go off the rails and end up mired in tech-debt hell. The AI doesn't prevent you from accumulating tech-debt, in fact it allows you to create more of it more quickly. I go over a few common issues with AI code that causes it to lose it's luster on large or long projects."
|
||||||
|
---
|
||||||
|
|
||||||
|
1. Concepts
|
||||||
|
1. ROI
|
||||||
|
1. Refer to the Glyph's article.
|
||||||
|
1. Net-positive and net-negative programmers
|
||||||
|
1. Simplicity and Complexity
|
||||||
|
1. Transparency
|
||||||
|
1. Some of the ways AI fails
|
||||||
|
1. Testing
|
||||||
|
1. Debugging and logging
|
||||||
|
1. Libraries and common code
|
||||||
|
1. Performance
|
||||||
|
1. Abstract structure
|
||||||
|
1. How do we fix it?
|
||||||
|
1. Functional tests
|
||||||
|
2. Enforce good debugging practices
|
||||||
|
3. Build your own libraries
|
||||||
|
4. Build real-world performance tests
|
||||||
|
5. You gotta know how to design it
|
||||||
Reference in New Issue
Block a user