First I should say that this book is not a step by step manual for acquiring a job at Google. It’s more an updated version of the author’s previous book “How to move mount Fuji”. This book is full of mind-blowing puzzles and quizzes that the top notch tech companies use to ask during their interviews. At the same time it’s not an encyclopedia, it gives you an exciting insight of the interview process at Google. The author had spent a lot of time interviewing recruiters/interviewers/interviewees to get to a point where he can explain why the interviews have become what they are.
The book is really interesting from scientific point of view, you can get there answers to many rhetoric questions that were asked centuries ago. My favorite question was asked by Newton :”Where a man can swim faster: through water or syrup?”. It had taken few hundred years to get an answer for this question. This book is full of amazing puzzles like this that would definitely help you to develop your analytical thinking.
The only flaw of this book is a fact that it’s not very practical, you would forget most what you’d read in a couple of days =)
I’ve been at Kazan for quite a few times, but never as a conference speaker. I was surprised by the technologies these guys use. I’ve been thinking that Kazan is not so well developed in terms of tech(and startups) amplification as Moscow and Saint Petersburg. I was completely wrong. Most of the attendees were working at a startup or were building their own tech startup. Most often used technologies were Ruby on Rails and Coffeescript. There were only one guy who had confessed that he uses .NET. I was the only person there who had been programming on Lisp. IT community in Kazan is very young definitely =)
I love meetups! I like to meet new people and learn new things. Last but not least it’s a great opportunity to make new friends.
Last Tuesday we had a third meetup at Luxoft Moscow. This time we’ve talked about web apps full-spectrum testing and how to synchronize the data between a server and a client using the MEAN stack. Andrey Kasatkin did a great talk on how to minimize the data flow using compulsory caching. We’ve talked about AngularJS, Node.JS, Java, TDD, Selenium, PhantomJS, Scala, highload, patterns of building robust web apps.
It was really interesting to discuss some things that i’d never thought of, like comparison of concurrency patterns in Java and PHP. Igor Sysoev who came to our meetup was as solid as rock =)
This 40+ pages manuscript shouldn’t be considered as a book, but it’s author insists to call it so.
There’s a certain lack of materials covering building a robust Rest API with Spring. Most of the manuals I’ve seen operate with JAX-RS, which Spring MVC doesn’t conform to.
There’s also a great talk by the creator of Apache Shiro which I would recommend to anyone striving to do a scalable web service regardless of particular language/technology you use.
I’ve been doing web services for a long time using different technologies (node, Clojure to name a few). I always try to do it as efficient as I can. This time I had an issue while integrating security layer into Spring MVC.
To make a long story short, this book is a waste of time:
It’s huge, some parts of it are repeating. I have no idea why the author has intended to do so much copy-paste
Some postulates are not true. Though Spring security 3.2 had a java config this book says that it hadn’t.
It doesn’t cover features of Spring 4 at all. The author has forgotten to update his book. Albeit he aggressively promotes it.
For a free ebook it’s not awful, but i would definitely recommend you to find some other book.
I have to admit that this book is the most complete manual for AngularJS. I haven’t had an opportunity to read it from cover to cover, though I use it as a manual very often.
Most of the topics that I’ve referred are well covered. Albeit some of the items are outdated(like a broad coverage of scenario runner which is fully replaced by Protractor) because Angular is extensively improving, it covers most of the topics you’ll ever need to know.
It’s a great manual, but it’s boring. Angular team should replace the demo application with chapters from this book. If you enjoy reading encyclopedias then this book is for you.
“James Murphy and IBM are teaming up to turn US Open tennis match data into music on the IBM Cloud.
Hear the music at ibm.com/usopen” Seriously? A guy from LCD Soundsystem analyzes Big Data? I don’t know how much did they pay to this guy, but he did a tremendous amount of work! Music is very different, mostly idm-ish, sometimes it gets ambient or minimal-like.
I’ll be giving a talk about the process of developing corporate single page apps next Saturday(20.09) in Kazan.
The talk will be mostly about my experience as a developer, tradeoffs that i had to pay developing “thick web apps” using Angular and lots of its complementary modules. I’ll talk a little bit about developing Rest api that suits most of the corporate restrictions. If there’ll be no backend devs i won’t emphasize on it.
A good practical book for anyone taming the asynchronous nature of Javascript. It could be read in a few days, but the concepts it teaches you are invaluable.
May be it’s a bit outdated and it makes a lot of accents on Backbone and Node.
I’ve enjoyed reading it, the book is written nicely and it’s simple to read.
Finally, i‘ve read this book! I have a point that i should finish every book that i’ve started to read. This book was an exception, because i wasn’t able to finish it for a few years. I had all sorts of execuses not to read this book, some of them were a lack of time and a complete disinterest in the subject of this book.
I was wrong, the book is interesting. It’s a sort of holy grail for those who want to know how generics work under the hood and where to apply them. As for me i was interested in the second part of it which is “Collections”. It’s nice and comprehensive guide that describes almost every entity in the Java 6 Collections API.
If i have read this books many years ago i would have avoided many pitfalls =)
There’s a certain lack of materials covering building a robust Rest API with Spring. Most of the manuals I’ve seen operate with JAX-RS, which Spring MVC doesn’t conform to.
I have to admit that this book is the most complete manual for AngularJS. I haven’t had an opportunity to read it from cover to cover, though I use it as a manual very often.
A good practical book for anyone taming the asynchronous nature of Javascript. It could be read in a few days, but the concepts it teaches you are invaluable.
‘ve read this book! I have a point that i should finish every book that i’ve started to read. This book was an exception, because i wasn’t able to finish it for a few years. I had all sorts of execuses not to read this book, some of them were a lack of time and a complete disinterest in the subject of this book.