Code-Quality on vnykmshr

Garbage context in, garbage code out

Sat, 07 Mar 2026 00:00:00 +0000

LLMs are exactly as good as what you feed them.

Experienced engineers feel like the gap between them and everyone else just got smaller. Someone with six months of prompting can ship something that looks like what took years to learn how to build. That’s the wrong read.

The output looks the same if you don’t look closely. The architecture doesn’t. The failure modes don’t. When traffic spikes and that generated code hits a path nobody thought about, the years show up.

Node.js style guide

Wed, 20 Feb 2013 00:00:00 +0000

We’re a Node.js team of about 25 developers, most of them fresh out of college. Node was new to everyone. This is the style guide we put together to keep the codebase consistent.

Based on Felix’s Node.js Style Guide with our own picks where his guide left things open. Read Felix’s first – this extends it.

Formatting

2 spaces. No tabs. No discussion.

Trailing whitespace: strip it. Your editor should handle this. If it doesn’t, fix your editor.

History as communication

Mon, 18 Feb 2013 00:00:00 +0000

Most teams treat git history as a side effect. You work, you commit, whatever ends up in the log is the log. Merge commits pile up. “WIP” and “fix typo” and “actually working now” sit next to meaningful changes. The history is technically accurate but communicates nothing.

The alternative: treat history as something you write, not something that happens to you. The commit log is the one piece of documentation that’s always in sync with the code – because it is the code’s changelog. If the history is incoherent, you’ve wasted that.