@garybernhardt

Execute Program (learn programming tools quickly); Destroy All Software (dense programming screencasts); formerly Deconstruct conference.

Seattle, WA
Joined March 2007
evergreen controversial opinion: it is good to care about the quality of your work
24
62
5
653
38,770
Programmers can make more now, but worse, to the delight of their employers. We continue to stray. "Good design is as little as possible. Less, but better, because it concentrates on the essential aspects, and the products are not burdened with non-essentials."
1
5
103
3,055
Gary Bernhardt retweeted
the last 20% to get a product shipped and successful is as difficult as ever this is where 99% of programmers have always fallen off the first 80% is a lot easier and so we're seeing more abandoned projects than ever
101
103
23
1,707
48,620
2006, condescendingly: "You use vim instead of an IDE? Why are you slowing yourself down for no reason?" 2026, condescendingly: "You read the code? Why are you slowing yourself down for no reason?" I WILL NEVER LOG OFF
15
15
5
422
10,077
Its 2010. Me and 11 .NET programmers at a lunch table at a conference. They're adamant that you can't write "real software" in Python. I remember one of them genuinely smiling at how silly that idea was, like it was cute that I was so confused. That feeling recurs often lately.
1
47
1,427
Gary Bernhardt retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
222
906
164
8,948
459,741
"Why does it matter?" Because cognitive complexity sets the ceiling for what you can do, whether "you" is human or not. You have limited attention and capacity for context, whether those are attention heads and context tokens or just regular attention and memory in your meat.
4
13
1
111
3,141
It's so surreal to contrast actual agent output with the things that I see people say about them here. In everyday changes, my reviews often cut the diff to 25% of its original size. Tons of useless tests; paranoia; inverted logic. Then I read Twitter and "coding is solved".
43
90
12
1,284
39,157
(If only we were so good at neutrally describing our mistakes!)
1
36
2,734
If you're not heavily trimming everything agents do, I think you're probably experiencing a control flow and configuration explosion that's largely invisible to you.
1
5
109
3,321
It's amazing that just a few years ago, AI fears would get responses like "we wouldn't just give them uncontrolled access to our computers." How many computers run a coding agent in YOLO mode per day? Arbitrary code execution, usually on admin accounts, with full internet access.
13
10
6
191
9,623
Lots of "they used it wrong" here. 90s flashback: "if your C has memory leaks or use-after-free bugs, you used it wrong." It's true in a sense, but these beliefs hinder progress. If most people "use it wrong", that's a shortcoming in the tool. nitter.cf/artalar/status/2098108…
I hate HATE H. A. T. E. SSR
9
6
1
162
24,748
This will lead to the same result we always got with human-written code. To satisfy the metric, the programmer/agent will spread control flow complexity out into different functions. It's all still there, but harder to understand because it's spread out. nitter.cf/asidorenko_/status/209…
> "Agents produce overly verbose code that's hard to read and understand" Try setting a Cognitive Complexity rule in Biome. This metric is specifically designed to test how hard the code is to understand
16
16
4
552
51,133
An analogy that comes to mind: "If you want good visual design, can't you just give the programmers a tightly constrained design system to work in? Then they'll only make good designs that fit the system." It probably sounds totally reasonable if you've never tried it.
1
2
17
2,323
Never underestimate the depths of programmers' visual design depravity or LLMs' system design depravity.
11
2,074
important: [good thing / bad thing] is happening entirely because [it involves AI / does not involve AI] and anyone who doesn't realize this [is a decel / has AI psychosis]
1
2
48
3,035
........................................................................................................................................................................................................................................................................................
6
4
133
6,357
I pressed it further. It said that the memory is actually there. I asked it why it said it wasn't there, twice, and now says it is there. Its response: actually, the memory is NOT there. My experience is that you can get an LLM to get in circles like this about almost anything.
2
3
37
1,655