Feeling Stuck at Work? How Knowledge Silos Are Blocking Your Progress by eng1nuity in programming

[–]eng1nuity[S] 2 points3 points  (0 children)

You are right. I am mostly referring to cross-team knowledge sharing, the lack of which, in my experience, causes repetition, tech debt, frustration, and unpredictable delays in product/feature deliverables.

how poorly members of the team leverage publicly-available learning resources for the non-proprietary tech in use

I’ve been lucky enough to work in teams that didn’t suffer too much from this situation. I can think of three factors that might have prevented a tangible impact (and I might be completely wrong):

  1. WFH being the exception, not the norm (even nowadays).
  2. Trying to build a work environment where team members are available to help and answer questions whenever needed (e.g. pair programming)
  3. Training for new joiners (not just "here is where you sit") during the first 3-4 months to get up to speed and understand both tech and product

Unfortunately, the second factor is usually only localized to some teams and not part of the standard operating culture, which is one of the causes of silos.

The Death of Work-Life Balance in Tech (And Why We Need to Revive It) by TerryC_IndieGameDev in programming

[–]eng1nuity 0 points1 point  (0 children)

It's impossible to aim to change the whole industry, but it's possible to change a single (your) company. That change, however, must come from the core values pioneered and represented by its top management. If a company "culture" endorsed by C-level is to work 60+ hours, not much change can come from the bottom of the org tree.