1,801 karma · joined January 12, 2014
* Iron-Clad Java: Building Secure Web Applications.
* How Linux Works: What Every Superuser Should Know.
* Black Hat Python.
Paused reading
* Functional Programming in Scala.
* Version Control with Git.
Bought due to HN praises, skimmed through, but probably won't read
* Structure and Interpretation of Computer Programs.
I agree that the economy might not be "big enough" yet. And yes I agree that we need more progress and probably more growth. But do we need to be in a hurry?
It surprises me that none of the commenters has mentioned global warming - a side effect of economic growth.
So, what do HN readers think about the correlation between economic growth and global warming? Should monetary policy not bother about including global warming side effects due to increased co2 pollution due to economic growth into their economics equations?
This greed doesn't lead to less global warming or happier people. I think politicians and economists should start thinking about what actually makes people happy. Economics is efficient management of resources nothing else. Giving the population ability to stay healthy with affordable health care, moderate taxes and stability should be a main priority.
HTML http://www.w3schools.com/html/default.asp
PHP+MySQL http://www.w3schools.com/php/php_mysql_connect.asp
I'd prefer we all just disagree when someone says something is girly. Man up and stand up for men and women's rights to be judged as people not gender without whining when someone fails to do so.
"Kyle Simpson8 months ago Report Abuse I can assure you, my goal of splitting up the content into a book series had ZERO to do with making more money. It's actually quite the opposite. One of the things I hate the most about tech books is that I spend $35-50 on a big book of which there's only a few chapters I actually care about. I almost never read a whole book.
I decided when I wrote this content that I'd make each logical chunk of content available separately, which means that you can buy only the stuff that you actually care about. This COULD quite likely mean that I make a lot less money in the overall picture, because there will be plenty of people who don't buy all the books, or even not enough of them that would have generated the same income as a single book would have.
This places you, the reader, more in control, not only of what you buy and own, but more deeply of what you spend your money on compared to the content you get. Rather than being about me greedily making more money, it rather downgrades my ability to make bigger chunks of money per copy for the majority of people who (like me) only want/need part of the content.
With regards to this content being "pointless", that seems quite a spurious and unsubstantiated claim. Pointless to you? Perhaps. But I feel quite certain there's a lot of content in there (like block scoping, etc) that most developers (and perhaps even you) aren't fully aware of. If you're already a JS expert (even on all the new ES6 stuff coming), then you probably do know JS and I'm not sure why you bought the book.
The spirit of the whole series (given the title) is to get us all (myself included) to admit how we don't fully know JS and how we need to dig deeper than we have before. If that's lost on you, I'm sorry.
One last comment: these books are all available fully for free to read here: http://YouDontKnowJS.com In addition, Amazon's site makes preview snippets of the book available to read for free so you can get an idea of what you're buying. It's a shame you apparently didn't read the content/previews before buying, you could have saved your $5-7 (at least it wasn't $35-50)."
I'm also thinking exactly like you and want to focus on Android programming and Java development but keep distracting myself with Linux Kernel books, pen testing with Python etc. I wish there were more advanced topics in narrow topics so that the cravings for deep understanding and knowledge and dream of awesomeness would be satisfied.
That said, I still think the page is very well made and the sounds sound great! Well done!
Don't blame the tool blame the fool :).
Modern often means simple. It should be easy to operate or resources via a web API and REST is often the answer. Use the HTTP technology which is already there and embrace it and create technologies around it. KISS principle is king, as opposed to inventing a proprietary complex and useless own method of data communication.
I love when something is explained in such an excellent simple way and was a good refresher for me. This is how things should be taught.
I think recent success of these soft topics may be based on people's feeling of self improvement and enlightenment. I can understand that it creates a nice feeling, but prefer to be enlightened by actually learning to solve real things in a more elegant, efficient way than before and I prefer to learn the rest via actual work experience.
Real self-help would mean to become independent from advice from the outside and looking into yourself and finding out how you can do something better by actually doing it...