Podcast episode 2.1: Ryan Djurovich #3280
Merged
Conversation
This file contains 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
create file for Ryan's episode
|
Notifying subscribers in CODENOTIFY files for diff 81bab19...88276dc.
|
add episode summary
first review/edit up to line 111
content-hacker
commented
Jun 11, 2021
podcast/2.1.md
Outdated
| Yeah, that makes a ton of sense. ,But that first issue by the way, I think is really important because it kind of drives focus in the process. But, I think one of the challenges that we have is, so when we were emailing earlier back and forth, we're talking about the different stages onboarding, and you'd mentioned that there's kind of the immediate issue of setting up your dev environment and going through the cycle of shipping something at first, but then there's kind of this later stage, which is acquiring a high level understanding of the code base, and the technical architecture and all that extra context that makes you a really powerful. I would say we don't really have a good solution to ensure that people get that understanding. It's mostly just osmosis and hope a bit. Do you have thoughts on that second stage? | ||
|
|
||
| **Ryan Djurovich:** | ||
| Yeah, for sure. Like contributing to that code base in that first stage, doesn't cater for the complexity of the system that you're working on, right? It's just really the tooling aspect getting a PR up. But that second part that you're talking about, if there is a very complex system that you're expecting someone to work on, how do you get them across that architecture? How do they understand that the way the code is structured? And I think that's probably one of the things that Ruby on Rails, and those kinds of frameworks reduce the cognitive load of, because you had these conventions in place and people could jump into these types of systems quickly. But when you're talking about kind of lower level things in Go or Rust or whatnot, it's a much more varied code structure. And then in terms of architecture, yeah, I think this is kind of a poorly solved problem in the industry, because the thing that people tend to lean on is documentation, which often becomes stale quite fast. And that's where things that I've seen recently, tools like the code tool plugin for VS Code. |
There was a problem hiding this comment.
@beyang do you know the name of the code plugin referenced here?
add buzzsprout link
set published to true
update intro
update mp3 link
content-hacker
deleted the
content-hacker-podcast-season-2-episode-1-djurovich
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
create file for Ryan's episode
preview link: https://deploy-preview-3280--sourcegraph.netlify.app/podcast/onboarding-ryan-djurovich/