How PMs use the Codex app

Key Takeaways

As PM on the team, I don't code that often. So, I like rarely understand the code that's being edited like and the code around the code that's being edited. So, I kind of want to read up on that before I look stupid in front of the team. I actually want to be kind of careful like when you decide to tag any engineer or even when you want to file a ticket. In this case, I saw, you know, there was this button and it was kind of confusing as to what it did. So, my gut my immediate thing is to say, okay, what does this button even do? I'm just asking a question. So, then I pinged the team and I was like, hey, this this is a strange behavior to me. I just confirmed that we don't need this button. You know, I don't want to go around deleting people's buttons for no reason. So, like, ah, we don't need it. Okay, great. So, I told it to delete it. Um, and actually, I got distracted and I was working on some other stuff. Um, saw the change. We went back and forth. So, I created PR and I saw that my PR got approved, but there was a test failure. M you know I have become so lazy like the moment I'm like oh I got to go into like build kite and like look at the test logs you know it's like ah you know but uh the app has all these great skills and so I could just click into the skills tab and I just be like build kite okay sick someone is like already figured this out for me so I'd be like okay let's go back to this thing and just be like build kite fetch logs why failing and and it told me okay you need to install the build kite tokens so I did that so I was like okay I I ran the command to get the token now fix my PR. So what I immediately did is I went to our main the top level folder in the repo which is where all the skills are and I just asked it to fix this problem. I had to ask you how to set the build token. I I don't want you to have to do that next time. So you know read the roll out reflect on what might fix it and like update the skill. I probably could have just said update the skill, but I feel like kind of helping it like know how to think through it results in higher quality, especially because I'm often using codecs on low, which I think is like an under underrated technique. Um, and so basically, uh, we, you know, we went had a bit of a back and forth, but ultimately made an update to the thing that is in a PR somewhere. Just to summarize, like we went through this inductive journey where I was looking at user feedback and I saw a thing, I asked a question, realized this probably needed to be changed. Yeah. >> Uh so then I like made the change in and then in making the change I had a PR failure. So so I used a skill to fix the PR failure but in the mean then improved two skills kind of as I went. And so over time Codex just gets like better and better in working on a codebase which is pretty fun.