Reading List Jan 17-Jan 27, 2017


Reading List – Nov 21 – Nov 27


Working with RESTful Data in Angular 2 and NativeScript

Using Hot RxJS Observables In Your Service Layer In Angular 2.1.1

Angular 2 Router

Angular 2 authentication revisited

The Ultimate redux typed store implementation for angular 2 – advanced


How to read Google SpreadSheet using Sheets API v4, .Net and a Service Account

Technical Debt: A change in perspective

.NET Standard 2.0 – Making Sense of .NET Again

No API? No Problem! Rapid Development via Mock APIs

Basic Interview Tips In C#

Fix: Downloads Folder Opens Slowly In Windows 10

.NET Core Data Access

13 DevOps Influencers, Groups and Blogs You Need to Follow

Writing Great Unit Tests: Best and Worst Practices

The First Few Milliseconds of an HTTPS Connection


Science Says Earth Might Not Survive 2017: So Take These 9 Risks Immediately

New battery concept could charge in seconds, last for days

Exclusive Interview: How Jared Kushner Won Trump The White House

Uber, But for Millennials Who Want Orchestras in Their Living Rooms

Arrival’s director also made Enemy, a movie that argues history will repeat itself

WebSites Runtime Performance Resources

I attended Build 2013 in SFO and on this excellent talk by Tobin Titus on Web Runtime Performance Tobin shared lots of insight on Web Runtime performance. He shared the list of resources which I thought is beneficial who is looking for improving website performance.

Books on Websites Performance

High Performance Websites
Steve Souders, September 2007

Event Faster Websites: Best Practices

Steve Souders, June 2009

JavaScript Patterns

High Performance JavaScript Nicholas Zakas, March 2010

JavaScript the Good Parts Douglas Crockford, May 2008

JavaScript Patterns Stoyan Stefanov, September 2010

JavaScript Cookbook Shelley Powers, July 2010

Microsoft Guidance

Windows Store App: JavaScript Best Practices
MSDN, December 2012

Performance Tricks to Make Apps & Sites Faster
Jatinder Mann, Build 2012

50 Performance Tricks for Windows Store Apps

Jason Weber, Build 2011

Engineering Excellence Performance Guidance

Jason Weber, EE Forum 2011

Internet Explorer Architectural Overview

Jason Weber, PDC 2011

W3C Web Performance

Web Performance Working Group Homepage

Performance Timeline Specification

Navigation Timing Specification

Blog Posts


WPT Standalone SDK

Windows Performance Toolkit

Fiddler Web Debugger


REST – Differences between PUT & POST.


PUT implies putting a resource – completely replacing whatever is available at the given URL with a different thing. By definition, a PUT is idempotent. Call it as many times as you like, and the result is the same. x=5 is idempotent.

One can PUT a resource whether it previously exists, or not (eg, to Create, or to Update)!

POST updates a resource, adds a subsidiary resource, or causes a change.

A POST is not idempotent, in the way that x++ is not idempotent.

Open Sourcery

Web service designers have tried for some time now to correlate CRUD (Create, Retrieve, Update and Delete) semantics with the Representational State Transfer (REST) verbs defined by the HTTP specification–GET, PUT, POST, DELETE, HEAD, etc.

So often, developers will try to correlate these two concepts–CRUD and REST–using a one-to-one mapping of verbs from the two spaces, like this:

  • Create = PUT
  • Retrieve = GET
  • Update = POST
  • Delete = DELETE

“How to Create a REST Protocol” is an example of a very well-written article about REST, but which makes this faulty assumption. (In fairness to the author, he may well have merely “simplified REST for the masses”, as his article doesn’t specifically state that this mapping is the ONLY valid mapping. And indeed, he makes the statement that the reader should not assume the mapping indicates a direct mapping to SQL operations.)

In the article, “I don’t get PUT versus…

View original post 731 more words

Yahoo Axis

Yahoo today announced new visual search called Axis with desktop plugins and for mobile. Try it out

More details here.