4 ms·
I always make sure I can still compile and execute the code. If I can't, I get someone to update the README files so that I can. That also helps me make sure ne
by lordnacho 8y ago
I always make sure I can still compile and execute the code. If I can't, I get someone to update the README files so that I can. That also helps me make sure new members can be onboarded.
I also do off-critical-path features and bug fixes. That said, I did write a fair bit of the code base before taking a more managerial role, and I contribute to discussions about what will make the thing faster.
- ansgri 8y agoCompiling and running your team's code could be the most powerful excercise to stay connected with the engineering part. Way too often I would discover that some functionality declared as 'done' cannot be demonstrated in any way, and such discoveries initiate discussions leading to meaningful decisions.
- lordnacho 8y agoYeah exactly. I see it as a form of QA. It's not serious if discovered early, but I've come across times when there was some new dependency I didn't have, forcing me to google how to install it. So then I tell the team and someone will update the docs. Basically, if only the people who wrote something can compile/execute it, it isn't done.