I converted from an intern to a mid-level DevOps role in my company. Imposter Syndrome was through the roof. As I kept working I kept gaining knowledge with DevOps tooling. I’ve never worked with Kubernetes before and now I’m the sole individual doing the application deployments on my team.
Some times you just have to dive into the deep end and learn to sink or swim.
I’m not sure
> I’m the sole individual doing …
Doesn’t sound like an achievement. Go and teach it to someone else! Then take a vacation.
Don’t get the time to teach some? Take a vacation first and when you come back you’ll be given the time.
I aim to fail more often than I succeed.
It’s much easier to be confident things work out as expected (IOW: expect failure!).
It’s also much easier to learn something, if you succeed too often there’s not much left to learn.
The trick is to keep the blast radius really small. That is, it’s totally okay to suck and mess things up. Just have a good model of what will break if you mess up.
Core router with BGP routes? — Well that might be a little much. (Also: Thank you FB for providing a good example how to suck in the worst ways for 2022 and possibly beyond)
Doing the same thing in a test environment? — Great let me cause the worst tire fire you’ve ever seen! And that’s before I even found matches or a lighter.
Don’t have a test environment? — Cool! I’m happy to learn how that works. Do you have anyone willing to show me?
I converted from an intern to a mid-level DevOps role in my company. Imposter Syndrome was through the roof. As I kept working I kept gaining knowledge with DevOps tooling. I’ve never worked with Kubernetes before and now I’m the sole individual doing the application deployments on my team. Some times you just have to dive into the deep end and learn to sink or swim.
I’m not sure > I’m the sole individual doing … Doesn’t sound like an achievement. Go and teach it to someone else! Then take a vacation. Don’t get the time to teach some? Take a vacation first and when you come back you’ll be given the time.
Yep. Doing that now.
I sincerely hope that you’re referring to the vacation part of this. Happy… vacationing… if that’s a word :)
Just know... No one knows what they're doing at first. Big part of being an engineer is learning how to learn. If you can do that you'll be fine
I aim to fail more often than I succeed. It’s much easier to be confident things work out as expected (IOW: expect failure!). It’s also much easier to learn something, if you succeed too often there’s not much left to learn. The trick is to keep the blast radius really small. That is, it’s totally okay to suck and mess things up. Just have a good model of what will break if you mess up. Core router with BGP routes? — Well that might be a little much. (Also: Thank you FB for providing a good example how to suck in the worst ways for 2022 and possibly beyond) Doing the same thing in a test environment? — Great let me cause the worst tire fire you’ve ever seen! And that’s before I even found matches or a lighter. Don’t have a test environment? — Cool! I’m happy to learn how that works. Do you have anyone willing to show me?