Log in or sign up to participate in this discussion.
With an account, you can revise, criticize, and comment on ideas.It responds live as you make changes to your code
This seems useful only for small codebases. If the music is composed of all the code in a large codebase, each PR would change only a small subset, making the difference in the music almost inaudible.
It doesn’t play the whole codebase at once. It walks through the code line by line, and when a file changes, it jumps to the changed lines and plays an accent made from them, rising or falling with that file’s health. So a small change in a big codebase is as audible as one in a small codebase. What’s quieter in a big codebase is the overall stage, and that’s on purpose: one long function shouldn’t make a whole healthy codebase sound sick. Bugs are the exception, since they count in full. One syntax error drops even a huge project from beautiful to meh.
I think you defeated my criticism. That’s kind of cool, I get it.
Relatedly, I think in the future, software engineering will mostly be you talking to voice agents and looking at diagrams the agent is generating and constantly updating to help you understand the code/ideas. This is kind of how students already learn in the classroom, where there's a teacher who talks them through a drawing on the board, etc.
