Links from 2020

Quality stems from and is proven by an implemented testing plan by which components are inspected prior to release. This article describes criteria and tools for testing components and how to order making them at a high level to help teams plan.

Hydrogen has an efficiency problem. You need to convert other forms of energy to hydrogen at a loss. Then you need to store it and transport it, which is costly and may impose quite some energy cost for cooling or compression. Then you need to convert it back to electricity, also at a loss. If you start at electricity, the electrical grid and batteries would be much more efficient. If you start at oil or gas, you could use convention ICEs and get comparable overall efficiencies. For them transport and delivery is a solved problem.

Fewer than I'd expected :(

A different take to the 2016 version.

During test-driven development we write tests to verify that features conform to desired business outcomes; with fitness function-driven development we can also write tests that measure a system’s alignment to architectural goals.

That early work on Adaptive Design has already done the hard digging of finding reference points and developing frameworks to guide product design for adaptation - it’s the anti Apple, the anti Amazon, the anti DRM. I’d love to for designers to share their ideas for future adaptable iPhones and adaptable apps, expand the discourse, and pushing back on the status quo. Adaptive Design is a movement worth reviving in 2020.

A React performance exploration with interesting stats and pointers.

Consistency alone can produce consistently poor outcomes without flexibility. If the system is too strict, teams are constrained and the results are rigid and dull.

It’s not currently possible for one account to own multiple repositories in the same network.

Oh, right.

32. One hour of prep per one minute of talk

One of the key elements of Google's software engineering culture is the use of defining software designs through design docs. These are relatively informal documents that the primary author or authors of a software system or application create before they embark on the coding project. The design doc documents the high level implementation strategy and key design decisions with emphasis on the trade-offs that were considered during those decisions.

Somehow I missed this first time around.

An attempt at modifying the original "skateboard to car" agile analogy to not require additional context.