The thing that makes me crazy about this article, others like it (and so many of the comments in response to them ) is the naive assumption that whatever the author is used to is always the case.
It's just not. I've been a developer for 25+ years, and in technical diligence looking at companies getting investments for seven, and have done diligence on 100+ companies. It's ALL OVER THE PLACE. It depends on the product, the company, the team, the way the company is managed, the business domain, etc.
For some companies, products, and teams.. the code absolutely is the hard part, and building that insanely sophisticated software is worth millions. I've seen scientific software that sold for millions of dollars per copy.
For others, the code is essentially commodity plumbing around some operational knowledge of a domain that makes nice dough with minimal code complexity. I've also seen founders who were going to spend the rest of their days floating around the bahamas because they wrote the right PHP-ball-of-mud in the right domain at the right time, sigh.
The world of software is vastly broader than the vast majority of programmers think. And there are a lot of very, very different ways to make money in it.
Regardless of the sleep effect (or lack of) they absolutely do work for reducing eye strain for migraineurs.
It's noticeable to me all the time, but if I'm borderline migraining, or recovering from a migraine, the difference between shifted and not is something I can feel instantly. Shifting all the way over enables me to eek out some work after a migraine without it flaring back up again.
At the risk of sending you down a giant rabbit hole, the book Designing Sound is all about making programmatic sounds with Pure Data, and open source low-code programming environment available for all platforms. From what I've read, the book is considered a classic in the video game sound world. It's really good. Combine that with the Cipriani book on PD and learning Ardour would give you a very good learning path.
Nice, I was going to mention that there had been several game devs on the mailing list, thanks for sharing.
The single C file convenience really is helpful. When I was figuring out the byzantine build process for incorporating s7 into a mixed JS, C, Scheme app, it was great to not have any additional foot guns there. On my eventual todo list is porting some of the same work to incorporate into JUCE apps for mobile, so good to know that worked for you.
Fennel is another language I have been watching, good to hear that worked out well.
yes, it really is. In my music pedagogy project I use it as the domain layer via WASM sitting between JS and C/C++ audio workers. It's been great that way.
That I don't know, but the s7 author, Bill Schottstaedt (who I will ping about this) is very helpful on the email list and is deeply, deeply knowledgeable about Lisp, so you could definitely ask there!
In my context, I have rigged up a REPL in Max, so I wind up using that instead. (Which is freaking awesome, because I can script all of Max from my vim buffers.)
It's just not. I've been a developer for 25+ years, and in technical diligence looking at companies getting investments for seven, and have done diligence on 100+ companies. It's ALL OVER THE PLACE. It depends on the product, the company, the team, the way the company is managed, the business domain, etc.
For some companies, products, and teams.. the code absolutely is the hard part, and building that insanely sophisticated software is worth millions. I've seen scientific software that sold for millions of dollars per copy.
For others, the code is essentially commodity plumbing around some operational knowledge of a domain that makes nice dough with minimal code complexity. I've also seen founders who were going to spend the rest of their days floating around the bahamas because they wrote the right PHP-ball-of-mud in the right domain at the right time, sigh.
The world of software is vastly broader than the vast majority of programmers think. And there are a lot of very, very different ways to make money in it.
reply