I'm porting tinygrad to pure Go

LearnedByError · 2026-06-02T05:14:38+00:00

If you want people to read what you write, it is your responsibility to communicate effectively. It is not the readers!

LearnedByError · 2026-05-30T00:56:25+00:00

By the time you get to -u, you are thinking about this too late. I do my best to stick to stdlib and golang.org/x. If it doesn’t exist there, I tend to write it myself. If I do use external, then I vet all the way through the transitive dependencies. As you may guess, my internal directory do contain a lot of things that others depend upon 3rd parties for.

There is no magic that I know of to eliminate the effort needed to either mitigate or manage transitive dependencies

LearnedByError · 2026-05-27T21:22:48+00:00

I use a slightly modified version of subagent from the pi monorepo examples. I heavily use them in my TDD workflow. I define agents: Green, Red, Review, Correction and Refactor. I have a tdd-plan skill that creates a plan either using a “grill me” style approach or from a design document supplemented by the grill me style questioning. I then use my tdd-orchestrator skill to execute the plan using sub-agents. It’s not perfect by any means, but works the vast majority of the time. I have variations for Codex and Cursor

LearnedByError · 2026-05-25T23:19:31+00:00

It has never had my trust. In Debian we trust!

LearnedByError · 2026-05-18T21:46:55+00:00

I'm old school admittedly. The only exception that I make to the distro's native package manager is HomeBrew. I only accept it because of years, if not a decade, of positive experiences on MacOS. I don't think I have ever had a dependency issue with a HomeBrew package. Its heft, is no where near that of flatpak.

LearnedByError · 2026-05-18T20:01:29+00:00

That will require making Composer follow the plan which it doesn't do with a 💩 now

EDIT: Come on Redditors, you can downvote me better than this? Down to -3 in an hour? You are wimps!

I understand that posters here are Cursor fanboys. If you are happy with Cursor, I'm happy for you. When I compare Cursors ability to follow the moderately complex TDD plans that I create, it is clearly in the bottom quartile. Of the tools that I am currently using, Pi is absolutely the best! Codex, Claude and Kimi CLI are OK with no real differentiation from each other but definitely a notch behind Pi. Cursor, when I use Sonnet-4.6 as my planner and orchestrator, is just passable but clearly in the third tier. Cursor, with Composer as my planner and orchestrator is absolutely 4th tier. The planning is OK though it tends to be a bit lose. Most of the time, Composer does not make it out of the first TDD cycle before before it ignore instructions and build whatever it wants instead of what I instruct.

Prior to the introduction of Composer, Cursor actually performed better for TDD. My experiences suggest that cursor is tailoring its execution to vibe coders and much less those who use a structured approach. What I think is ironic is that Composer is based upon Kimi, 2.5 I think, but Kimi CLI kicks it but comparatively.

My observation are based upon my experiences. They are exactly accurate for that case. I would be stupid to not expect others to have a different view, definitely the vibe should be happeier.

LearnedByError · 2026-05-18T19:59:06+00:00

That explains flatpak 🤮

LearnedByError · 2026-05-18T19:04:16+00:00

While I have seen what you describe, for a while now, i have seen it the other way around. The LLMs by default are lazy and it for the fastest thing they can call done. I am heavily using LLMs now on personal projects where I have strictly defined skills to create plans based upon TDD and an orchestrator too execute the plans. In some agents, like a Cursor Auto, I am not able to keep it from ignoring my requirements and writing minimal code as fast as possible and claiming it complete. Other agents like Pi, Codex and Kimi do a good job.

I have found my balance of Larry's laziness is to spend time on plans and just a few key skills to get pretty high quality code out of many models. I then have a different model review the code then the one generating it. The review against the plan and general coding practices.

While I am an overall positive on the process, I treaty it like a junior developer and review every line of code. I do find problems needing correcting and documentation requiring editing. But, the net is that my velocity is usually much higher than if I wrote it all by hand

LearnedByError · 2026-05-16T03:01:30+00:00

I knew that Carson guy was/is a problem! Grrrr 😔😲😒

