Useful little helper site providing cheat sheets for getting a quick start on a program language.
This presentation talks about Event Sourcing and CQRS within the Microservice world.
Both Event Sourcing and CQRS are quite popular within software architecture. They build on DDD principles (although can be used separately from it).
Event Sourcing looks at retaining data in an event stream rather than a snapshot of time that we are familiar with in RDMS. This about it as a list of all the transactions (credits and debits) that have been made against your bank account rather than a current balance. The events allow you to have a full audit where as the current balance is just the current snapshot in time.
The current balance can be calculated by totalling (sum in this case) of the transactions.
To avoid the performance overhead of a walk through the event stack for the current state, you can implement event listeners which would produce a snapshot of the current state (a read only version that you may have had in the RDMS). You can register multiple listeners so that you could generate multiple optimised views of the event stream - think of it like fact tables in data warehouses.
Event Streams aren't appropriate for all problems - but are great for being able to see the version at any point. Look at source control systems for an example.
CQRS is Command/ Query Responsibility Separation. This talks about separating the logic of command (insert, update, delete) from query (select). By separating the two distinct activities you can make services more focused (easier to dev & test) and allow scaling independently.
This great article talks about agile productivity and how it is influenced by willpower - or more importantly by avoiding the need to rely on it. It talks about the neuroscience behind willpower and techniques of how to use that willpower effectively in relation to performance.
Good news here is that a lot Scrum practices play to those techniques.
I love Trello. This article isn't ground breaking - but most of the suggestions are ones I've used before - so useful if you've not played with Trello before.
In this presentation, Jim Benson discusses why Kanban is helpful. While he does give an overview of Kanban, he also talks about the physiological positive effects of physically moving a sticky to done.
If you're following my ROI series on LinkedIn, then you will see the tie into the promoting the Intrinsic Motivators.
Useful article here to compare between Azure & AWS.
In the latest article of my LinkedIn series on better ROI from software development, I have released part 2 on Agile Software Development.
You can read there article here.
This website shows you what type of cat your JavaScript framework is.
Probably the most important thing you'll learn this week.