Four short links: 17 July 2018

Sizing Teams, Publishing Incentives, Serverless Experience, and Configuration Languages

By Nat Torkington
July 17, 2018
  1. Sizing Engineering TeamsTeams should be six to eight during steady state. To create a new team, grow an existing team to eight to 10, and then bud into two teams of four or five. Never create empty teams. Never leave managers supporting more than eight folks.
  2. Cockygate — in which a somewhat amusing lawsuit between Kindle Unlimited authors is pulled apart, and the incentives that drove weird behaviour are laid bare.
  3. Learn faster. Dig deeper. See farther.

    Join the O'Reilly online learning platform. Get a free trial today and find answers on the fly, or master something new and useful.

    Learn more
  4. AWS Kinesis with Lambdas: Lessons LearnedThese are our learnings from building a fully reactive serverless pipeline on AWS. See also the Hacker News comments with some other thoughtful heavy users sharing their cautionary tales.
  5. DhallA configuration language guaranteed to terminate—useful for specifying Kubernetes, etc., configurations.
Post topics: Four Short Links