You Need a Private Code Repository

Your knowledge should not be allowed to rot away in your brain.

Oren Cohen

--

Photo by Luke Chesser on Unsplash

If being a software engineer is your day job, you’re probably all too familiar with using git repositories for your day job. You save all of their code. But what about the code you learn to use while on the job? Those little nuggets of wisdom you discover as part of our natural problem-solving process?

You need to have a personal git repository to ensure you don’t forget those particular little nuggets you learn, make room in your mind for new lessons, and make sure the next time you need to use this code, it’s easy to retrieve it.

Let’s dive more in-depth into those points.

Save Nuggets of Wisdom

One of the nuggets of wisdom I learned while developing a feature that required me to use the multiprocessing module in Python was the Process Executor and how it makes stuff easier and reduces joins and other maintenance in your code.

If I didn’t save an example of how to create a Process Executor, I’d be googling it again when I need to use it. Now, I no longer need to do that. I can go back to my notes and save that research time.

Repurpose For Future Consumption

--

--