Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
will__ness
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
will__ness
8mo ago
Great questions. For me, high quality code is code that: 1) works (is functional, no bugs) 2) is secure (no security vulnerabilities) 3) is extendable (I can quickly and easily build new features with limited refactors) I argue the code sti
2.
▲
by
will__ness
8mo ago
Here is my exact workflow: https://willness.dev/blog/claude-code-workflow
3.
▲
by
will__ness
8mo ago
This is very true. My biggest frustration is people who use LLMs to generate code, and then don't use LLMs to refine that code. That is how you end up with slop.I would estimate that as a SDE I spend about 30% of my time reviewing and
4.
▲
by
will__ness
8mo ago
> it's orders of magnitude worse This is not my experience *at all*. Maybe models from like 18+ months ago would produce really bad code, but in general most coding agents are amazing at finding existing code and replicating the c
5.
▲
by
will__ness
8mo ago
> But there are serious limits. [Your coding agent] will lie to you, they don't really understand things, and they often generate bad code. I think that really high quality code can be created via coding agents. Not in one prompt, b
6.
▲
You Need to Clear Your Coding Agent's Context Window
(willness.dev)
3 points
by
will__ness
8mo ago
|
0 comments
7.
▲
by
will__ness
9mo ago
https://willness.dev
8.
▲
by
will__ness
9mo ago
Author here. I kept hitting the same tradeoff with Claude Code: 1) move fast, ship bugs, slow down feature development due to bad code 2) manually review all code and move super slow This post covers the workflow I landed on: 1) sub-agents