jwilliams

5 ms·

31.
by jwilliams 6mo ago
It’s terrific to see this. I’m definitely going to give it a whirl. I’ve been working on a specific JavaScript isolate[^1]. This is great source of inspiration for it. [^1]: https://github.com/jonathannen/hermit
32.
by jwilliams 6mo ago
GraalVM is genuinely great -- Native Image and the polyglot story are impressive. I was put off by the earlier licensing - it was confusing, which wasn't great in a license. The GraalVM Free Terms and Conditions "GFTC" now se
33.
by jwilliams 6mo ago
It's live! If you're on the latest cc you can use /buddy now.
34.
by jwilliams 6mo ago
I used to swear at Claude. To be honest, I thought it helped get results (maybe this is "oldschool" LLM thinking), but I realized it was just making me annoyed.
35.
by jwilliams 6mo ago
I don't disagree that organizations are probably making that tradeoff in an uninformed way. As a counterpoint -- it's rare I've seen a new UX issue fixed with a PR. If you valued quality you could feature-flag some different
36.
Early Observations from Interviews with Engineering Teams Adopting AI(jonathannen.com)
4 points by jwilliams 6mo ago|3 comments
37.
by jwilliams 6mo ago
Good to know. I’ve been using ghostty and generally not a fan of the code ligatures (or just too stubborn to adapt!).
38.
by jwilliams 6mo ago
Try this - For the same task, try the same prompt three times with totally different framing - do it fast, be comprehensive, find stuff I’ve missed, etc. Then throw away the ones you don’t like. It also prevents reinforcement of your incomi
39.
by jwilliams 6mo ago
For me the framing is critical - what is the model saying yes to? You can present the same prompt with very different interpretations (talk me into this versus talk me out of it). The problem is people enter with a single bias and the AI c
40.
by jwilliams 7mo ago
It's meant to, yes.
41.
by jwilliams 7mo ago
> Simply put: whatever you write in CLAUDE.md, Claude will follow. No. CLAUDE.md is just prompt text. Compaction rewrites prompt text. If it matters, enforce it in other ways.
42.
Battleship Prompts(jonathannen.com)
2 points by jwilliams 7mo ago|0 comments
43.
by jwilliams 7mo ago
There are niches where DC makes sense - low-voltage lighting, USB/LED ecosystems. Once you get into higher power (laptops and up), switching and distribution get harder, so the advantages fade. For bigger appliances (fridge, etc), AC i
44.
by jwilliams 7mo ago
It's the most transformative technology I've clocked in my lifetime (and that includes home computers and the Internet). Large organizations are making major decisions on the basis of it. Startups new and old will live and die by
45.
We're Not Vibe Engineering(jonathannen.com)
2 points by jwilliams 7mo ago|0 comments
46.
by jwilliams 7mo ago
It’s a blend. There are plenty of changes in a production system that don’t necessarily need human review. Adding a help link. Fixing a typo. Maybe upgrades with strong CI/CD or simple ui improvements or safe experiments. There are fea
47.
by jwilliams 7mo ago
Definitely made me feel old to see bit-shifting needed an explainer! I must admit as I was reading I was "why is he explaining this? it's obvious!".
48.
by jwilliams 7mo ago
Very true. I realized recently that I've subconsciously routed-around merge conflicts as much as possible. My process has just subtly altered to make them less likely. To the point of which seeing a 3-way merge feels jarring. It's
49.
by jwilliams 7mo ago
Indeed. And plenty of successful merges end up with code that won't compile. FWIW I've struggled to get AI tools to handle merge conflicts well ( especially rebase ) for the same underlying reason.
50.
by jwilliams 7mo ago
If it’s any comfort, I don’t hear many JS/TS/Node/etc developers calling them threads or really thinking of them that way. Usually just Workers or Web Workers — "worker threads" mostly slips in from Node. Even then,
51.
The Claude Dichotomy(jonathannen.com)
2 points by jwilliams 7mo ago|0 comments
52.
by jwilliams 7mo ago
Thanks! I'd assume that this will be a bit like JSON schemas - the decoding will eventually get smart enough to validate in the output in line with more complex rules. Agree on the "behind it's back" too. I might make a
53.
ESLint Tuned for Claude(github.com)
2 points by jwilliams 7mo ago|2 comments
54.
by jwilliams 7mo ago
If you know what you need, my experience is that a well-formed single-prompt that fits the context gives the best results (and fastest). If you’re exploring an idea or iterating, the roles can help break it down and understand your own requ
55.
Man's dog riddled with tumors. He used ChatGPT to design a cancer vaccine(finance.yahoo.com)
2 points by jwilliams 7mo ago|0 comments
56.
by jwilliams 7mo ago
I love Jevons’ paradox too, but if we apply it here don’t we still end up with more software? Definitely would entertain -- I do agree with your framing. I just think the article undersells the impact of fast+cheap codegen. Lowering the cos
57.
by jwilliams 7mo ago
> Humans and LLMs both share a fundamental limitation. Humans have a working memory, and LLMs have a context limit. But there’s a more important difference: I can’t spin up 20 decent human programmers from my terminal. The argument that
58.
by jwilliams 7mo ago
Atwood has been writing about speculative futures for a long time, so it’s interesting to watch her react in real-time to one of them actually happening. The post captures something real about LLMs: the interface makes the interaction feel
59.
Still Choose Boring Technology(jonathannen.com)
3 points by jwilliams 7mo ago|0 comments
60.
by jwilliams 7mo ago
I have moved towards super-specific scripts (so I guess "CLI"?) for a few reasons: 1. You can make the script very specific for the skill and permission appropriately. 2. You can have the output of the script make clear to the LLM

More ›