Oliver's 7 questions interview

[bradcray]

This is a checklist of items that an editor, if not author, should go through prior to publishing a blog article.

• Read through
• Consider adding pullquotes?
• Check title
• Check summary and its formatting
• Check slug
• Check date
• Check author profiles
• Review tags
• Feature article?
• TOC look good? (can all entries be a single line?)
• Does start_test work?
• Check captions
• Check code comments?
• Check for console vs. terminal choices and consistency
• Spellcheck
• Check hyperlinks
  • If a release announcement, check for docs/main or docs/ vs. docs/x.yz
• Make sure to commit+push any changes made in this pass

Post-merge:

• Update website's "news" section
• HPE Dev card
• Social media blurb

[e-kayrakli]

Potential pullquote

Chapel’s biggest benefit for me is how quickly it lets me prototype
high-level parallel and distributed code, and then incrementally
optimize it.

[e-kayrakli]

Potential pull quote

I went from knowing little about
parallel programming to becoming comfortable both as a graph scientist
and a parallel programmer.

[e-kayrakli]

Another alternative, though a bit long

At the end of the day, these tools are all about
parallelizing operations, and Chapel helped me see how parallelism
maps to real problems without needing to first understand every detail
of message passing, the underlying runtime, etc.

[bradcray]

Thanks for the pullquote suggestions, Engin! I think this one works well when shortened to:

Chapel helped me see how parallelism maps to real problems without needing to first understand every detail of message passing, the underlying runtime, etc.

[e-kayrakli]

Pull quote?

That clarity helped me understand
how parallel and distributed codes work, and later made it much easier
to read and work with codes written in other parallel frameworks.

Maybe edited slightly to start as "Chapel's clarity" in the quote itself.

[bradcray]

I like this one too, but think I'll just stick with the previous, as the two appear close to one another in the text and carry a similar message. So the two I'm going with are:

Chapel’s biggest benefit for me is how quickly it lets me prototype high-level parallel and distributed code, and then incrementally optimize it.

Chapel helped me see how parallelism maps to real problems without needing to first understand every detail of message passing, the underlying runtime, etc.