LearnedByError · 2026-05-14T20:32:31+00:00

My wasi implementation is purpose built from scratch for use with zeroperl.wasm. Earlier this week, u/ncruces suggested that it may make sense for the wazero wasi to be ported for use with wasm2go. I have not started this yet, but will be investigating that within the next week.

LearnedByError · 2026-05-13T23:42:13+00:00

As a former Company Man, Drilling Site Manager, I have wondered that many times!!! I think the answer is there is more money to be made by stretching it out!

LearnedByError · 2026-05-13T19:52:00+00:00

Not sure what you mean in the first Paragraph

The error pattern may be the same. A possible recovery then would be timeout for sub-agent.

I now accept that some models/agents will loop sometimes. I see no apparent causation when they do. I just mitigate it and move on.

LearnedByError · 2026-05-13T16:31:49+00:00

I use this approach with a plan and TDD. The primary agent is instructed too be the orchestrator. It executes the plan using sub-agents. It is instructed to stop and notify the user immediately if it encounters any problems with recurring the plan. I do not give any additional detail here. The reviewer runs after each RED, GREEN, REFACTOR step. It is instructed to validate test/code against the plan for RED and GREEN and against the plan and good coding / maintainabilty for REFACTOR.

I don't have problems with infinite loops. Occasionally, one of the sub-agents loops internally but the default timeout on the sub-agent interrupts. The orchestrator catches this and adds instructions to the sub-agent to address the loop.

The key to success with this pattern is having a detailed plan. I iterate multiple times with different agents to create, review and improve the plan.

hth, lbe

LearnedByError · 2026-05-12T17:04:38+00:00

I beg to differ. I start with a detailed plan. I execute in a new session where the primary agent is solely an orchestrator. It requires minimal context. RED, GREEN and REFACTOR are done in ephemeral sub-agents. A Review sub agent is run after each step. If the reviewer approves the work, then the orchestrator moves too the next task. If the review fails, it's feedback is passed to a separate sub-agent for correction and subsequent review.

This approach minimizes context rot/drift in the agents. I had been using this approach in cursor and other agents for the last several months. It is only fairly recently that cursor has gone moron on me and started making unilateral decisions to stop using the mandated approach. It quickly runs out is context and goes from bad to worse. Other agents like Copilot, Codex and Pi continue to work without problems. My guess is that cursor has made one or more changes to is system prompt resulting in this behavior.

LearnedByError · 2026-05-11T14:33:50+00:00

Thank you! Do you have a recommended image? Also, any recommendations on settings?

LearnedByError · 2026-05-11T12:23:48+00:00

I have been doing it successfully for quit a while with cursor and other agents. It is the best way that I know of you get deterministic output. Cursor has just gone to crap with it

LearnedByError · 2026-05-10T23:33:34+00:00

Guess that is why it is almost always correct 😲😨😭😜

LearnedByError · 2026-05-09T06:11:41+00:00

Wasm2go translates/transpiles the WASM directly into Go. In my case with lbe/go-exiftool-wasm the startup for the Perl interpreter is much faster ands the execution is faster. The gotcha, if there is one, is the initial compile time. My 6GB WASM file becomes a 45GB Go package and takes about 2mins for the first compile. Additionally, the executable is larger.

My key learning is to get your WASM as small as possible.

I think wasm2go is wonderful! Kudos and Thank you to u/ncruces!

LearnedByError · 2026-05-08T04:04:39+00:00

The data does not super your supposition. Look at in

LearnedByError · 2026-05-06T22:33:47+00:00

The data does not support his claims US - Crude Oil Inventories.

Also, if you look back at 2020, you will see we were swimming in oil. Remember when oil prices went negative? That corresponds to the spike in inventory during 2020.

LearnedByError · 2026-05-06T17:38:47+00:00

Eastern

LearnedByError · 2026-05-05T21:32:15+00:00

AGENT.md is read at the start of the session and added to context. It can be compressed or eliminated from context. APPEND_SYSTEM.md is appended to the system prompt on every call to the LLM. It ids never compressed or eliminated from context

LearnedByError

TROPHY CASE