Do you have meetings that your team have to bring technical subjects to talk about? We have it here, but it doesn't seem people like it, and it's difficult to find someone willing to talk. I wondered why the leads or managers insist on having these kinds of meetings.

Attitude thing. Most devs are too lazy to learn in their own time or do a good job by reading documentation and learning on the job.

A mandatory tech talk session is a good way to find out if people have any kind of passion for the craft, and hopefully to foster it in the team.

In practice though Deva with no interest will never change just from this.

@craig939393 oh, I see. Yes, it makes sense. One weird thing here, though, is that most of the developers are very skilled engineers. I don't feel comfortable about talking unless it is something very complex.

@santiagodias you just explained why this is a very good idea.

Especially those who are extremely skilled are very "prone" to fall into the pit of overengineering or overthinking.

As always, balance is the key.

But not talking at all leads to the bus factor 1 problem aka "noone except him/her knows what this thing does" and especially skilled people have a dislike of talking about solutions.... :)

My complaint about these meetings is that the presenter wants to make things super low level to look smart. So they show something with a super specialized solution but you have no context for what needed solving and how the solution was a solution.

Once I showed a library (at a high level) that helped us a lot for a specific situation. Then everyone was implementing it for no reason because it looked neat. No! Use it when it makes sense not because it looks neat. Then I became the “resident expert”.