If I’m unfamiliar with a project I force slow work by first looking for existing process improvements, like organized GitHub milestones and well-described and m

If I’m unfamiliar with a project I force slow work by first looking for existing process improvements, like organized GitHub milestones and well-described and meta’d issues. I’ll commonly explore new tech by generating my own summarized documentation and through light tooling of initial configuration. I am in the midst of this now where an existing operational “algorithm” needs better software support. A lot of the discovery for that is starting with very general issues describing “problem” areas and then drilling them down to specific issues that might require action. It can be tedious to go this “slow,” but it’s how I get to fast.