tejaswidp

I found "Composing music a new approach by William Russo" a good start this. It is a pretty Nifty guide to the topic.

I read the book a while ago, It was quite an eye opener. The one thing I haven't been able to go through was the last chapter, building a "metacircular evaluator. I saved it for a time when I understood compilers/interpreters better.

Diving into codebases, like the octave and supercollider interpreters recently. might be quite interesting to re-read it.

I know what you mean, but it's not as clear cut as you think it is.

You don't operate in a vacuum when you work on projects. What if you think someone is wrong? Being direct might be a risk, because then the community might not be seen as "welcoming to newcomers" anymore.

I mean, ideas don't come out of nowhere for projects, and people who care about things, will be passionate about them. What if someone comes in the way of you building things? What then?

With the CoC in most projects, that's changing. See also: the Python Mailing list, where threads are locked and people are being banned for CoC violations.

Sure, but the primary point of her article was the abstract nature of academia which they should have expected going in.

There's also recoll, a document indexer and search tool, which I've heard is pretty good.

Why do you think PhD is a waste of time?

Aren't wavelets analogous to the fourier transform. Wouldn't that mean it would be a fundamental aspect of DSP these days?

Alan watts said that. Terrence Mckenna would probably say the opposite.

could you tell us how many books have you been able to sell on amazon?

He isn't commenting on the legality of drugs. He is comparing drug cartels to the above mentioned websites.