Zeitgeist.5

Being an account of some things that captured my interest this week.

Apparently last week I’ve been mostly thinking about process.

The million dollar engineering problem

Details of how Segment reduced their AWS spend. The details on tracking DynamoDB partition imbalance are really useful.

The implication here is that you aren’t paying for total throughput, but rather partition count. And if you happen to have a few keys which saturate the same individual partitions, you have to double capacity to split a single hot partition onto their own partitions rather than scale the capacity linearly.

PipelineDB 0.9.7 Release

Latest PipelineDB release introduces Delta Streams.

Perhaps the most powerful capability this enables is the sharing of work between continuous views for greater efficiency and simpler, more elegant continuous topologies.

Why we discontinued our Android / iOS SDK and Why JavaScript is the future of app development.

We honestly think JavaScript will take over the world of app development — be it web, mobile, or desktop with one codebase being able to run on all the platforms.

I’m coming around to this world view. JavaScript is already everywhere.

App performance monitoring provider increases throughput by 2,000 percent with .NET Core

Speaking of JavaScript, have you considered .Net? MS marketing, but this Reddit Thread has some more details from the team involved.

108 Counterintuitive Things QA People Know About The Field Of Software Testing

Counterintuitive things about testing #6: service-oriented-architecture would be the worst thing you could possibly do.

The Zero Bug Policy

An approach to improve quality and throughput by focussing on bugs.

The crux and the controversial part of this system is that all bugs take priority over all new feature development or improvements.

How Discord Indexes Billions of Messages

Deep analysis of how Discord uses ElasticSearch to index billions of messages.

The MVP is Dead, Long Live the Rat

Rethinking the MVP.

MVP is used so much it’s lost its original meaning.
A Riskiest Assumption Test is explicit. There is no need to build more than what’s required to test your largest unknown. No expectation of perfect code or design. No danger it will prematurely become a product.

The biggest problem I’ve seen with the MVP is actually working out what Minimum and Viable actually mean. Products are often pushed with effort in all the wrong places.