I swing back and forth. I go for months without touching the code, then I go for months where I stay in touch. It's easy to think a code base is decent when

I swing back and forth. I go for months without touching the code, then I go for months where I stay in touch. It's easy to think a code base is decent when you stay close to it. Diving into a new code and unfamiliar code base allows me to see how new engineers will approach the code base, what's the onboarding/setup docs? Is it automated? install.sh or containeriazed? Are there tests? FAQ? user documentation, maintenance document? architectural documentations? If I can jump in the code fast and get moving, it's great. If not, I know the team is slacking and I figure out why and cover that area. If pressed for time, then I might do the test/bugfixes cycle. I code multiple times a week at home, so I'm not really pressed to program at work