5 ms·

We're using Slack the product design course I'm teaching at University of Michigan this semester[1]. Not only does it do that stuff better than Piazza, but it'l

• konschubert 10y ago
  Your second point rubs me the wrong way, a little bit. You probably didn't mean it like this, but... I think educators should have the education in mind first, and employability second. In this case, nobody is going to put Slack on their resume, so... I just find the argument strange
  • ethbro 10y ago
    As I heard it put when I went through GT, "We're training you for the last job you'll ever have." The more I'm out in the working world and interacting with people from a diversity of educational backgrounds, the more I agree with that approach. (I'm specifically thinking about the "No, we as a profession tried that in the 70s, and here's why we decided it was a bad idea" moments)
  • sampl 10y ago
    I could definitely see why you read it that way! I just meant that Slack has some drawbacks, like any tool. Specifically at work, when large groups are collaborating on important projects, I've been relying on wikis, email, and issue trackers more. If the same issues creep into the class, we'll reconsider Slack. What probably won't change is the popularity of online collaboration tools for all workers. Fostering a community of similar learners to ask questions, share work, and help each other is one of our goals for the semester.
  • callalex 10y ago
    Nobody puts bash on their resume either but in my observation interns that come in with extensive command line/tooling experience from school (myself included) are much more likely to be seen favorably and converted to full time because they can spend less time fighting with their computer and more time delivering.
    • smileysteve 10y ago
      Bash is maybe not the best example because it's indeed a skill listed for many devops positions.