One of the hardest things in the life of a programmer is joining a large legacy project and making sense of it. This is made even harder when that programmer is junior, since that makes everything worse. What tops everything? The fact that often the senior ones don't have time, so the junior has to fight with the problems alone.
I would want to see ideas that make the life of a junior developer easier when they join a project
Ideas:
reorganize documentation based on it's importance (e.g. frequency of use of an API, as opposed to
automatically generate documentation (based on NLP analysis of the code)
propose new visualizatoin, code navigation tools that could help
... your's?
But even before we have ideas, we should also do interviews with developers in junior roles to learn and understand about their needs better.
One of the hardest things in the life of a programmer is joining a large legacy project and making sense of it. This is made even harder when that programmer is junior, since that makes everything worse. What tops everything? The fact that often the senior ones don't have time, so the junior has to fight with the problems alone.
I would want to see ideas that make the life of a junior developer easier when they join a project
Ideas:
But even before we have ideas, we should also do interviews with developers in junior roles to learn and understand about their needs better.