The video shows a Product Manager using the Codex app to understand and modify their team’s codebase, relying on its built-in tools to troubleshoot issues and improve workflows despite not being a frequent coder. By collaborating with the team and iteratively enhancing Codex’s skills, the PM demonstrates how non-engineers can effectively contribute to technical projects.
The video features a Product Manager (PM) explaining how they use the Codex app to navigate and contribute to their team’s codebase, despite not being a frequent coder. The PM describes feeling the need to understand the code being edited, as well as the surrounding context, before engaging with the team or making changes. This helps them avoid making uninformed decisions or appearing unprepared in front of engineers. When encountering a confusing button in the application, the PM’s first instinct is to clarify its purpose by asking the team, rather than making assumptions or deleting features without consensus.
After confirming with the team that the button was unnecessary, the PM proceeded to remove it and created a pull request (PR) for the change. However, the PR encountered a test failure, which initially seemed daunting. Instead of manually digging through build logs, the PM leveraged Codex’s built-in skills, specifically the “skills” tab, to quickly access relevant tools like Buildkite for fetching logs and diagnosing the failure. This streamlined the troubleshooting process and saved time.
Upon investigating the test failure, Codex informed the PM that a Buildkite token needed to be installed. The PM followed the instructions, obtained the necessary token, and fixed the PR. Recognizing that this issue might recur, the PM proactively updated the relevant Codex skill to handle Buildkite tokens more smoothly in the future. This not only resolved the immediate problem but also improved the workflow for subsequent similar issues.
Throughout the process, the PM emphasizes the value of interacting with Codex in a thoughtful, step-by-step manner. By guiding the app through the reasoning process—rather than issuing vague commands—they found that the resulting solutions were of higher quality. The PM also mentions using Codex on “low,” suggesting a preference for a more hands-on, iterative approach that encourages learning and continuous improvement.
In summary, the PM’s experience with Codex demonstrates how non-engineers can effectively contribute to technical projects by leveraging intelligent tools. By asking questions, collaborating with the team, and iteratively improving Codex’s skills, the PM not only resolved a specific issue but also enhanced the team’s overall workflow. Over time, this approach helps Codex become more adept at supporting the team’s needs, making it a valuable asset for both technical and non-technical contributors.