3 ms·
> All my classmates were either already familiar with it, or more than capable of figuring it out with a search or two. I’m guessing your program covered materi
by formerkrogemp 4y ago
> All my classmates were either already familiar with it, or more than capable of figuring it out with a search or two. I’m guessing your program covered material that required a little more effort than a google search to build basic competency in?
I did come across this charitable expectation in my CS coursework where you were given tools and expected already to know or to learn on your own. Which is fine if you want to weed people out. I can understand where someone might be frustrated if you hand them a tool and expect them to know or figure it out while they're learning new material.
- emteycz 4y agoProblem is, schools expect students to do this with like 100 tools and give no guidance on what to do, and why. It's absolutely overwhelming. Even as a professional SW engineer for 10+ years, when I join a new job, the amount of new tools and workflows is overwhelming - and that's when I at least understand the descriptions. Dumping all that on a student is just idiotic, not good teaching.
- garren 4y agoI get what you’re saying. I didn’t feel overwhelmed by git, but I’d been working with it for a couple of years, so there’s a clear bias. I did run into frustration with other tools, though. Maybe git, in particular, does deserve some specific focus given its unique status and ubiquity in the industry.
- formerkrogemp 4y agoThank you for the acknowledgement. I appreciate your consideration of an alternative view. Not everyone gits it at first and it takes some effort to learn.