Every issue at work becomes an item in this org, and all information relevant to the issue goes there: emails, chats, code snippets, documentation paragraphs, etc...
It's amazing how clearer things become, and how quickly you can get back in action if the issue resurfaces a few years later.
You don't need Facebook for that. Write down a list of the people you care about and contact them with some frequency, at least on their birthday.
An year into the project I am forced to revise my opinion. When browsing my code-base I often stumble in abstruse niche solutions for problems that should not have existed. It was clearly the work of someone inexperienced walking through walls in an AI-fuelled coding frenzy.
Having an oracle that knows all answers is useless if you don't know what to ask.
I don't mean to offend, and I'm happy for you that you've been so successful, but the advice does not make sense for people whose interest is not in popular demand.
For example, there are many failed artists out there, and it would be more helpful to these people if they were given realistic advice early on.
Finally, I meet a lot of young people (developers as well), who do not know exactly what their passions are. They are quite miserable in feeling lost, searching for their "true passion" -- which they probably simply don't have.
Many times the business just needs a boring old solution for a tedious problem that no one would be passionate about, and it's normal to engage in that kind of grind.
I would change that advice to "do what you are passionate about, among the things that the business needs, and understand that sometimes you just can't do that".
On the other hand I have seen several devs who were just good at quickly tackling whatever was necessary at the moment and became very successful without ever showing a sign of passion for computing. For them it's just a craft and they go do some hobby after that.
The same issue plagues many private companies. I’ve seen employees spend days drafting documents that a free tool like Mistral could generate in seconds, leaving them 30-60 minutes to review and refine. There's a lot of resistance from the public. They're probably thinking that their job will be saved if they refuse to adopt AI tools.
What I have seen is employees spending days asking the model again and again to actually generate the document they need, and then submit it without reviewing it, only for a problem to explode a month later because no one noticed a glaring absurdity in the middle of the AI-polished garbage.
AI is the worst kind of liar: a bullshitter.