> My question is: Is thinking about music as applied mathematics a good way to create good music? Or is it just the most easily digestible model of music for the crowd on this site?
You are probably aware that there are these things called synthesizers, which exist both hardware and software, complex pieces of technology that can shape sound. There are people who are specialized in creating them (with code and/or electronics), people who are specialized in programming them (creating presets) and people who excel in using them to make music. And many more different profiles who are in between. Each will care about different aspects, they all contribute to making music.
Life is not black and white, and music neither. What is even "good music"? What is your mental model for "the crowd on this site"? In your questions, aren't you reducing the possibilities of learning by putting these into boxes?
The world is big, life is rich and people are much more diverse than what one typically perceives.
Tbh I've only personally tested on Firefox (desktop and mobile) on Linux and Android, and some friends tried on Chrome.
I'm going to install Chromium and see if I can reproduce -- thanks!
Thanks for trying it out and thank you for the honest feedback.
That's interesting, many friends of mine tested it and nobody reported an issue with loading.
(Btw I wrote the audio loading code more than 10 years ago, it wasn't written by any LLM -- you're free to judge tho)
Yes, the +22 at the top means the remaining levels. I need to clarify that, you're the second person that seems confused by it.
Fair point, my example was indeed "shipped to production" and may not compare a throwaway static generator toy project.
I still think those estimates are off, because I think many of those projects would need significant research and learning time, possibly more than actually coding -- not to mention time spent troubleshooting when something goes wrong.
I quite enjoy the spirit of the article, and I believe joy in programming has become even more important in the AI agent coding age we're leaving.
However, am I the only one finding those time estimates way too short?
I'm not the fastest programmer on Earth, but I'm not the slowest either, and I think most of those projects would take me a lot more time than those estimates, specially if I'd be working only 2-3 hours per day.
I feel most of those projects would take significant time researching and learning about the subjects, before even starting to code.
Example: recently I replaced my Pelican blog by my own hacky static site generator written in Odin, working 2-3h per day, it took me 2 weeks -- and this is a simpler project than many on that list.