Skip to main content
Computer Science Educators

Return to Answer

remove redundent work, replace source control with revision control (as may not be programming).
Source Link
ctrl-alt-delor
ctrl-alt-delor
  • 10.8k
  • 4
  • 25
  • 54

For point 2. I can think of a few solutions each with different amounts of work and tradeoffs.

  1. At work we'd use sourcerevision control for this. The repository is stored in a common location where all people have access. Whenever you're done working as a pair you'd push/commit your work.

  2. Have everyone one work on a shared network drive permissioned by you. Each pair would get a folder just for them. Or its just a freeforall.

  3. Have every workstation be 'public' as in there's only one user and it's always logged in. The students will do their work, and as long as the work station is available they can work on it.

For point 2. I can think of a few solutions each with different amounts of work and tradeoffs.

  1. At work we'd use source control for this. The repository is stored in a common location where all people have access. Whenever you're done working as a pair you'd push/commit your work.

  2. Have everyone one work on a shared network drive permissioned by you. Each pair would get a folder just for them. Or its just a freeforall.

  3. Have every workstation be 'public' as in there's only one user and it's always logged in. The students will do their work, and as long as the work station is available they can work on it.

For point 2. I can think of a few solutions each with different amounts of work and tradeoffs.

  1. At work we'd use revision control for this. The repository is stored in a common location where all people have access. Whenever you're done working as a pair you'd push/commit your work.

  2. Have everyone work on a shared network drive permissioned by you. Each pair would get a folder just for them. Or its just a freeforall.

  3. Have every workstation be 'public' as in there's only one user and it's always logged in. The students will do their work, and as long as the work station is available they can work on it.

Source Link
jmathew
jmathew
  • 101
  • 1

For point 2. I can think of a few solutions each with different amounts of work and tradeoffs.

  1. At work we'd use source control for this. The repository is stored in a common location where all people have access. Whenever you're done working as a pair you'd push/commit your work.

  2. Have everyone one work on a shared network drive permissioned by you. Each pair would get a folder just for them. Or its just a freeforall.

  3. Have every workstation be 'public' as in there's only one user and it's always logged in. The students will do their work, and as long as the work station is available they can work on it.