✳flâneur — a map of the web's best reading

new codebase, who dis? (How to Join a Team and Learn a Codebase)

samueltaylor.org · 2,374 words · saved by 1 readers

I have switched teams more often than I have had to implement an AVL tree, and you can guess which one of those two was taught in school. I wish someone had taught me how to join a new team! While learning a new codebase can be daunting, I've found a few things that work for me. You should do at least three things when joining a new team. The order of these three can be whatever you like, but all three should be done as soon as reasonably possible. First, you’ll likely set up the development environment. As you do this, pay attention to just what it is that you're setting up. For instance, if you need to get Redis running locally, then that's a good hint that there's some caching happening somewhere. Noting the order in which you run internal projects helps you understand dependencies. If the feature store needs to be running before you bring up the model serving service, that's a hint that the model serving service may depend upon the feature store. Such dependencies start to hint at

new codebase, who dis? (How to Join a Team and Learn a Codebase) - Samuel Taylor Home > Articles > new codebase, who dis? (How to Join a Team and Learn a Codebase) new codebase, who dis? (How to Join a Team and Learn a Codebase) I have switched teams more often than I have had to implement an AVL tree, and you can guess which one of those two was taught in school. I wish someone had taught me how to join a new team! While learning a new codebase can be daunting, I've found a few things that work for me. You should do at least three things when joining a new team. The order of these three can b

Explore this link on the map →

related reading