Looks fantastic and very clean. I will be interested to know how to manage the codebase across the team. Is it possible to run these scripts simultaneously if it stored in a central location or every team member has to have a version of a Master notebook?
This is a great question. If you do things "correct", you have a github repository where you keep track of all the tools of the team. Everyone can then propose added features etc - the tool is something everyone can contribute to, but the changes must be accepted by the owner. This works amazingly. But if we are honest, you will never have all engineers in a team being on GitHub. So I think it's important to have someone being responsible for the master notebook, and for updating it. Similar to Excel templates people will end up making local copies and adapting the script to do things a little bit different. This is both the huge benefit (super flexible), but also something that calls for caution. You need someone being responsible for the tools, so it doesn't become a wild west. But I'm curious to hear what input others have to this as well.
wonderful
Thanks for sharing. Looks interesting and you delivered it well. I am looking forward to your courses.
Thank you! I'm launching the course next month :)
Very nice Timo! 🎉
Thank you! 😃
exactly what i was looking for
It is so motivations to read comments like this. Thanks for letting me know
Hola ING saludos desde Colombia 🇨🇴🇨🇴
Looks fantastic and very clean. I will be interested to know how to manage the codebase across the team. Is it possible to run these scripts simultaneously if it stored in a central location or every team member has to have a version of a Master notebook?
This is a great question.
If you do things "correct", you have a github repository where you keep track of all the tools of the team. Everyone can then propose added features etc - the tool is something everyone can contribute to, but the changes must be accepted by the owner. This works amazingly.
But if we are honest, you will never have all engineers in a team being on GitHub.
So I think it's important to have someone being responsible for the master notebook, and for updating it. Similar to Excel templates people will end up making local copies and adapting the script to do things a little bit different. This is both the huge benefit (super flexible), but also something that calls for caution.
You need someone being responsible for the tools, so it doesn't become a wild west.
But I'm curious to hear what input others have to this as well.