Skip to content

Commit

Permalink
initial checkin
Browse files Browse the repository at this point in the history
  • Loading branch information
@jowens
jowens committed Jul 11, 2023
1 parent 8f70dce commit 63b9644
Showing 1 changed file with 244 additions and 0 deletions.
Loading

1 comment on commit 63b9644

@behoppe
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jowens for this clear, comprehensive, and well-organized "big article." Here are some comments about the blog post part of this article. (I will email separately about proposal parts.)

I recommend re-ordering and streamlining things for a blog post with an eye towards making it more engaging and persuasive. IMO the top goals of the blog post are

  • Engaging our audience (CS professors) with your personal voice and a short, compelling case that we surveyed the landscape of teaching SPE and have a good handle on the issues and how we can help. The details of what we learned are eventually important, but not right away. The important thing is to establish our credibility so that our readers are paying attention and we can move to the next goal...
  • Helping our audience to see themselves in the landscape that we have surveyed. Near the top, I recommend the blog post call out some diverse examples of CS professors and their hallmark issues, so that a reader can quickly sense that he/she belongs in this story too.
  • Inviting our audience to participate in the next steps. For example, instead of just reporting things to add to the curriculum, and reporting that we hope professors take ownership of particular lectures or materials, let's use this blog post to put those ideas into motion. Of all the possible additional topics, which would most entice a reader to reach out to us and offer help? Let's make those invitations prominent, and push the less enticing opportunities down, where they won't distract from the audience engagement that is the main goal of the blog post.
  • Offering specific services to our audience. For example, instead of reporting that we are helping faculty share resources, we can offer that service outright and invite faculty to join the circle of trust. I think there are other good ideas for services in this article, and I recommend we prioritize a few for piloting and use the blog to promote our new services.

Separate from the blog post, I have been working on a page of resources for people who want to learn SPE (as opposed to resources for people who want to teach it). I think we might migrate some of the details in this big article into that page of resources -- especially the "specific tools that are useful" and "relevant projects that we heard about." I would love to incorporate those into a solid page for anybody learning SPE, and then the teacher-oriented pages (like this blog post) can reference that.

What do you think? Let me know if you'd like specific help following up with any of this.

Please sign in to comment.