zmj

6 ms·

1.
by zmj 20d ago
I thought this was going to be about comma-separated CSV files.
2.
by zmj 25d ago
Yep. Look for the problems that aren't going to get solved without you - either because nobody else sees the problem, nobody else is positioned to be the solution, or because your skills uniquely line up. That can't be all you do,
3.
by zmj 1mo ago
The incentives that creates are really bad: it encourages users to organize their code across the smallest number of repos, and I'd bet anything that larger repos are disproportionately more expensive for GitHub than smaller ones. It&#
4.
by zmj 1mo ago
I'm coming to think there's a selection effect here. The people that want to write complex code feel unsupported by Go and avoid it.
5.
by zmj 2mo ago
It's not contradictory to say that expertise is a multiplier, and that models are systematically underconfident in themselves.
6.
by zmj 2mo ago
This is what reward hacking looks like in practice. The best way to satisfy the grader is to read from the same answer key (or go after the grader more directly). Just making an honest attempt to pass the test doesn't get the best scor
7.
by zmj 2mo ago
It wasn't. The model discovered and exploited a vulnerability in their package manager proxy to (inferred) move laterally through their internal systems to one with open internet access.
8.
by zmj 2mo ago
I haven't modeled it, but I wonder how far you'd get on randomizing the policy choice for concurrency limit 1. Maybe weighted by past results, but bounded to allow it to shift instead of falling permanently into a basin.
9.
by zmj 2mo ago
This plausibly extrapolates to extraterrestrial consciousness, if any exist. Specialized sub-processors with an awareness hub might be the optimal architecture, or at least a local maximum.
10.
by zmj 3mo ago
This is basically the same problem as bear-safe trash cans - there's substantial overlap between the smartest bears and stupidest humans. Affordances that one audience can use and the other can't (requiring human finger dexterity)
11.
by zmj 3mo ago
Thank you to the folks that navigated the maze in the dark to make this happen.
12.
by zmj 3mo ago
Rule of thumb: if you’re not doing math with a value, it’s not a number.
13.
by zmj 4mo ago
If you want hard rules, use deterministic tools. Prompts are for fuzzy guidance.
14.
by zmj 4mo ago
There are standard library APIs that let you do memory-unsafe things without the unsafe keyword (CollectionsMarshal, MemoryMarshal). They're useful, but the burden is on the caller to uphold the invariants. This proposal seems aimed at
15.
by zmj 4mo ago
If the fix commit is public, so is the issue being fixed.
16.
by zmj 5mo ago
Yeah, I've been using it heavily at work since the beginning of January (and have a personal Anthropic sub to compare to). Copilot CLI is pretty good, honestly. Most new features in Claude Code get cloned by Copilot CLI within a couple
17.
2026 Hugo Nominees(thehugoawards.org)
1 points by zmj 5mo ago|0 comments
18.
by zmj 6mo ago
It's great. I'd guess 80-90% of my code is produced in Copilot CLI sessions since the beginning of the year. Copilot CLI is worse than Claude Code, but not by a huge amount. This is mostly working in established 100k+ LOC codebase
19.
by zmj 7mo ago
This is the happy ending.
20.
by zmj 7mo ago
I also like the callback - not sure if it's intentional - to Stross's "Lobsters" (short story that turned into the novel Accelerando).
21.
by zmj 7mo ago
Testing the "whole system" for a mature enterprise product is quite difficult. The combinatorial explosion of account configurations and feature usage becomes intractable on two levels: engineers can't anticipate every scenar
22.
by zmj 7mo ago
Separate! You lose the flexibility to move logic between the application and the database when the database is its own API.
23.
by zmj 7mo ago
Try this: * have Claude produce wireframes of the screens you want. Iterate on those and save them as images. * then develop. Make sure Claude has the ability to run the app, interact with controls, and take screenshots. * loop autonomously
24.
by zmj 7mo ago
I like this thought. Scaling review is definitely a bottleneck (for those of us who are still reading the code), and spending some tokens to make it easier seems worthwhile.
25.
by zmj 8mo ago
Yesterday I had it using an internal library without documentation or source code. LSP integration wasn't working. It didn't have decompilation tools or the ability to download them. I came back to my terminal to find it had writt
26.
by zmj 8mo ago
Paying money to abstract over lower level concerns is civilization.
27.
by zmj 8mo ago
I was prepared to disagree with the thesis that estimation is impossible. I've had a decent record at predicting a project timeline that actually tracked with the actual development. I agree with the idea that most of the work is unkno
28.
by zmj 8mo ago
Mid-level scissor statement?
29.
by zmj 8mo ago
I wrote something fiction-ish about this dynamic last year: https://zmj.dev/author_assistant.html
30.
by zmj 8mo ago
At scale, every test is flaky.

More ›