Imagine you're inheriting a production web application that needs ongoing updates, but the existing documentation is sparse. Would you begin by reviewing the code, deployment and infrastructure setup, logs and error tracking, access credentials, or by speaking with the previous team? What would your first steps be to understand the system safely?
4 Answers
Start by making sure you can deploy and roll back safely. Check where the app runs, how changes reach production, who has access, whether backups or snapshots exist, and whether rollback is straightforward. Then inspect the logs, recurring errors, support issues, and deployment history before tracing those problems back into the code. A handover conversation is useful, but real production behavior is usually a better guide than old documentation.
Infrastructure and access come before deep code review for me. Verify credentials, revoke access that is no longer needed, rotate important secrets, identify dependencies, and locate the monitoring and logging systems. Once I understand how the application is operated, I can review the code paths that matter instead of trying to read the entire codebase without context.
I’d talk with the previous team if possible, but I’d prepare a detailed question list first and document the answers. Ask how the system is supposed to work, what has caused incidents, which workarounds exist, and what technical debt or management-driven compromises they had to accept. Having them review the resulting notes can make the handover much more useful.
Another reasonable approach is to take a small, low-risk ticket and use it as a guided tour of the system. You learn the architecture, testing process, deployment flow, and hidden dependencies while making a useful change. I’d still establish rollback, monitoring, and access safety first so that the learning process doesn’t put production at risk.
I’d also ask the previous team about shortcuts, known compromises, and areas they wanted to improve. Those details often never make it into the documentation.