Mathematicians do not compute numbers.
39 karma · joined November 10, 2013
Mathematicians do not compute numbers.
A math professor was giving a lecture and then remarked that something was trivial. Somebody raises an objection and asks why. The professor stops and thinks hard for the rest of the lecture, then finally remarks: "Yes, I'm right, it is obvious."
There is no way that this will ever achieve anything close to $500k/year. For this to happen, at $8/month it needs to attract 5000+ subscribing, paying users. This is not going to happen when anyone can just use Google docs for free. Especially when Google is more well-known, better maintained, and integrates into existing Google accounts. There is just no good reason to sign up for a new service.
Most people have never heard of draft or etherpad. I'm willing to be that they are not actually generating any substantial revenue either, which is the benchmark for whether it's a good idea to start a business or not.
This is incredibly naive. There are many good reasons for deregulation, but propagating arguments like this just gives libertarianism a bad name.
The linked formula has been completely removed from its context
http://en.wikipedia.org/wiki/Averaged_one-dependence_estimat...
Below the formula in the page, you see everything defined and logically derived, and a brief overview of what it's supposed to do. You are correct in that Wikipedia may not be the best place to learn from scratch if you are a novice, but its purpose is more to be a concise reference than a thorough introduction.
If you need more guidance, there are thousands of textbooks at all levels of understanding, and if you opened a single one of them, you would immediately see that the "P" is standard notation for (conditional) probability.
Yes, you could not talk about Lebesgue measure at all. However, the importance of theory is that you gain a deeper understanding of the abstract objects that the code is supposed to represent in the first place. This in turn, can have practical applications.
For example, you could implement a Fibonacci function using recursion as usual. But if you study the math a bit more deeply, then you can discover Binet's formula and get it in constant time.
For example, everyone intuitively knows what holes are. Well, how do you rigorously define a hole? It took centuries to come up with the correct definition, which is given in terms of homotopy groups, and the definition of homotopy groups will look incomprehensible to the non-mathematician. Seemingly "easy" statements like "bounded three dimensional objects without holes are spheres" (i.e. the Poincare conjecture) turn out to be very, very hard (worth a million dollars and a Fields medal!)
In industry, what I've seen is that often engineers are scrambling to please managers or customers, with work divided among multiple people, so the code is usually poorly written and undocumented.
In academics, publications are of primary importance, so everything is documented. The longer timescale means there's more time to refine code that's designed for a single, focused problem. The limited scope of the programs used means code quality isn't an issue most of the time.
Also, in theoretical computer science at least, the focus is entirely on rigorous proofs and finding optimal algorithms. While in industry, it's more "get practical things done quickly so we can sell it".