NEDD is a one day conference in Cambridge. It’s an inexpensive way to learn about the cutting edge of database research. These are my notes on each speaker.

I’m not in management, but damned if I don’t love a good management paper. Today it’s Frederick Herzberg’s “One More Time: How Do You Motivate Employees,” where I learn to not kick an employee.

There is one scene that gets referenced several times in Rapid Development by Steve McConnell as an example of a hugely productive team.

Joel Spolsky’s writing and opinions are evergreen, and his 2004 book The Best of Software Writing shows it.

An 1984 paper that models the time it takes to complete a project, and show what happens when you pull are up against bad deadlines. The answer will not surprise you!

All of this comes from reading everything in Martin Fowler’s https://www.martinfowler.com/microservices/, and many of it’s linked articles.

Core reading

Microservices

https://www.martinfowler.com/articles/microservices.html

Microservice architectural style: building applications as suites of services

Amazon has the idea of a Two Pizza Team - a team should be feedable by two pizzas

Smart Endpoints Dumb Pipes - There is no smart choreography of messages or central busses, just straight service calls over http or something similarly simple. At most, there are message queue services (e.g. rabbitmq).

excerpt from How Complex Systems Fail

For my own reference, here are notes I took while reading Google’s book on SRE.

If you’re responsible for a large, legacy code base, here’s my hint to you: delete your failing tests.

A small trick to make “before” a bit more powerful, a bit more useful, and a bit more dangerous.