DEV Community

Cover image for How do you handle KT for new developers joining an existing project?
Boomiga
Boomiga

Posted on

How do you handle KT for new developers joining an existing project?

When a new developer joins an existing project, we usually spend hours on KT sessions and share documents like the BRD. But sometimes even the BRD is outdated, and a lot of project knowledge stays with existing developers.

What if there was a tool that acted like a Project Guru, knowing the ins and outs of your project's code, requirements, architecture, and workflows?

Here's how I'm imagining it:

Easy onboarding: When a new developer joins, simply share your Project Guru link. Instead of spending hours on KT sessions and sending multiple documents, they can explore the project themselves.

Ask anything: Developers can ask questions about specific modules, business logic, workflows, or how something works in the code.

Always up to date: The tool tracks code changes and keeps project knowledge updated, so new developers aren't learning from outdated information.

Automatic BRD updates: You can import your existing BRD or ask the AI to generate one based on the current code and available requirements. When code changes, it suggests documentation updates for developer review and approval.

Keep everyone informed: Whenever someone makes changes, the team gets a short summary of what changed, who changed it, and which parts of the project might be affected.

The idea is to reduce repetitive KT sessions, avoid outdated documentation, and make sure everyone understands what's happening in the project.

I'm still exploring this idea and haven't started building it.

Does your team face this problem? How do you handle KT today? Would something like this actually help, or do you think existing AI tools already solve it?

Would love some honest feedback, especially from developers and tech leads.

Top comments (0)