[arkh]

> It does not matter that they will all leave in couple months, the know-how will stay.

How about no. I think there is a big divide between people who do project maintenance and those tornadoes. Most new hotness people want to put on their resume will bite you in the ass 2 or 3 years down the line. But the super hero tornado will already be 4 companies out of sight so they'll never see what the things they started ended being. And when they stumble upon an old project started by another different team of tornadoes they'll complain.

[adrianN]

There is resume driven introduction of new technologies and then there is introducing modern source control, a CI pipeline, a modern compiler toolchain with activated warnings, a usable bugtracker... all of which is often missing in small companies that only do software on the side, or live in a slow moving market.

[jswizzy]

I work in defense contracting and version control is either non existent or dated at most companies. I've gotten very good at selling git to management.

[arkh]

2 months to introduce those kind of changes usually mean it will still be in the "people don't want to change their way of doing things" phase. With most of the infrastructure half deployed, the process ready to be cargo-culted and a lot of things directly copied from stack-overflow into critical parts of this process. The know-how never got shared and won't appear to fill the void.

[adrianN]

That our hypothetical tornado managed to start introducing change during just 6 months is imho a strong sign that at least some people want to change. In my experience introducing changes takes years.