Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I can only speak for the way I try to do things, but I try to stick with explaining how we use the different packages and avoid spending too much time explaining how the libraries work; they can and will be looking that up as they go. I make sure to point out any non-obvious hacks if any.
Ideally our Readme only mentions the tools used. I always saw it as a canary when you have to start adding "If you are going to X remember to Y".
Any tips for onboarding a new joinee to a couple-month old Django back-end project and eventually take it over, as my tenure ends?
The newbie is from a theoretical CS background and only knows very basic Django.
It's gonna be fine, I know; I'm just not sure how to go about handing over the project since even with coding best practices and detailed comments and a README.md, there's still a lot of stuff happening in the background that I know only because I've worked with it daily.
rant