How deep should your understanding of a system be? How deep should you go with it?
It depends on if you're in a work setting or a fun setting and what you're trying to get out of it.
If you're trying to learn a system, I say go as deep as you can before your eyes catch on fire or you lose interest.
One of the two.
But if it's for work, my answer would probably be go as deep as you need to to get the task done and move off of it sort of thing, which is sometimes a bad answer.
Sometimes I feel like I'm a perennial beginner.
I'm always going just deep enough to get the task I'm doing done because I'm stressed about a deadline or whatever.
So I'm talking about work mostly.
And it does make me feel like there's some kind of impossible goal that I'm never reaching of actually knowing what I'm doing.
The memory that comes to mind is a colleague I had where we worked somewhere with a proprietary build system.
So this is great big pile of XML files that you used to build together all your C++ into a horrific, massive blob.
And there were all these different words you could put in your XML.
And I can never get motivated to learn a system like that, especially if it's proprietary.
And this colleague just took the time, like it irritated them enough that they took the time and figured the thing out and understood how it worked.
And then I just went to them with any question I had at any time and felt bad.
So I wish I had the ability to go deep enough that I don't have to constantly feel like a beginner.
I think it's important to go deep on those ones that interest you, especially.
And in work settings, I think it can be beneficial to go deep on ones that don't interest you, such as your colleague.
I imagine there was some sort of a work incentive, right? They're the person that knows that thing the best.
They get some recognition.
They have some longevity.
I don't know.
That can actually be a detriment to, though, because I like I've worked with people that and I would say I've even fallen victim to this myself.
But if you feel like you have to turn over everything and see how all the bits fit together.
How deep should your understanding of a system be? How deep should you go with it?
It depends on if you're in a work setting or a fun setting and what you're trying to get out of it.
If you're trying to learn a system, I say go as deep as you can before your eyes catch on fire or you lose interest.
One of the two.
But if it's for work, my answer would probably be go as deep as you need to to get the task done and move off of it sort of thing, which is sometimes a bad answer.
Sometimes I feel like I'm a perennial beginner.
I'm always going just deep enough to get the task I'm doing done because I'm stressed about a deadline or whatever.
So I'm talking about work mostly.
And it does make me feel like there's some kind of impossible goal that I'm never reaching of actually knowing what I'm doing.
The memory that comes to mind is a colleague I had where we worked somewhere with a proprietary build system.
So this is great big pile of XML files that you used to build together all your C++ into a horrific, massive blob.
And there were all these different words you could put in your XML.
And I can never get motivated to learn a system like that, especially if it's proprietary.
And this colleague just took the time, like it irritated them enough that they took the time and figured the thing out and understood how it worked.
And then I just went to them with any question I had at any time and felt bad.
So I wish I had the ability to go deep enough that I don't have to constantly feel like a beginner.
I think it's important to go deep on those ones that interest you, especially.
And in work settings, I think it can be beneficial to go deep on ones that don't interest you, such as your colleague.
I imagine there was some sort of a work incentive, right? They're the person that knows that thing the best.
They get some recognition.
They have some longevity.
I don't know.
That can actually be a detriment to, though, because I like I've worked with people that and I would say I've even fallen victim to this myself.
But if you feel like you have to turn over everything and see how all the bits fit together.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.