317 karma · joined March 23, 2015
“Deliberately destructive trolls” is interesting phrasing when held up against “roasted dead orphans.” If we owe no consideration to the former, you prove yourself such with the latter.
2: The Obesity Code, Dr Fung Probably the most eloquent and effective breakdown of how and why obesity comes to be and what to do about it. As a bonus, it’s really funny!
3:Not Alone, Craig Falconer I picked this up on a whim and enjoyed it more than any other work of fiction in the past year. It’s a first contact story that focuses on the media and politics.
4:Measure what matters, John Doer This book has transformed how my team runs. Anyone in any kind of management role should read this book.
5:Win Bigly, Scott Adams I’m going to be controversial with this one. It’s an interesting story that provides more practical tools for persuasion than any book I’ve ever read (and I’ve read every popular book on the topic). If you want to know how to apply influence read this book.
One thing to note. API Gateway is super picky about your response. When you first get started you may have a Lambda that runs your test just fine but fails on deployment. Make sure you troubleshoot your response rather than diving into your code.
I saw some people complaining about using an archaic version of Node. This is no longer true. Lambdas support Node V6 which, while not bang up to date, is an excellent version.
Anyway, I can attest it is production ready and at least in our usage an order of magnitude cheaper.
The real problem is that I can write a native iOS app in a fraction of the time it took to write a Xamarin app. Swift has improved iOS development speed so much I'm not convinced we need cross platform app engines (excluding games).
As for Android, yeah, native Android sucks. Activities and fragments are the worst idea anyone has ever had and no one agrees on best practices. But even with cross platform high levels of abstraction like Unity3D you still need to understand them. So, my current advice is to suck it up and write it native twice. Pick your favorite OS, start with that, and then port the logic.
For all the people calling this out as a hack I would counter that it is actually an example of elegant code reuse.
Additionally, if you are using NoSQL as a backing store then solutions like class serialization don't make any sense since you will need to communicate in JSON anyway.
As for the NHS the mother of a friend died due to negligence while being transported home. So it's not all good, which is why the system cannot be judged this way.