It's actually exactly that. Her set of skills is to do that actually accurately with setpoints for both distance to the objects as well for different wavelengths simulataneously.

Aye, this is a pattern which indeed seems to become more and more common in an attempt to "modernize" design and "making it more lean". Yeah, right

It's a bit funny that the title reads "write nice and stable code" - but it's actually a plea for "proper" versioning.

Starting with the versioning a few examples are given - and I read it as "this is not good versioning" as it continues with the very basic description of how semantic versioning works. Yet all those examples given above are excellent examples of how semantic versioning works at its best! """ 10. Build metadata MAY be denoted by appending a plus sign (...) Examples: (...) 1.0.0-beta+exp.sha.5114f85. """

And these meta data, referencing used library versions and actual hash of the commit used in the build, are given there - and exactly these meta info on used library versions may help a great deal when it comes to checking bug reports as programme behaviour may differ between versions, but work with any.

Did anyone notice that the study is about 7 years old? Maybe user behaviour changed somewhat since....

Working by example may work. And analysing many successful examples may also yield some insight. But make sure to get the full picture: look also at those who fail. They might have tried the very same methods to most degrees. Don't fall for the survivorship bias :) It might be other factors which are truely important than those which seem the obvious ones.