Although the article is written in a slightly humorous vein, the concept may be valid; there's the case of 28 year old woman who fell 300 feet onto a rock and survived (see http://www.sjtrem.com/content/19/1/63 )
tl;dr--if your lower extremities progressively absorb the impact, the lethal forces on the spine and head can be lessened enough to survive.
Data Structures and Algorithms in Java by Adam Drozdek has a lot of actual code that works. I think the code is online, but the book is worth buying because things are explained well (http://www.amazon.com/Data-Structures-Algorithms-Java-Drozde... ) to be fair, there's quite a bit of math supporting Drozdek's book.
Stay away from Sedwick, in my experience his examples are incomplete/don't compile and are abstract.
Now, while, CLRSS is the gold standard (Joshua Bloch cites it in his Java Collections code) be aware it's math heavy and lacking on implementation details. Rumor was that there was a CD of CLRSS examples somewhere...
> However, many finite-state automata regex implementations have existed for years
If you read his write-up on RegEx matching, you'll see notes that Thompson wrote an implementation in the mid-60s, so he definitely doesn't claim they're new. What he does claim is that most regex libraries don't use them, even when the regex they're matching to doesn't require backtracking.
A lot of people get the CS degree and stop learning or lose the drive to write or create anything interesting. Who knows, maybe they never had it:
It's easier to take a creative person and teach him engineering than it is to teach an engineer to be creative.
Me: B.A. English and Classics. I'm getting a masters in CS--only because I already read/have read many of the graduate texts. I started programming at an early age, but I wasn't interested in CS because the universities were still insisting on Fortran and Assembly, and I'm sure Cobol was on the list of requirements too.
Lastly, deep domain knowledge is priceless--no fancy algorithm trick can beat it. Someone without specialized domain knowledge can't even envision what he doesn't know.
Success in software and startups is largely determined by one's commitment to keep learning and trying to improve.
Spring and J2EE are modular, not object oriented to any great degree. One can implement more OO further down the chain, such as in model objects, of course, and in other custom subsystems but the overall J2EE/Spring model is a hybrid of procedural/imperative and some OO.
a good counterpoint to your idea is: Would You Bet $100,000,000 on Your Pet Programming Language?
http://prog21.dadgum.com/13.html
--Don't worry, as for myself, I see only questions, and answers that only bring more questions.
Users love a sparse UI, but you've gone overboard. You need to add descriptions to the different pricings; the labels aren't intuitive.
I assume you mean 3 brands = monitor three brand destinations (e.g. youtube.com mentions, twitter mentions, and yahoo news mentions). That is confusing to marketing people. Try to make it more clear that you offer increasing depth penetration for a single brand. The multiple users feature isn't intuitive either.
--Neither of these items were adequately answered by your FAQ.
I would revise your FAQ language, it comes across as too chatty and colloquial. Your trying to get into the wallets of marketers, act professional. Your design is clean and well done, now bring the writing up to the same level.
