(Part 2) Top products from r/coding

I'll go with a1k0n here, IIRs are the way to go, unless you want to start implementing really long filters. A 3rd-order FIR has very poor attenuation in the stopband compared to a 3rd-order IIR. The only drawback of IIRs is that they have non-linear phase response, but I guess in audio work it's not that crucial.

For playing around with digital filter design I strongly recommend Matlab's signal processing toolbox. If you don't have access to that, Octave has an implementation of pretty much all the functions in SPT and is free. With it you can do the whole filter design in digital domain, which is a lot easier for experimentation.

And to accompany Matlab-DSP-coding I'd strongly recommend Digital Signal Processing by Mitra. It's got all the basic theory plus a lot of examples in Matlab (all of which should also work with Octave); it doesn't specifically address audio signal processing, but understanding the basics will get you a long way.

I like these and would add:

3) Given how cheap they got lately, I would suggest to use at least two screens for work. More screen real estate equals more efficiency.

4) Master your tools. Memorize the shortcuts your editor provides (or learn Vim :) ), learn to take full advantage of your IDE's debugging capabilities, and so on.


...and regarding this...:
> Design patterns.

Refactoring - Improving the Design of Existing Code is a great book on this topic.

Don't forget The Pragmatic Programmer

I can highly recommend the Artificial Intelligence for Games book mentioned in this article too, has many useful techniques written in an easy to understand manner.

"More focused" is the key point for me. I have a different opinion what that means, that's all.

See here for the following quote:
> The following subjects would be off-limits: Technology, devices, software, operating systems;

For me, operating systems are relevant to coding: they define the framework that I must navigate in order to get my code to do what it is supposed to. But I can find my OS-related programming content elsewhere, I don't need to have it present in /r/coding. But I would rather exclude too much than allow too much in - noise is distracting, and simplicity stimulates focus. If people really miss something, it will find its way in.

Regardless, I can recognize a losing battle - the idea of code reviews seems to have many supporters and few opponents, so it will happen anyway if someone wants to risk and endure not-so-constructive criticism, puns and potential fame on TheDailyWTF.

I think the whole idea will be short-lived. The comment threads will provide some helpful remarks (e.g. read Code Complete, Beautiful Books, or other books, learn about various algorithms and their computational complexity to figure out better approaches, etc.). The comments will become redundant after a while, and then people will realize that they are doing somebody's homework, and that learning good style is largely a self-study, and can't be passed on in a couple of sentences. And we'll have a new rule for "no newbie code reviews here".

But I've been proven wrong by Reddit many times before, so I won't bet on my version of events. So, who's gonna be the first one to submit code for a review?

I would add Computer Systems - A Programmer's Perspective to that list.

he authored this book

https://www.amazon.com/Clean-Coder-Conduct-Professional-Programmers/dp/0137081073