3 ms·
I don't disagree with your main point, and I think the apprenticeship model could work wonders in many tech environments. Harder to implement when you have a ve
by cydonian_monk 9y ago
I don't disagree with your main point, and I think the apprenticeship model could work wonders in many tech environments. Harder to implement when you have a very migrant worker population, even at normal rates of turnover.
There is however some merit to writing down details to critical or seldom-used processes in a communally-accessed place such as a wiki. Keeping it up to date and having someone review it regularly has to be part of the process.
- ThatGeoGuy 9y agoBuild instructions, and dependency assumptions for starters. Sometimes the hardest part is just figuring out how to get a project running, or learning what kinds of settings need to be enabled on deployment. As for craft and actual in-code understanding, I think the masonry example can fit well (see pair-programming as a more fluid example of this). Granted, if you have an API, you probably want to at least document the interface with an example of how to call it. The complex bits of "how is this architect-ed can be better taught by 1:1.