RushOrm for Android replaces the need for SQL by mapping java classes to SQL tables

Dive into all the details that a JavaScript developer needs to know to be a great TypeScript developer — Basarat Ali Syed  

How you shouldn’t implement base classes

public class Entity<T>
{

  public T Id { get; protected set; }

}

Motivation for such code it pretty clear: you have a base class that can be reused across multiple projects. For instance, if there is a web application with GUID Id columns in the database and a desktop app with integer Ids, it might seem a good idea to have the same class for both of them. In fact, this approach introduces accidental complexity because of premature generalization. 

There is no need in using a single base entity class for more than one project or bounded context. Each domain has its unique path, so let it grow independently. Just copy and paste the base entity class to a new project and specify the exact type that will be used for the Id property. 

The best TypeScript links every week, right in your inbox.  

The TypeScript Tax
A Cost vs Benefit Analysis 

Opinionated vs Flexible

TypeScript or JavaScript

Paradigms

The Future 

Using the TypeScript 2.1 async/await construct in Aurelia 

Entity Framework Crash Course: Point of Sale Project