Lukáš Lánský @lukas@social.lansky.name

https://florentcrivello.com/index.php/2019/09/04/the-efficiency-destroying-magic-of-tidying-up/

"love of order is above all else about appearances. Streets arranged in grids, people waiting in clean lines, cars running at the same speed… But everything that looks good doesn’t necessarily work well. In fact, those two traits are opposed more often than not: efficiency tends to look messy, and good looks tend to be inefficient."

https://programming.lansky.name/coverage-driven-test-selection

"The idea of this year’s experiment is simple: using per-test coverage data flowing from CI to run only that part of your test suite that might have been affected by changes you did."

https://fire.ci/blog/api-end-to-end-testing-with-docker/

I would love to see this work in a team of mine in the future.

https://keysleft.com

Oh no.

https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/merge_trains/

Nice feature, looks much better than rolling builds.

By the way, given it put some more time and logic between hitting the "merge" button and the actual merge, it further strengthens the case for Azure DevOps's "auto-complete" feature. Under normal circumstances, it really doesn't make much sense for the developer to control time of merge tightly.

https://ourworldindata.org/happiness-and-life-satisfaction