not sure if this is the path we would like to take, but raising the question in code if helpful. many 301 students experience a significant time-dump (time dump for students and TAs actually) when trying to install mongoDB locally. The answer always seems to be the same "oh, that thing we told you to do, you don't actually need to do it".
Instructions for the "what-if" or "eventuality of" failure would preserve everyone's time and most importantly save student bandwidth for being 301 ready! Can we just call it out and reap the quality of life benefits across the org?
Alternatively, can the MongoDB install just go away, even if just for now? because we allow WSL usage, using Ajax is just the way we teach them in class anyway! why have half the class install mongoDB which is never used locally?
not sure if this is the path we would like to take, but raising the question in code if helpful. many 301 students experience a significant time-dump (time dump for students and TAs actually) when trying to install mongoDB locally. The answer always seems to be the same "oh, that thing we told you to do, you don't actually need to do it".
Instructions for the "what-if" or "eventuality of" failure would preserve everyone's time and most importantly save student bandwidth for being 301 ready! Can we just call it out and reap the quality of life benefits across the org?
Alternatively, can the MongoDB install just go away, even if just for now? because we allow WSL usage, using Ajax is just the way we teach them in class anyway! why have half the class install mongoDB which is never used locally?