HN user

a_c

1,732 karma

https://kmcheung12.github.io/

Posts14
Comments699
View on HN

People learn and relearn the core concepts from different paths. A recent trend due to coding agent is that people are learning software engineering is not about syntax and frameworks. It is just the way it is. People build up concepts with things they already understand. The same happens when someone doesn't use a book. It just went implicit and way harder for you to find the magic combo.

My own set of heuristics

1. Use less subagents. The act of using subagent already needs dumping adequate amount of context for subagent to work effectively

2. Refactor when file grows large. Reasonably scoped files is easier to understand, for both human and agents, and consume less tokens because less guessing which section of the file to read

3. More capable models for planning, learning. Cheap models for execution. Same for human teams, senior member for higher level planning while junior member more on the act of translation of idea into code

4. I wasn't doing any fancy stuff that opus can't handle

5. Consult a second opinion for things you are not sure. (I have made a skill specifically for that)

6. Audit how your habit correlates with token consumption. I found out a skill a use frequently is using a lot of context just so a subagent can get all the context. (made a tool to audit claude specifically)

Decoy Font 6 days ago

A natural extension would be a reverse steganography that trips AI into see other things in images

Many such examples with variations

- browser extensions where a bookmarklet will do (media speed control)

- tolerate-able UX where alternatives available (e.g LLM chat interface without a table of contents is a pain to me, vibe coding an extension took me less than 1 session worth of credit)

- buying bulk vs buying individually

- doomscrolling vs reading a book

- standing vs tip toeing (one I discovered only very recently that I can tip toe any time to train my toes for climbing, no need dedicated training sessions)

- getting angry/depressed online vs realising most thing on internet is about provoking emotion

I climb and I want one :)

talking about climbing apps with fellow climbers is a great way to be outside.

Indeed. The climbers I met are very supportive. They helped me scan the gym, shared their own climbing footage, which is what I'm trying to do, visualize climbing in a 3D scene.

I find it highly similar between running agents and running human teams.

Clear goal, share context, delegate but verify. Running a team of engineers also inevitably generates pages and pages of material, design spec, code, test, review. Just that we now do that with agents and agents are way less trust worthy

Indeed it is. I’m very grateful to what LLM enables me.

The revelation to me was that I used to code what I know, now I could code what I don’t know. The common path is that when I face something I don’t know, which is quite often, to move forward I have to level up my understanding.

I spent multiple 5-hour sessions spec-ing my climbing app with AI, clarifying interactions, algorithm, workflow etc. It ended up a frankenstein that I didn't recognise or know how each part interact with each other. Command line were a mess, different commands doing the same thing, with similar but redundant arguments. Everything looks kind of doing what I intended but overly convoluted and nothing really works. Real progress was made when I actually dig into the documentation of colmap/OpenMVS (essential tools, which I had never used before, in my workflow).

The AI gave me unprecedented turn around time in experimentation. The same experiments would easily take me over a month in the past. Now it was a few days. But still, real progress is made only when my understanding catch up with reality.

3D model construction of climbing gym. There is so much detail a normal climbing video can't show. Wall angle, hip position. I'm hoping to overlay human model, taken from climbing video, onto the 3D wall to make climbing visualization easier.

The system behaviour is totally up to anthropic's discretion. Its current behaviour is verifiable. In claude code, spawn a subagent with

1. Agent("Test")

2. look at your token usage

3. Repeat a few times

I didn't check again as I type this message but am somewhat sure subagent doesn't cache system prompt as of maybe last week

Will give it a try thanks for the heads up. Mind if I ask if you are referring to SendMessage? I was testing on Claude code 2.1.196. SendMessage was not available. Skimming through their change log didn’t seem to have anything related to SendMessage. There is “ Fixed SendMessage silently misrouting when a re-spawned agent reuses a previous agent’s name — the tool now detects the mismatch and asks the caller to retarget” from 2.1.199. Not sure if they are related

Regarding the lack of vision part, if you are using Claude or opencode, I've made a skill[1] that let's you talk with any models in Claude/opencode mid-session. You ask "Have claude opus to look at this PDF for a second opinion" during a session of claude with GLM5.2 or opencode with GLM5.2

It doesn't need to pass whole conversation history as context (unlike /model), you can ask follow up to that forked model (which sub agents in claude doesn't support AFAIK), and you can ask models from opencode while using claude.

[1] https://github.com/kmcheung12/second-opinion

Sometimes I find myself wanting the other way round, instead of letting LLM tell browser what to do, I want what I did manually in the browser be visible to LLM. I made a MCP to cover that use case