Our company is building a remote team, and similar to Gitlab, we are discovering that staying in sync is not just a good value but a way of life. Trello, wiki, and code help us repeat our assessment work and ensure everyone is on the same page.
We are also putting non mission-critical information in a Wiki; basically as a tl;dr of the more dense documentation.
I think it's one of those tools which demand a lot of expertise in setting them up, or you will paint yourself in a corner, with explosive paint.
So true. But when you have a culture and an industry where 2 years ia a long tenure at a company and a long lifecycle for the latest faddish "framework" or whatever, it's impossible. I'd love to stay somewhere 10+ years and work on a single significant application the whole time. But it seems to be impossible to find such a gig. Experience is generally undervalued throughout our entire industry.
Try CAD. The industry is full of crusty applications pushing 30 years. I'm sure some of the careers are equally long.
JPL has a formal database that maintains all its requirements documentation. Though, it isn't very user friendly; and you generally have to know what you are looking for.
When I was there, most of the knowledge transfer happened by talking to the older folks around. As a result, I ended up developing close work relationships with people who had been there for 20-40+ years. The historical context they provided on current and past designs was incredibly useful, and not something you would find in a requirements document.
Software was a different matter. Until recently, when the internal GitHub was introduced, finding and digging through code was not as straightforward. Each team/section maintained their own repos. And there was very little consistency, some used subversion, others cvs, accurev, etc, so it made it difficult to find and read code for projects outside your purview. Naturally, this led to software fiefdoms. In contrast, I work at google now, which is the polar opposite: I can effectively read through the entirety of google3 and send a CL/patch to just about anyone.
After all they're accountable for spending taxpayer dollars on stuff that can crash, burn, explode, and in order to keep funds coming they must be able to prove they're not just making money vanish for no reason.
Seriously, the degree to which age discrimination is an accepted reality in tech today is a great failing, and one that has enormous hidden costs over time.
Sadly I know a number of extremely talented older engineers who have been discarded like trash only to be constantly rejected in their search for new employment, until some of them just give up. It's remarkably ignorant and short-sighted of employers who practice this kind of discrimination.
It's laziness mixed with incompetence mixed with the simple reality that too many companies consider it a competitive advantage that they're completely fucked up in their process and procedure but manage to somehow churn out something anyway.
And if you're not hitting your targets, why, move the target! Imagine how much easier NASA's job would be if they could say the moon shot was a success even though they only got something into orbit because we redefined what a moon shot was.
That's a 'reasonable' cause for being short sighted, but it still means they are short sighted.
This is the way in biomed:
>'When scientists finished the first draft of the human genome, in 2001, and again when they had the final version in 2003, no one lied, exactly. FAQs from the National Institutes of Health refer to the sequence’s “essential completion,” and to the question, “Is the human genome completely sequenced?” they answer, “Yes,” with the caveat — that it’s “as complete as it can be” given available technology.'
https://www.statnews.com/2017/06/20/human-genome-not-fully-s...
Even in a relatively small team >20 I have found that even simple communication or sharing of knowledge falls apart _Very_ quickly.
Maybe I'm not actually supposed to be in the loop, but it still doesn't feel like how teams are supposed to be ran.
The secret: Employee retention.
Everything is easier when the knowledge stays in the company.
But, for me, another amazing thing about these long term projects is the sheer amount of knowledge that needs to be maintained and passed on to new people, over the course of several decades. To pull it off, this need of knowledge management and transfer must be so deeply engraved in the culture of the organization. How do they do it in this day and age of "FAQs", "Forums" and "Helpdesks"? :)
In all seriousness, what do you do to maintain "knowledge" in your organization?