James Clarke

Engineering at @polytomic. Previously at @getzaius. Past life: Natural Language Processing and Machine Learning.

[James Clarke @jacla]

@badlogicgames Please generate a input/output pricing comparison table for all models based on price pi-mono/README.md 😭

[James Clarke @jacla]

@badlogicgames Quick and simple: https://t.co/t2Bf61dDpn

[James Clarke @jacla]

@badlogicgames If you are using a commit-based workflow you may find value in having the review strip concept from Reviewable. I added to my own version of pi-diff-review. The tool remembers what commit has been reviewed and defaults to showing the new changes.

[James Clarke @jacla]

@bentlegen I had this exact concern. I am still yet to run the experiment.

[James Clarke @jacla]

@badlogicgames @nicopreme I still occasionally use Jane Street style review comments in code. See my old description at https://t.co/MHsS2JB85b

[James Clarke @jacla]

@simonw Sesame is good but only a preview of the technology so it is less useful for productive conversations unless you take notes.

[James Clarke @jacla]

@davidcrawshaw @badlogicgames @ssh_exe_dev I'd take one if you are still extending the invite!

[James Clarke @jacla]

@warpdotdev @GitHubCopilot @WisprFlow When are you adding first-class support for https://t.co/fShL8pqUNu?

[James Clarke @jacla]

@thomasmustier This looks awesome and very close to my existing workflow. I'm going to give this a try over the next week. Thanks for sharing!

[James Clarke @jacla]

@badlogicgames I was hoping this could be solved at the harness layer. Codex is really hates to pair program. I sometimes have more success by letting codex commit, make my own changes in a commit, then hand it back to codex.

[James Clarke @jacla]

@badlogicgames I have opinions. 1. Make the diffs editable (so you can add in-file review comments or fix things), 2. Mark files as reviewed (at that diff). IMO this is the best of Jane Street-style code review and Reviewable incremental review.

[James Clarke @jacla]

@steipete No one wants an anxious code generator.

[James Clarke @jacla]

@mitchellh Same! For over 15 years I've just read and listened to The Economist. If it's important, I’ll see it in the next edition.

[James Clarke @jacla]

Every time I edit a file, Codex gets confused and changes it back. Need to teach it to collaborate, not overwrite.

[James Clarke @jacla]

Great to see OpenAI demo how they use Codex internally. But at review time, it still feels a bit like Homer’s bird at the keyboard. Human-in-the-loop review matters, and I'm sure they do it. https://t.co/RpjQQcxxFL

[James Clarke @jacla]

@mitsuhiko I appreciate you posting the video. I struggled with a good review workflow.
Now I try to do almost everything in a single terminal split into three panes (agent | diff view | shell).
Wrote up my workflow https://t.co/MHsS2JBFUJ

[James Clarke @jacla]

@simonw Running multiple coding agents used to be too much cognitive load with window juggling and no flow.
Now: one Warp terminal (split into agent | diff | terminal panes), each git worktree in its own tab, plus one Cursor window to switch worktrees.

[James Clarke @jacla]

@CptKrrk @carsNbikelane I think both intersections (mystic and Everett) are particularly tricky. Left turns can be pretty fast 15-20mph so many times the car will not need to slow down to take the turn. Thus you cannot anticipate the left hook.

[James Clarke @jacla]

@joshm @arcinternet I use it but also enable it a lot by accident. The default keybinding clashes with forward-delete binding which I use a lot when writing in textfields. I guess I should change the shortcut. I need at least C-a, C-e, C-f, C-d, C-b when editing text.