exclipy

> Insert a battery and press Read battery

Where do you insert the battery?

OK, I have implemented this; expect to see it as version 1.0 tomorrow when it gets approved.

You'll be able to use the vertical scroll wheel to scroll horizontally.

Good feedback, thanks! I'll see if I can fix that today.

For now, you can press the left and right arrow keys or shift-left and shift-right to jump by column.

This.

The ampersand method in the OP video (and the sibling slipped-lapp-knot comment) is needlessly complicated. Just follow this super simple animation instead (except pass a bight in the last step to make it quick-release).

The Lapp knot (aka. lapp bend) is my favourite of all the knots and very underrated. It's so versatile and simple, even simpler to tie than a square knot. As shown in the OP, it can be tightened and loosened and explodes when you pull the tag rather than leaving the half-knot behind. It is my default way to tie two ropes together.

And the instant start cloud dev servers complete with shareable full stack preview links! Chefs kiss

Oh yeah, not to mention the drag and drop GUI mercurial client in the IDE. I still haven’t seen anything as good on the outside.

Regular engineers could use stacked diffs proficiently and regularly, without it being seen as a super advanced 10x engineer power user thing.

I jumped from Google to Facebook on 2019 and while I had thought Google had best in industry developer tooling, Facebook had it better.

Google’s dinky browser based Cider was cute but Facebook in its transition from Atom to VS Code was far ahead. Google might have invented asynchronous web based code review with Mondrian and Critique, but Facebook’s Diff was better with its stacked diff support. Google’s Buganizer was outdated and clunky compared to Facebook’s Tasks.

I left Facebook the year after but I do wonder where Meta’s tooling is up to nowadays. Is it still a glimpse of the future?

The specs are inscrutable agent slop. I want it to tell me what it does and instead it just lists database fields. It mentions a state machine and then proceeds to not describe the state machine.

If I wasn’t so attuned to agent slop, I’d be thinking I’m just too dumb to get it but no, whatever GPT model wrote this is not good enough (and the fact this was published by OpenAI suggests this is not an operator skill issue).

The root cause is that the TUI is just not the right surface an agentic coding tool. If it were a GUI with mouse support and other rich affordances, it'd be trivial to click to expand

I think the first message consumes disproportionately much percentage because it's not cached and includes the system prompt, tools, etc.

If anyone sees this, I tried it and unfortunately am not getting better results on the pelican-on-bicycle test. I think the vision models just aren't good enough yet (I tried Claude and Gemini)

I can share the code if there's interest.

Free idea: turn this into an MCP server. Give the agent the ability to virtually "hover" a path and see which part of the final render it corresponds to

Can you port tsc to go in a few hours?