feat: add blog article for content team interview with jan david nose of rust infrastructure team #1749
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
traviscross
reviewed
Nov 23, 2025
content/content-team-interview-with-jan-david-nose-rust-infrastructure-team/index.md
Outdated
Show resolved
Hide resolved
traviscross
reviewed
Nov 23, 2025
content/content-team-interview-with-jan-david-nose-rust-infrastructure-team/index.md
Outdated
Show resolved
Hide resolved
Contributor
Author
|
Added text transcript as well, feel free to take a look. Nice excursion into learning what's possible with Machine Learning these days. |
Contributor
Author
|
Looks like this now: |
traviscross
force-pushed
the
feat/content-team-interview-jan-david-nose-rust-infrastructure-team
branch
3 times, most recently
from
775853a to
48b6524
Compare
traviscross
approved these changes
Nov 25, 2025
traviscross
added a commit
to PLeVasseur/blog.rust-lang.org
that referenced
this pull request
Nov 25, 2025
… of rust infrastructure team
Co-authored-by: Travis Cross <[email protected]>
Now that we don't have any associated files for this interview, let's not create a directory for it. Similarly, we had earlier shortened the title; let's correspondingly shorten the URL.
Everything on our blog is about Rust, so it tends to strike more the kind of tone we try to strike to say "the Project" or "the Language Team" rather than repeating "the Rust Project" and "the Rust Language Team" everywhere. Let's trim some of those uses accordingly.
There's no particular reason to minify this YouTube link, and people tend to prefer unminified links, so let's use the full one here.
We actually released this video a while ago; if we were only now releasing it, that wouldn't be a very accelerated timeline (as the blog post mentions about the release). Let's state the release in the past tense to account for this.
At the time of the interview, JD was at the Foundation, but he's since gone on to bigger and better things. Let's adjust the wording to account for this. In this adjustment, we'll tighten up the wording generally.
The note about our release of the video is its own idea and deserves its own paragraph, so let's add a paragraph break here.
It reads more clearly to lead with whom we mean by "we" in this context rather than to have that appear later in the sentence.
We had already mentioned "infrastructure"; let's remove duplication of that later in the sentence.
Rather than using Unicode single and double quotes, let's just use the ASCII ones as we normally do. This looks more regular on the blog. We'll keep the use of em dashes. This also fixes a place in the text where duplicate double quotes had appeared.
The tooling doesn't add the "the" before the team name, so we need to add that ourselves.
traviscross
force-pushed
the
feat/content-team-interview-jan-david-nose-rust-infrastructure-team
branch
from
3d1c295 to
f93f625
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First blog post containing interview from Content Team efforts
cc: @rust-lang/content, @jdno, @MerrimanInd
Rendered