673 karma · joined May 31, 2017
Alas it appears this wasn't of interest to HN as it never made it past the "new" queue.
It's the same when you get a junior dev to work on things, it's just not how you would do it yourself and frequently wrong or naive. Sometime is brilliant and better than you would have done yourself.
That doesn't mean don't have junior devs, but having one doesn't mean you don't have to do corrective stuff and refinements to their work.
Most of us aren't changing the world with our code, we're contributing an incredibly small niche part of how it works. People (normal people, lol) only care what your system does for them, not how it works or how great the code is.
Cursor, Windsurf et al have no "moat" (in startup speak), in that a sufficiently resourced organization (e.g. Microsoft) can just copy anything they do well.
VS code/Copilot has millions of users, cursor etc have hundreds of thousands of users. Google claims to have "hundreds of millions" of users but we can be pretty sure that they are quoting numbers for their search product.
Obviously nobody is really using Ladybird yet and there will be many more such issues to address, so now is a good time to evaluate how to avoid such mistakes up front.
So:
- Humans make mistakes all the time and we happily pay for those by the hour as long as the mistakes stay within an acceptable threshold.
- Models/agents will get cheaper as diminishing returns in quality of results get more common. Hardware to run them will get cheaper and less power hungry as it increases in commodity.
- In all cases, It Depends.
If I ask a human tester to test the UI and API of my app (which will take them hours) the documented tests and expected results are the same as if I asked an AI to do it, the cost may be the same or less of an AI to do it but I can ask the AI to do it again for every change, or every week etc. Have genuinely started to test this way.
For real "lessons" you'd probably need to start at chord progressions, go into scales and how the chords relate back to those, then move to these types of soloing technique lessons.
AlphaTab is the star here https://github.com/CoderLine/alphaTab - it's been maintained tirelessly for years by Daniel Kuschny.
I've started to build this type of lessons sitea few times in the past and never really got it together enough to release anything. I've done scale/chord/arpeggio tools: https://github.com/webprofusion/scalex
Most of us don't do that, those that do are sometimes eventually considered "influencers" and "thought leaders" (urgh), because they have focused on the visibility of what they do.