"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."
"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."
I would love to see this work in a team of mine in the future.
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.
I finished my stint as a Mozilla Fellow and now I'm relaunching my Patreon with a focus on, well, fixing social media.
This means I'm going to continue my concerted work trying to make the fediverse a better place, in the form of best practice guides for running instances, external advocacy, and technical tutorials and training so that more people can contribute software to the fediverse at large.
You can read a partial summary of my work so far at my new Patreon page!
I'm Prague based software engineer, currently working for Microsoft on .NET Core build infrastructure. This account is personal, though.
Personal server of Lukáš Lánský