Thanks for your thoughtful comments, Nicolas.
You're right, big companies deal with these issues differently than small companies. My experience in small companies has been that people rarely commit resources to continuity planning because there is always something seemingly more urgent going on. But if someone critical to the company dies or leaves suddenly, its very existence can be threatened.
Nobody thinks to read your documentation? That strikes me a strange. Is your documentation useful/helpful? Or is it verbose, out of date, misleading, etc., etc.?
Finding talented software devs/IT people with the range of skills required to succeed in a small business is always a challenge. And small businesses don't have the resources to invest in huge amounts of training so hiring is a perennial problem.
For the documentation reading, even when it is available and quite decent, I noticed that some people still don't read it.
This include doc of official recognized libraries with honestly very good doc. And of course it is the same for internal documentations.
Some people just don't have the "hook" to look for documentation. Maybe a part of that is they worked on projects or company/whatever where the doc was not that helpful but I think also they may take the habit to ask colleagues instant, and that fine, you gain time, but only to a point. If you want to grow yourself, you also need to know way to do things yourself.
Sometimes these things are more complicated than they first appear. It could be a habit, like you say, or there could be hidden benefits to asking for help instead of just reading the documentation. Being on the outside, I could only speculate.
We’re a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.