SQL is a bastard of a language. You pretty much got it.

Most of my code is kept very simple. If there is a way that isn't exact, but close enough, and it reduces enough, I'll use it, and add the extra later. I get away with it by calling it prototyping, and my boss will usually just use the prototype and not have me dev further.

Use logs. You can use logs to find whatever is causing rage quits, or whatever.

My immediate thought is that you are either making your project way too complex, or you are in way over your head. By the time you start making projects like that, you should have a solid grasp on what works for your team.

It would be more professional to keep it in. It's a widely accepted standard.

I somehow expected more from FPH and Niggers.

It really depends on what you are doing. Systems where you need as much performance as possible? Yes, math really helps. A program that can't fail but can be slow? No need for math, just a shit ton of boundary checks and unit tests.

Windows. Do you have any good tutorials?

It takes 2 years of college comp Sci to understand.

Wait, so did they prove NP = P to be false?