I started using C# a couple of years ago, and my favourite part of the language and integration by far is LINQ. The ability to write natural code which can be fired as a database query or series of optimised collection manipulations is impressive, but mainly just nice to work with.
The problem is that using a nice syntax such as the ES6 arrow functions, (s => s.active), would require us to craft an object to pass as the first parameter during execution. Naturally, determining this before the function is run is very difficult to achieve dynamically. Instead, I opted to use Esprima to derive the results statically. As such, while the evaluation is conducted from a function, such function is never actually called.
Data-First development is an idea that I’ve had for a while and it’s the way I approach most development projects these days. I’m sure that you will have done it too, but just never quite thought about it.
The way I see development is to start with the data. At the very beginning of a project it’s important to get the specification right, and as part of that – design the data store and models. That makes sense, but once they are designed they are inherently forgotten about until they need to be changed.
Instead, I propose a simple workflow that at the start of the project admin interfaces to manage the data is the first thing that is built. There are a few reasons.
Notify is my take on what a notification library should be.
So this is just another library I need to pull in? Absolutely, and your users will love you for it.