Summary
Curtis gives a new hire the lay of the land: clone the repo, use your Mac not Windows, read the docs, and we'll sync tomorrow. It's a straightforward dev onboarding call.
⚡
TL;DR
Curtis onboards a new developer to the team, walking through repository setup, hardware requirements, and a week-long onboarding plan involving local development and eventual GPU VM access.
Want this for every new video Tests posts? Brevyd summarizes each upload automatically, the morning it drops.
Takeaways
- ✓Use your Mac for development instead of Windows because the codebase needs a dedicated GPU and your M4 will handle it better than an Intel Core 7.
- ✓Read through the repository documentation and instructions first, then collect questions for a follow-up call rather than asking everything at once.
- ✓Plan to get local setup comfortable this week before moving to the staging GPU VM next week once other team members join.
Key moments
4:05Hardware recommendation
“I would suggest use the Mac for development here because Windows could work, but you need like a dedicated GPU to run DOCX effectively.”
6:43First week roadmap
“Day one just you know get comfortable with the repository. You can upgrade things and fix things. I wouldn't maybe upgrade Python version and stuff yet until you've got everything set up.”
7:56Communication plan
“Once you got Slack you just ping me whenever and then yeah, normally quite quick to respond or you can jump in a call.”
You just read one. Brevyd does this for every upload.
Follow Tests and every new video comes back as a summary like this, in your morning briefing. No watching required.