virpo
I'm a big fan of SponsorBlock for YouTube too, from the same dev.
I took all the channels HN keeps recommending (3+ videos in Karpathy's data) and made a page with their fresh uploads as they come in: https://hn.youtldr.com
(I make YouTLDR, which writes the one-line answer under each video.)
My plan was to try to find the "answer" for videos in comments. Never really got around doing it, but LLMs make the possibilities more interesting and easier.
Edit: this is also a good opportunity to ship something like this: https://hn.youtldr.com, like Karpathy's HackerTube, but with the new videos from "HN-vetted" channels.
I made myself a thing that tries to answer the title + thumbnail from the transcript, and shows me the answer if there is a good one. Never launched it, but it's at youtldr.com if you want to try.
But your agent can see what you're doing! So I wrote down 100 levels and made it so your agent checks which ones you already do and suggest what to learn next. It reads check.md, runs a read-only script that prints only names and counts, and finds interesting things for you.
The 100 tips are based on my own usage, but also on what internet-famous engineers have been doing and sharing.
The code is at github.com/virpo/levels. Tell me what you think! :)
https://newsletter.kentbeck.com/p/party-of-one-for-code-revi...
How 94 internet-famous engineers use coding agents
So I went through their repos, blogs, talks, tweets of 94 of them and made a card for each of them. Things like agents, models, harness, rules, skills, hooks and how they review whta their agent wrote. Agents did a lot of the digging, so every claim links to its source and you can check it yourself.
Most surprising finds are, that 8 of 94 still read every line of their code, and 21 more of them read the riskiest parts and skim the rest.
You can also make your own card (with your own agent), and it will suggest what trick from these 94 engineers you should try adapting.
If something is missing on a card, it means I didn't find it, not that they don't use it. If you spot something wrong, you can open a PR, happy to fix it.
I used oak plywood, and it has held up well so far, including in our kitchen. You do get the occasional tiny splinter, but nothing serious.
The main trick for getting clean holes, especially on the back side, is to drill into a sacrificial board so the exit side stays supported.
If helpful, here's a close-up photo: <https://files.virpo.sk/pegboard.jpg>
For a bigger pegboard, I'd almost certainly go the plywood route, ideally with access to a CNC drill or a laser cutter through some community workshop. The hole precision mattered more than I expected, and getting a whole board right with a handheld drill was surprisingly tedious.
So while I can't compare the whole market, I can definitely say the jump in ease of use was huge.
Prusa printers are great too, especially if you care about supporting a company that invested heavily in open source. I found them harder to justify on price, but I also understand why people choose them for that reason.
There have also been pretty public disputes around Bambu's use of open-source work from the Prusa/Slic3r ecosystem, so that is part of the decision too.