Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phamilton
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
phamilton
8mo ago
It's using about 100M input tokens a day on glm 4.7 (glm 5 isn't available on my plan). It's sticking pretty close to the throttling limits that reset every 5 hours. 100M input tokens is $40 and anywhere from 2-6 kWh. Certain
32.
▲
by
phamilton
8mo ago
As an experiment, I set it up with a z.ai $3/month subscription and told it to do a tedious technical task. I said to stay busy and that I expect no more than 30 minutes of inactivity, ever. The task is to decompile Wave Race 64 and in
33.
▲
by
phamilton
8mo ago
Intelligence per token doesn't seem quite right to me. Intelligence per <consumable> feels closer. Per dollar, or per second, or per watt.
34.
▲
by
phamilton
8mo ago
Maybe I expressed that clumsily. With historical development, investing in hypotheticals can be wasteful. Make the fewest assumptions until you get real user feedback. With AI, we make more decisions upfront. Being wrong about those decisio
35.
▲
by
phamilton
8mo ago
Not as much upfront. I had plenty of opportunities to adjust and correct along the way. With AI, the cost of not thinking upfront is high and the cost of being wrong in upfront decisions is low, so we bias towards that. But beyond that, I h
36.
▲
by
phamilton
8mo ago
I think harder because of AI. I have to think more rigorously. I have to find ways to tie up loose ends, to verify the result efficiently, to create efficient feedback loops and define categorical success criteria. I've thought harder
37.
▲
by
phamilton
9mo ago
It all comes back to "Do more because of AI" rather than "Do less because of AI". Getting back into coding is doing more. Updating an old project to the latest libraries is doing more. It often feels ambiguous. Shipping
38.
▲
by
phamilton
10mo ago
I tried to ask Gemini about the blog content and it was unable to access the site. It was blocked and unable to discover the API in the first place.
39.
▲
by
phamilton
10mo ago
The inf1/inf2 spot instances are so unpopular that they cost less than the equivalent cpu instances. Exact same (or better) hardware but 10-20% cheaper. We're not quite seeing that on the trn1 instances yet, so someone is using th
40.
▲
by
phamilton
1y ago
It successfully got through the captcha at https://www.google.com/recaptcha/api2/demo
41.
▲
by
phamilton
1y ago
Just tried it in an existing coding agent and it rejected the requests because computer tools weren't defined.
42.
▲
by
phamilton
1y ago
Does that just do Database Level Conflict Checking?
43.
▲
by
phamilton
1y ago
I'm sad this project fizzled: https://github.com/losfair/mvsqlite It had the fascinating property of being a full multi-writer SQL engine when using Page Level Conflict Checking. Even more fascinating: every singl
44.
▲
by
phamilton
1y ago
That's a different problem. To quickly sort a nearly sorted list, we can use insertion sort. However the goal is to make progress with as little as one iteration. One iteration of insertion sort will place one additional element in its
45.
▲
by
phamilton
1y ago
This feels similar to when I heard they use bubble sort in game development. Bubble sort seems pretty terrible, until you realize that it's interruptible. The set is always a little more sorted than before. So if you have realtime requ
46.
▲
by
phamilton
1y ago
I think we should focus less on API schemas and more on just copying how browsers work. Some examples: It should be far more common for http clients to have well supported and heavily used Cookie jar implementations. We should lean on Accep
47.
▲
by
phamilton
1y ago
(not trolling) Would that undefined behavior have occurred in idiomatic rust? Will the ability to use AI to write such a solution correctly be enough motivation to push C++ shops to adopt rust? (Or perhaps a new language that caters to the
48.
▲
by
phamilton
1y ago
My LLM workflow involves a back-and-forth clarification (verbose input -> LLM asks questions) that results in a rich context representing my intent. Generating comments/docs from this feels lossy. What if we could persist this final
49.
▲
by
phamilton
1y ago
If we can detach content and presentation, then the reader can choose tone and length. At some point we will stop making decisions about what future readers want. We will just capture the concrete inputs and the reader's LLM will expla
50.
▲
by
phamilton
1y ago
Jokes aside, this happens all the time. I have it write doc strings. I later ask it to explain a section of code, wherein it uses the doc strings to understand and explain the code to me. A less lossy way to capture this will probably emerg
51.
▲
by
phamilton
1y ago
I can run the Qwen 3 0.6B model directly on my 3-year-old phone, and it can rewrite text and help me clearly explain my views. Even with new models possibly being less open and subsidized options drying up, we still have useful open models
52.
▲
by
phamilton
1y ago
We used to have a "2 approvals" policy on PRs. It wasn't fully enforced, it was a plugin to Gitlab we built that would look for two "+1" comments to unhide the merge button. I used to create PRs and then review my o
53.
▲
by
phamilton
1y ago
Other feedback: allow permalinks for a given day's prompt. I expect to keep a collection of clever techniques and share with my team.
54.
▲
by
phamilton
1y ago
I would put attempt history above the leaderboard. Having to scroll past it to see the results of my submission makes it hard to not peek.
55.
▲
by
phamilton
1y ago
A nice addition to this I've seen twice now is a slack channel (via their personal emails) with continuing employees willing to help them practice interviewing and share their professional networks to help them find their next role.
56.
▲
by
phamilton
1y ago
I suspect this will indeed be part of it, but it won't work with today's AIs on today's codebases. Models will improve, but also I predict code style and architecture will evolve towards something easier for machine review.
57.
▲
by
phamilton
1y ago
Agents could generate more PRs in a weekend than my team could code review in a month. Initially we can absolutely just review them like any other PR, but at some point code review will be the bottleneck.
58.
▲
by
phamilton
1y ago
Sincere question: Has anyone figured out how we're going to code review the output of an agent fleet?
59.
▲
by
phamilton
2y ago
`'unbounded` isn't a bad idea. With my team when someone new to Rust hits the static type constraint I usually tell them an overly simplified "is not a reference" followed up with "The data does not have any constra
60.
▲
by
phamilton
2y ago
A coworker once told me: "Undefined behavior means the code could theoretically order a pizza" Hyperbole sure, but made me chuckle and is a nice reminder to check all assumptions.
More ›