There's as well this one (but my impression is that it didn't get traction - pragmaticbookshelf.net/titles/dbleg...)

There is more than one book. I know at least: Object-oriented reengineering patterns: www.oscar.nierstrasz.org/files/oorp/O..., working effectively with legacy code (M. Feathers) and Kill it with Fire (www.goodreads.com/book/show/54...) - more strategic/management level

And how would you rate working with legacy Code in usefullness of software developers skills?

To everyone sympathetic for Ukraine who is trying to downplay this or do whataboutism pointing to corruption in the West - the best thing we can do for Ukraine is to help it eliminate corruption ASAP, as it's the single biggest weakness of the country.

Ось польська стаття - culture.pl/en/article/t...

Дивіться англійську Wikipedia - там теж згадується, що початково немо мав бути поляком - en.wikipedia.org/wiki/Captain...

And I have not seen high-performance teams without proper-engineering practices (although it is as well depends on stage of product - search for product niche vs keeping found product stable and growing)

Secondly, if one believes Gary Gruver "Leading the transformation" book, there were no difference in performance of teams, working in continuous delivery environment, whether it's uses classical ones per weeks meetings or follow Scrum-like meetings schedule.

I see several problems with this understanding of agility - first, it is not team who decides what to work on, but the product owner decides, what are the priorities and the team gets to say what is doable and how it should be done ( in the frame of company standards).

Not quite sure due to accus lifetime for electric vehicles (which could be more close to typical buses (ca 12 years) vs up to 40 years for trams)

huggingface.co/spaces/Huggi... and gist.github.com/jph00/3c97a2...