This is a blog post that I spent the last two months working on. I've run into a situation at work where there are several people who aggressively vibe-code all the things, and while I think that LLM usage is helpful in some cases, I don't believe that outsourcing your brain to it has any real usefulness. This post is about the techniques that I've adopted at work, and the history behind them, for proving beyond a shadow of a doubt that the documentation I write is by me and me alone.
If there's one thing I've learned about website design, blog publishing, documentation publishing, and commenting on things it's that the nanosecond I push to production I'll catch a glaring error that I should've caught in one of the 4-5 passes before I finalized and published. Every time. Without fail.
[OP] itsthejoker | 8 hours ago
This is a blog post that I spent the last two months working on. I've run into a situation at work where there are several people who aggressively vibe-code all the things, and while I think that LLM usage is helpful in some cases, I don't believe that outsourcing your brain to it has any real usefulness. This post is about the techniques that I've adopted at work, and the history behind them, for proving beyond a shadow of a doubt that the documentation I write is by me and me alone.
I'd love to know your thoughts!
secret_online | 8 hours ago
Your mobile-friendly link at the top links to example.com, not the mobile friendly version.
[OP] itsthejoker | 8 hours ago
I knew someone was going to point that out before I fixed it
The build that fixed it failed before I noticed, and it's re-running now. >_<
edit: it's fixed now!
Narry | 5 hours ago
If there's one thing I've learned about website design, blog publishing, documentation publishing, and commenting on things it's that the nanosecond I push to production I'll catch a glaring error that I should've caught in one of the 4-5 passes before I finalized and published. Every time. Without fail.
[OP] itsthejoker | 2 hours ago
Every single freakin' time.