رونوشت 🔗
WEBVTT
00:00:00.080 --> 00:00:11.551
If a junior came to you and asking the questions you were asking your mentors now, is there a piece of advice you would give almost everyone and say, hey, start there.
00:00:12.080 --> 00:00:17.925
I would say the fact that you're reaching out is you're going to get an answer and you're going to be able to be successful.
00:00:17.925 --> 00:00:22.890
It's the people that don't reach out that are going to remain stuck and stay junior.
00:00:22.890 --> 00:00:26.910
So, just building your network and talking to people, because there's not going to be any.
00:00:26.910 --> 00:00:28.263
It's all contextual.
00:00:28.263 --> 00:00:34.542
It's all situational, but if you can find the right people that have been where you are, they'll help you through it.
00:00:34.542 --> 00:00:40.210
So reaching out is that key piece of advice is what I would give to the juniors.
00:00:40.759 --> 00:00:50.210
Hello and welcome to Developers Journey, the podcast bringing you the making of stories of successful software developers to help you on your upcoming journey.
00:00:50.210 --> 00:00:51.984
I'm your host, tim Bokenu.
00:00:51.984 --> 00:00:55.148
On this episode I receive Joshua Duffney.
00:00:55.148 --> 00:01:07.028
Josh is a senior cloud advocate of Microsoft, a former Microsoft MVP and XSRE site reliability engineer at Stack Overflow and a Pluralsight author, to name only a few.
00:01:07.028 --> 00:01:08.912
Fz books or e-books and stuff.
00:01:08.912 --> 00:01:11.379
I'm sure he's doing tons, josh.
00:01:11.379 --> 00:01:12.522
Welcome to have Journey.
00:01:12.522 --> 00:01:13.585
Thank you so much.
00:01:13.585 --> 00:01:16.132
Pleasure to be here and it's my pleasure to have you.
00:01:16.132 --> 00:01:20.388
It's been a long time in the making and I'm glad you're finally here Finally here.
00:01:20.388 --> 00:01:21.611
Thanks for the persistence.
00:01:21.611 --> 00:01:27.052
Before we come to your story, I want to thank the terrific listeners who support the show.
00:01:27.052 --> 00:01:31.028
Every month you are keeping the DevJourney lights up.
00:01:31.028 --> 00:01:46.527
If you would like to join this fine crew and help me spend more time on finding phenomenal guests than editing audio tracks, please go to our website devjourneyinfo and click on the support me on Patreon button.
00:01:47.159 --> 00:01:52.557
Even the smallest contributions are giant steps toward a sustainable DevJourney journey.
00:01:52.557 --> 00:01:56.865
Thank you, and now back to today's guest.
00:01:56.865 --> 00:02:03.507
So, josh, as you know, the show exists to help listeners understand what your story looked like and imagine how to shape their own future.
00:02:03.507 --> 00:02:06.608
So, as is usual on the show, let's go back to your beginnings.
00:02:06.608 --> 00:02:08.848
Where would you place the start of your DevJourney?
00:02:09.753 --> 00:02:10.800
The very, very beginning.
00:02:10.800 --> 00:02:27.092
Well, it's interesting that
Load full transcript
you say DevJourney, because I feel like the DevJourney for me is just beginning, because the first decade or so that I've been in the tech industry I've been in the operation side or like scripting, and so I've always kind of skated around development, so to speak, going deeper and deeper.
00:02:27.092 --> 00:02:30.609
But it all kind of started for me in high school with video games.
00:02:30.609 --> 00:02:41.372
So I was around like the early thousands when I was getting really into video games and starting to go into the PC gaming and needed to upgrade my graphics card.
00:02:41.372 --> 00:02:44.094
And so my grandma got me a graphics card for Christmas.
00:02:44.094 --> 00:02:51.429
But then I learned that there's different sockets and slots that you put video cards into, and so my computer didn't work for the video cards you got me.
00:02:51.429 --> 00:02:53.705
And so that's kind of where it all began.
00:02:53.705 --> 00:03:08.167
And then you know tinkering and taking apart computers and then eventually going into an associate's degree program for computer networking because it was the closest thing to like video game design that I could find at a local college.
00:03:09.340 --> 00:03:16.051
That's where it all began for me that must have been a rough wake up call when you realize that networking has nothing to do with gaming.
00:03:17.623 --> 00:03:19.207
A little bit, but it got me in the industry.
00:03:19.207 --> 00:03:21.906
It was either that or joined the military.
00:03:21.906 --> 00:03:41.149
And I just met my wife now then and so I felt like I had to make a choice, like I could go the military route and get a GI bill and eventually pay for video game design down the road, or I could go to the community college route, stay here and kind of pursue that path which eventually to starting a family and all that goodness.
00:03:41.149 --> 00:03:46.151
So that's kind of the choices I made and it was the closest thing and it's treated me well.
00:03:46.151 --> 00:03:48.808
I've gotten pretty far on that associate's degree.
00:03:49.581 --> 00:03:50.566
And I approve this message.
00:03:51.061 --> 00:03:51.562
Do you want to tell us?
00:03:51.602 --> 00:03:56.151
about how you do studies went and maybe compared to what you were expecting.
00:03:57.199 --> 00:03:58.806
Yeah, I had really no expectations.
00:03:58.806 --> 00:04:05.383
I really I could have gone to a four year university for game design, but I didn't want to start life Six figures of debt.
00:04:05.383 --> 00:04:14.472
You know, college in the US is really expensive and so I wanted to avoid that and had the community college, the computer networking degree.
00:04:14.472 --> 00:04:19.112
It was, it was said, computer networking, but it wasn't focused on that entirely.
00:04:19.112 --> 00:04:39.891
I mean, I had a semester about printers, a semester on shell scripting, semester on Linux, semester on virtualization of course, had some Cisco classes, had some C classes that I really did not do well at the time and so it was kind of like a general introduction to technology and computers in general.
00:04:39.891 --> 00:04:41.906
You know, I did have some networking concepts.
00:04:41.906 --> 00:04:54.612
I even got to wire the new dorm room so I had to run, you know, hundreds of, hundreds of feet of cable and so I just got exposed to everything really in that two year degree, you know, from layer zero all the way up to the application.
00:04:56.240 --> 00:05:02.252
You had pictured that in your mind as a first step in your studies, or would you expecting something else?
00:05:03.040 --> 00:05:03.060
I.
00:05:03.060 --> 00:05:21.689
All I knew was I wanted to do something in the technology sector because previously I had come and my summer job was a road crew, which I enjoyed, but it required a lot of travel, is a lot of manual labor, and I was just seeing like, as I get older this is going to be harder and harder to do, and I guess it was.
00:05:21.689 --> 00:05:27.406
It was pretty laid out from the syllabus and I had a good idea of what to expect because I knew what these things were.
00:05:27.406 --> 00:05:31.283
I just didn't understand how they worked, you know, and so it was.
00:05:31.283 --> 00:05:34.456
It matched up with my expectations and then it get.
00:05:34.456 --> 00:05:36.100
Basically, let me hit the ground running.
00:05:36.100 --> 00:05:41.420
When I went into the workforce to start on the help desk, let's talk about that how.
00:05:41.440 --> 00:05:44.166
how did you pick that field of operations?
00:05:44.166 --> 00:05:48.142
Or how did that field of operation pick you the help desk?
00:05:48.564 --> 00:06:02.170
Yeah, well, it was kind of like the entry level position that I could get with that degree, you know, aside from just trying to walk in as a network engineer or a network administrator, which is kind of what one of the teachers at the college campus did.
00:06:02.170 --> 00:06:09.096
He was a network administrator and managed all the way in connections and stuff like that was where there was T1 lines and stuff and all that.
00:06:09.096 --> 00:06:17.048
Where you'd have to bundle it to get beyond was a one and a half mag download and so, yeah, it was just I.
00:06:17.048 --> 00:06:25.660
My wife lived in, kind of lived with me for a little bit in college and it's a couple hours away from where she's from and where I'm from, and she wanted to move back home.
00:06:25.660 --> 00:06:35.444
And so I just started looking for jobs in the area and there was a little engineering firm that was looking for a help desk person, someone to upgrade everybody's computer from XP to Windows seven.
00:06:35.444 --> 00:06:47.927
And I, I fit the bill, you know, and figured that out and kind of ran the help desk there and installed software and troubleshots stuff and all that, all that good good thing, all those good things that you do on the help desk.
00:06:47.927 --> 00:06:54.228
But I learned, learned a
lot, mainly a lot of people skills, so that was a valuable trait that I picked up.
00:06:54.288 --> 00:06:57.007
Communicating my favorite, my favorite story, I got to share this one.
00:06:57.007 --> 00:07:08.348
There was an executive that was super mad at me because I went into his office work on his computer over lunch and so I, you know not to disturb his working hours.
00:07:08.348 --> 00:07:26.589
And so then I went in and I replaced everything, upgraded his computer, put a new keyboard and mouse on there and I got called into his office not even 15 minutes after he got back and he's like if you're going to have the audacity to come in here and mess with my computer, you should at least plug back in my mouse and keyboard so I can work.
00:07:26.589 --> 00:07:32.778
Lo and behold, I had replaced his mouse and keyboard with wireless Nice keyboard.
00:07:33.081 --> 00:07:36.096
And I was like oh, I don't know what you mean.
00:07:36.096 --> 00:07:40.089
I say I've got batteries in them, they're powered on, like I made sure all those things work.
00:07:40.089 --> 00:07:44.112
I had literally a paper checklist I had to go through to leave your office.
00:07:44.112 --> 00:07:45.404
I was like it all works.
00:07:45.404 --> 00:07:48.569
And he didn't say anything to me after I shook the mouse and it worked.
00:07:48.569 --> 00:07:50.367
He just said I could leave.
00:07:50.367 --> 00:07:52.367
I mean no apology, nothing.
00:07:54.302 --> 00:07:58.492
Yeah, I guess I would be speechless as well, yeah.
00:07:59.422 --> 00:08:01.067
What is this magic Exactly?
00:08:02.341 --> 00:08:09.103
Do you have other example of people skills, besides being able to deal with executives that have no idea what you just did.
00:08:10.079 --> 00:08:29.812
Well, a lot of it was just, um, just realizing how much that you could know so quickly in the industry, like there's these people that have a really, really smart had their electrical and mechanical engineers, but I could quickly learn more than them about these particular things that they depended on Just because of my focus on technology.
00:08:29.865 --> 00:08:43.830
It's so I really loved that that fact that the there was so much to learn in technology that even me with less than a year would know so much more than these people that have been kind of in this field or in an adjacent field, dependent on this for decades.
00:08:44.865 --> 00:09:20.634
And so a lot of the the people skills I learned was just to communicate without that kind of Talking, that demeanor like talking down to people, and so learning to communicate things and to teach things is kind of I stumbled upon Very quickly in technology one of the kind of the passions or areas that I really enjoy, which is the teaching aspect of it, and so, yeah, just being able to communicate with people about technology was probably the bigger skill that I learned in that role, and Calming people down when they're getting emotional about you know their spreadsheet doesn't do this or that, or you know Outlook isn't doing this or that, like it's just.
00:09:20.634 --> 00:09:26.384
It's a, it's a program following a procedure, and once you understand a procedure then you can understand how to make it work.
00:09:26.384 --> 00:09:28.489
But doesn't mean that it's not complicated.
00:09:28.809 --> 00:09:31.134
Yeah, that is very true, that is very true.
00:09:31.134 --> 00:09:45.177
The oldest positions, actually, where you're in Mendated to help people when something is not working, those are all really learning pressure cookers.
00:09:45.177 --> 00:09:45.547
Really.
00:09:45.547 --> 00:09:53.677
People come at you, they are mad already they have a problem that cannot solve and and it's timely, and it's painful, etc.
00:09:53.677 --> 00:09:55.345
And so you have to be thinking on your feet.
00:09:55.345 --> 00:09:57.253
You have to understand the whole system.
00:09:57.253 --> 00:10:01.644
You have to understand what they're telling you and what they're not telling you, because you just don't know about it.
00:10:01.644 --> 00:10:15.570
And I've had my fair share of of after-sales support now in a Tech store, and that was that, was this, again and again and again, people coming in and screaming and this is whoa, I really learned a lot.
00:10:15.570 --> 00:10:16.192
I agree with that.
00:10:16.192 --> 00:10:17.034
It's very interesting.
00:10:17.034 --> 00:10:19.850
So how did you go from there?
00:10:19.850 --> 00:10:26.332
Because I've heard you code a bit, so, oh, at least you did coding stuff after that.
00:10:26.332 --> 00:10:26.835
So how?
00:10:26.875 --> 00:10:29.623
yeah, yeah yeah, so the story there is.
00:10:29.623 --> 00:11:03.658
I was helped Desk, worked there for a couple years and then I became kind of like a one-man shop, like a network administrator was the title, but I was really just like the sys admin for a small bank and so I was rack and servers, like figuring out the storage capacity, like for the backups you know, and installing battery backups for this little bank and data center, rewiring everything, upgrading the access points, and then I started working on virtualization at that point so net app Was the solution that they chose there and we were placing all the like the teller terminals with these little wise devices.
00:11:03.658 --> 00:11:06.654
So instead of hardware computers there are these wise devices.
00:11:06.654 --> 00:11:10.265
And that's where I I just got exposed to like everything I was.
00:11:10.265 --> 00:11:37.672
I was responsible in the primary on call for this little bank and all these operations and keeping the way and links connected and all that stuff and and I learned a ton and I was only there probably about a year until I got this opportunity to join, to get a pretty big pay raise and join the service desk for a really large enterprise and that's where the kind of the coding journey started and the ticket that kind of Pushed me down that path
was we got was.
00:11:38.254 --> 00:11:52.705
I worked for this really large construction company and what they would do is they'd spin up and they'd spend down construction sites and they'd hire what they would call craft workers, you know contractors, and but they would have to provision them all these accounts and stuff to log in time and whatever.
00:11:52.705 --> 00:12:06.514
And so we would pretty often we get these tickets that you know this job site spun, spun down, we needed to disable these 300 or 500 people and doing Is we had a service desk of about 60 people.
00:12:06.514 --> 00:12:20.551
They just divvy up this Excel spreadsheet and say you right-click, disable 25 and you disable 25, and so you know, by the end of the day, you know we had three chefs or whatever of people it would get done.
00:12:20.551 --> 00:12:29.683
And there was this guy His name was Rob that worked with me on the tier two help desk and we kind of looked at each other and we're like I think there's a better way.
00:12:29.683 --> 00:12:32.190
I I think we could do this quick.
00:12:32.650 --> 00:12:52.131
The monotony of it was getting us, we're getting bored, we're getting a little stir crazy, right click disabling these hundreds of lists, and so we could some of them upon PowerShell, powershell I just kind of taken root in the Windows ecosystem and it had a really good support for Active Directory and Exchange and those are the two primary things that we administered.
00:12:52.131 --> 00:13:06.697
And the first time we did that we got that list of 300 and seconds later it was all disabled and our bosses were just stunned and blown away and magic, you know like, oh, we needed, we would have had.
00:13:06.697 --> 00:13:10.215
You know, I need a team of developers to be able to figure this out is what they said.
00:13:10.215 --> 00:13:11.027
And so we quickly.
00:13:11.447 --> 00:13:23.119
I was in my younger, my early 20s at the time, so I got the title of a script kid, so from that point on I kind of anything that had any kind of volume behind it.
00:13:23.119 --> 00:13:44.745
It was an opportunity for me to exercise some more scripting skills and eventually that got me hired, taken out of the service desk and hired as a systems engineer working on SCCM, so system center configuration manager, and I worked to automate a bunch of software installs and Windows updates and imaging, which kind of ties back to the help desk job, you know.
00:13:44.745 --> 00:13:47.192
But now fast forward to Windows 8.1.
00:13:47.693 --> 00:13:48.255
You know that was.
00:13:48.255 --> 00:13:51.649
That was the OS Windows 8.1.
00:13:51.649 --> 00:13:53.039
Oh, that was a nasty one.
00:13:53.503 --> 00:13:57.278
Yeah, not as bad as Vista, but definitely not fun.
00:13:57.578 --> 00:14:05.120
That was the surface and everybody wanted the surface and those were a nightmare to try to image, if memory serves.
00:14:05.120 --> 00:14:07.368
But that's kind of where the coding started.
00:14:07.368 --> 00:14:29.245
And then I got kind of hopped on the DevOps bandwagon and got roped into infrastructure as code and learning a lot of software engineering principles, but in the lens of operations and through infrastructure the kind of all the DevOps I read like the Phoenix project and got on that bandwagon, started following a lot of influential people in the community that were starting that up, just humble being one.
00:14:29.245 --> 00:14:31.028
And then what's his name?
00:14:31.028 --> 00:14:33.052
Gene Cam.
00:14:33.052 --> 00:15:07.908
And so that was kind of my first kind of introduction into software engineering and those disciplines, was trying to apply them and mature the process of managing infrastructure and that eventually I was a DevOps engineer and tech lead for a payroll company for about four years and then I got the opportunity to join Stack, overflows and SRE, which you know they're at kind of like the top of the industry for the practices that are led by Thomas Limoncelli, who was a sysadmin at Google for many years and he's now been at Stack for a long time.
00:15:07.908 --> 00:15:16.596
But they've got a really, really good you know ship, so to speak, and it was just an honor to be among them for the short time that I was.
00:15:16.865 --> 00:15:30.779
And then I kind of hit that pivotal point, I guess, where I was like, okay, well, I've kind of got to the top of this particular field that I'm super, was super interested in profession and kind of.
00:15:30.779 --> 00:15:41.287
I took a leap of faith and joined Microsoft as a technical writer because I had just released a book in this time and so I'm skipping a bunch of stuff we can dive deeper into.
00:15:41.287 --> 00:15:52.966
But I in hindsight overpivoted into that role, because something that you do for the side that you have a passion for doesn't always make a good full time job.
00:15:52.966 --> 00:16:01.369
And so I quickly realized that and I started to miss the sense of mastery that I previously had in my other discipline.
00:16:01.369 --> 00:16:05.326
And so since then I've been trying to repivot, so to speak.
00:16:05.326 --> 00:16:10.586
Right now I'm currently as a I'm a cloud advocate, so I'm not necessarily fully content.
00:16:10.586 --> 00:16:20.087
I'm in the middle where I get to sit between the customers and the product and both be the storyteller and teacher, but also an engineer, and so that's been a good balance for me currently.
00:16:20.148 --> 00:16:46.039
But yeah, ever since I left stack I guess I've been kind of like trying to course correct a little bit since an overpivot, but what's been humbling and honoring and people like realizing that jump of people that have followed me online and stuff and I get these conversations sometimes they really admire the ability to kind of rebase right, like rebase your skill set, which is super hard.
00:16:46.039 --> 00:16:50.495
A lot of people they get really good at one thing and they have
that sense of mastery and I get it.
00:16:50.495 --> 00:16:52.571
You don't want to let it go because it's so rewarding.
00:16:52.571 --> 00:16:57.269
But this, this field, demands that you constantly develop your skill set.
00:16:57.269 --> 00:17:03.969
My only caveat I think in hindsight that I would do a little bit differently is make smaller pivots.
00:17:03.969 --> 00:17:09.739
That's such huge, drastic changes but it is indeed.
00:17:10.005 --> 00:17:14.539
It is indeed and I want to know the choice of word we say rebase your skills.
00:17:14.539 --> 00:17:28.513
That's the, the, the expert probably talking when you, when you say you over pivoted and you miss the mastery, can you, can you explain a bit more what you mean?
00:17:28.513 --> 00:17:33.753
Yeah, so I was moving from yeah, absolutely so.
00:17:33.814 --> 00:17:38.335
I, to give the full context, I was, you know, a site reliability engineer at Stack Overflow.
00:17:38.335 --> 00:17:41.509
I had been working seven years to get into that position.
00:17:41.509 --> 00:17:50.548
I had applied many times, never got in, and then it finally got in and I had a number of friends and colleagues that already worked there that I knew from different communities and so I was well connected.
00:17:50.548 --> 00:17:53.497
But I just had such a sense of mastery.
00:17:53.497 --> 00:17:54.394
I knew everything that I was.
00:17:54.394 --> 00:18:00.211
I was still challenged and the team was still moving and progressing and bettering the organization.
00:18:00.211 --> 00:18:08.594
But if in like the dev ops space and is from a company and culture stack overflow is, you don't have to like sell dev ops to stack overflow.
00:18:08.594 --> 00:18:14.432
They understand it, they embrace it, and so for a long time I had to fight, fight that in organizations.
00:18:14.432 --> 00:18:32.261
But what I mean by over pivot was I was moving from this discipline of dealing with infrastructure as code and dev ops and a lot of that stuff and Over into technical writing, and so the difference in the daily level is I'm no longer responsible for maintaining Production systems.
00:18:32.261 --> 00:18:51.747
I'm now writing very technical, detailed, technical documentation that explains the things of my previous domain, like terraform and ansible, and writing that and so is a totally different skill set to be able to see, without even talking to the audience, like what, like, what is this library want?
00:18:51.747 --> 00:18:54.250
There's a lot of information architecture that goes into that.
00:18:54.250 --> 00:19:06.294
There's obviously the editing, a little bit of storytelling that you need to have in there, and then the real world experience was kind of like the edge that I had on other people that had technical writing as their discipline.
00:19:06.314 --> 00:19:17.583
For many years I had, I'd lived in these tools and I knew some of the rough edges, but what that left me with was having to create All these different scenarios for myself.
00:19:18.124 --> 00:19:37.627
No longer was I constantly hit in the face by the problems of production, and now I had to create all the problems myself, and the main thing that I lack there was just the that keeps your skills so sharp constantly having problems presented to you and having to solve them.
00:19:37.627 --> 00:19:42.894
Just like the help desk, you get a, get a call, you get a sit down and like outlooks not working, that's the only directive you get.
00:19:42.894 --> 00:19:44.236
You gotta figure it out.
00:19:44.236 --> 00:19:51.709
On the other side, with the technical writing, there's no one calling you, there's no problems hitting you in the face.
00:19:51.709 --> 00:19:59.823
You've gotta go and seek them out and try to understand them, and so the biggest challenge there was just Having a faith in my decision.
00:19:59.823 --> 00:20:06.190
For the problems I was selecting, there was no one telling me that they're good or bad, or useful or not useful.
00:20:06.190 --> 00:20:07.111
You know, you don't have.
00:20:07.111 --> 00:20:11.236
You don't get that feedback till the end, just like an author doesn't get that feedback till the end of their book.
00:20:11.236 --> 00:20:11.635
You know.
00:20:13.102 --> 00:20:18.067
I see, I see it probably also do the problem of of if you have a blind spot.
00:20:18.067 --> 00:20:22.051
You didn't see a category of problems that could happen.
00:20:22.051 --> 00:20:23.213
You just don't see them.
00:20:23.213 --> 00:20:28.903
They're not gonna hit you in the face and so, unless somebody tells you gonna see, not gonna see it.
00:20:28.903 --> 00:20:34.710
Yeah, how was it in terms of of reward cycles?
00:20:34.710 --> 00:20:40.615
I mean, when you solve problems day in, day out, you get your kick off problem solving.
00:20:40.615 --> 00:20:49.734
When you have to make your own problems and you're writing stuff, I guess the time that would be way longer and the rewards way less often.
00:20:50.480 --> 00:20:59.053
Yeah, yeah, your feedback loop is way, it's a long tail, right, and that was actually the biggest thing that I miss was the problem solving in the reward cycle of that.
00:20:59.053 --> 00:21:05.226
You know that constant feedback you get from programming or solving those challenging problems.
00:21:05.226 --> 00:21:13.743
Yeah, for the content, I mean it would be take me two weeks to write an article and then I would release it and then I get some feedback.
00:21:13.743 --> 00:21:19.972
And then, you know, doctor, it's learn now has good domain authority, so the sc always pretty decent.
00:21:19.972 --> 00:21:26.105
I can get ranked on google, but there's the most people like they won't leave feedback on there.
00:21:26.105 --> 00:21:35.163
The verbatim is always kind of the negative stuff and so, yeah, you don't really get the same feedback that you normally would you like?
00:21:35.163 --> 00:21:40.632
It's funny now that it's been two years since
I've done that, I'll get a comment like, hey, this was a helpful article.
00:21:40.632 --> 00:21:47.391
So there's an example Like two years after I wrote it did I get a single piece of feedback on it?
00:21:47.391 --> 00:21:48.073
You know.
00:21:49.560 --> 00:21:50.041
But I'm.
00:21:50.041 --> 00:21:50.622
Then.
00:21:50.622 --> 00:21:57.290
Why did you decide to I wouldn't say double down, because you pivoted again a little bit of pivoted back, as you said.
00:21:57.290 --> 00:22:03.868
Why didn't you say, hey, screw that, I'm coming, I'm going back, and but decided to try something else still?
00:22:05.101 --> 00:22:06.201
That's a really good question.
00:22:06.201 --> 00:22:09.826
I don't know if I made that consciously, part of it was just opportunity.
00:22:09.826 --> 00:22:17.296
So I kind of realize like, hey, I enjoy the technical writing, but it's not somewhere I want to stay for a long, like a long, long time.
00:22:17.296 --> 00:22:20.685
You know, I've kind of learns a lot of good skills.
00:22:20.685 --> 00:22:26.522
My writing skills obviously improved with 18 months of just Always writing a little backstory.
00:22:26.522 --> 00:22:35.054
I was writing a nonfiction book at that same time as becoming a full time technical writer, so I was just like reps and reps and reps with writing.
00:22:35.054 --> 00:22:36.635
So my communications gotten a lot better.
00:22:36.635 --> 00:22:38.883
But yeah, it was more.
00:22:38.923 --> 00:22:46.595
So just the opportunity came up to join a team with someone that I've looked up to in the industry for a long time is named seed morowski.
00:22:46.595 --> 00:22:54.594
He had a spot open and I just somehow stumbled upon it to the job site and I was like I'd be really cool to work with him.
00:22:54.594 --> 00:23:00.026
You know, it's kind of like in the middle of the two things that I used to do or what I'm currently doing, what I used to do.
00:23:00.026 --> 00:23:01.627
So maybe I'll just give it a try.
00:23:01.627 --> 00:23:14.010
It's just kind of an opportunity that I saw it and it's the funny thing is is I was, I think four hours shy of meeting the cut off for the hiring pause.
00:23:14.010 --> 00:23:16.134
That happened couple years ago.
00:23:16.134 --> 00:23:23.232
Wow, like had I waited to sign the offer just a couple more hours, I wouldn't have the current role I'm in.
00:23:24.961 --> 00:23:40.346
Wow, okay, so that means, just before cool, be the gorgeous when could it or something I was kind of afterwards, yeah when the economy really hit in twenty, twenty two, twenty three, yeah, okay yeah, yeah, that's that one for sure.
00:23:41.028 --> 00:23:41.847
Okay, I'm.
00:23:41.847 --> 00:23:48.915
Do you still miss this, this feedback loop, or did you manage to create your own now, in this new position?
00:23:49.960 --> 00:23:51.082
I do still miss it.
00:23:51.082 --> 00:23:52.605
I've got variants of it.
00:23:52.605 --> 00:23:53.906
Depends on the project I'm on.
00:23:53.906 --> 00:24:01.605
But I'm also starting to realize, listening to some of your other episodes actually, that this is kind of the world of the senior role is.
00:24:01.605 --> 00:24:17.130
Things are so much more ambiguous, you know, and there are things are more long tail, just like a mentoring is a long tail thing, and I'm realizing that I'm probably just gonna have to get used to that ambiguity a little bit, you know.
00:24:21.765 --> 00:24:44.996
Maybe I've seen those deep technical roles where you actually say, no, I'm not gonna go this direction, I'm going back to the I know staff, senior staff, principal route and really going very deep as as an expertise in what I'm doing, and then I guess you can still keep that part of the of the feedback to be intact.
00:24:44.996 --> 00:24:59.817
But as soon as you want to multiply bb a force multiplier and really try to to multiply your effort by mentoring, networking, helping others, I guess that's the price you have to pay.
00:25:00.401 --> 00:25:01.102
Yeah I guess I'll.
00:25:01.102 --> 00:25:02.503
Yeah, that's that's kind of.
00:25:02.503 --> 00:25:10.383
You talked about the fog of the words beginning, beginning of the episode before start recording and when you feel lost.
00:25:10.383 --> 00:25:13.669
That feeling I definitely definitely feel that way.
00:25:13.669 --> 00:25:23.413
I feel kind of like right at the cusp of that being lost and just trying to find, like, do I double down and find an area where I want to be super technical or do I kind of embrace this?
00:25:23.413 --> 00:25:25.582
Am you a little bit more?
00:25:25.582 --> 00:25:36.064
Is this the best way to just uncertainty right and try to look for ways to drive more clarity and have broader impact, you know, and to have some faith behind that?
00:25:36.064 --> 00:25:45.631
And that requires that you learn more in your network so that way you can bet out those blind spots and All that good stuff, which are all skills that I have yet to really hone.
00:25:46.701 --> 00:25:48.546
Do you mind loving a bit more in this?
00:25:48.546 --> 00:25:50.549
You're facing this problem right now.
00:25:50.549 --> 00:25:51.853
What do you do?
00:25:51.853 --> 00:26:02.113
I'm explicitly to try to get out of it, or understand it more, or or cut some branches that you might realize are not the good one.
00:26:02.113 --> 00:26:03.013
How do you?
00:26:03.013 --> 00:26:03.976
Do you go at it, right?
00:26:03.996 --> 00:26:04.076
now.
00:26:04.076 --> 00:26:08.386
Right now, it's been when it gets too much to handle.
00:26:08.386 --> 00:26:12.973
What I typically do is reduce scope and I try to find some kind of problem that has a finish line.
00:26:12.973 --> 00:26:41.372
So I just did like a little deep dive into how containers work and made that like a little learning sprint and I found a way to make some, you know, content, did some live streams, and that's an example of where the ambiguity and the uncertainties just like it's too much, it's too
restless for me that I need to have some kind of finite outcome, and so I'll kind of like zoom in for a sprint, like a one to two week period, on something like that, and I'm kind of coming out of that phase where I know I need to deal with this.
00:26:41.372 --> 00:26:49.288
But one thing that I'm just recently learned is that I can't think my way out of it.
00:26:49.288 --> 00:27:10.906
I have to talk my way out of it, and so now what I'm doing is I'm starting to set up meetings with my lead and with other Product group leaders in the space I'm in to get a better idea, like, okay, I have these vague notions of important work, but I need I need more data points, and those data points can't just be conjured from my imagination.
00:27:10.906 --> 00:27:14.471
I need to have real data points from different people.
00:27:14.653 --> 00:27:23.867
Really good advice that I got from a colleague was Find the problems that the people at your level or above Find important but don't have time to do.
00:27:23.867 --> 00:27:29.041
Then you know that you're always working towards something that has impact, because you don't have to sell them on.
00:27:29.041 --> 00:27:30.492
They see the value.
00:27:30.492 --> 00:27:32.157
You don't have to sell them on that.
00:27:32.278 --> 00:27:46.936
But if you go and start your own little thing You're gonna have to create, unless you really believe in it and you really see the vision, you're gonna have a uphill battle convincing people that they should even care that your problem is is worthy of solving.
00:27:46.936 --> 00:27:54.275
You can go and solve it and they're gonna say, okay, cool, but if you go and solve something that they already are experiencing as pain, you don't have to sell them on that.
00:27:54.275 --> 00:28:09.582
And so that's where I'm currently at right now is is trying to Find the right people to have these conversations with so that way I can more accurately Articulate the problems that I'm working on and then go back into that scoping thing that I talked about.
00:28:09.582 --> 00:28:16.262
Or okay, here's this broader chunk of a problem, here's what I can get done and show some visible progress on.
00:28:16.262 --> 00:28:23.162
And you know the next quarter or whatever it is, and then break that down further, I love it.
00:28:23.482 --> 00:28:23.782
I love it.
00:28:23.782 --> 00:28:26.394
How would that discussion go?
00:28:26.394 --> 00:28:35.321
Would you go towards some of your senior peers and then and say, hey, I have the feeling you're working on this and you're working on that and you have those problems.
00:28:35.321 --> 00:28:37.233
This is by interesting right now.
00:28:37.233 --> 00:28:38.155
Is it accurate?
00:28:38.155 --> 00:28:40.402
Can you describe it a bit more, etc.
00:28:40.402 --> 00:28:43.398
Oh, would you go at it completely differently?
00:28:44.433 --> 00:28:45.258
I'll be on my first stop.
00:28:45.258 --> 00:28:58.538
I have a really good team lead was the gentleman
that I mentioned earlier, and so he's he's got a really good luck, he's got a good leadership capacity and so he does have a good, like broad View of the different organizations, things that are coming in.
00:28:58.538 --> 00:29:07.990
And so typically what I'll do is I'll try to find someone like that, someone that's just has a broader view than I do, like I'm too down in the weeds here or I'm just not seeing things.
00:29:07.990 --> 00:29:17.051
I don't have the same network, and so I like to try to peer into their minds, so to speak, to get that a broader, detached view, kind of landscape.
00:29:17.051 --> 00:29:22.943
Like are there some things coming down the pipeline that are important, or should I stay in my lane here and double down and keep focusing?
00:29:22.943 --> 00:29:31.809
And so my first stop is usually to that person and say, hey, it's usually in the form of a career check-in, like I'm a little bit lost right now.
00:29:31.809 --> 00:29:33.596
I'm usually super honest.
00:29:33.596 --> 00:29:35.964
Like I'm lost, I don't exactly, don't I'm doing.
00:29:35.964 --> 00:29:42.799
It doesn't feel like I'm having any impact, I feel like I keep wasting my time, learned a bunch of stuff that really doesn't do a whole lot.
00:29:43.990 --> 00:29:46.397
Like you, where do you think I should invest my efforts.
00:29:46.397 --> 00:29:56.853
You know, like what are your two or three little areas that you've got like future state, current state, and then Kind of like the present.
00:29:56.853 --> 00:30:11.042
You know, like the the now, next future type things, and usually there's a technology kind of bracketed in there, like maybe wazzy and web assembly type stuff is the future stuff that I should be have on my radar and be tinkering with.
00:30:11.042 --> 00:30:14.721
But you know, don't make it a big boulder just yet, like there's not enough there.
00:30:14.721 --> 00:30:19.401
And so that's typically what will come out of those conversations some clarity.
00:30:19.401 --> 00:30:25.192
And then Usually I move on to people that are more Focused.
00:30:25.192 --> 00:30:28.340
So then they, they send me on, it's like kind of like a quest.
00:30:28.340 --> 00:30:35.201
You know these the video game analogy, like here's the entry point and then then here's they, just they're a pointer to the town's person.
00:30:35.201 --> 00:30:40.882
That's actually got you know the monster or whatever in the dungeon that you need to go and slay.
00:30:41.202 --> 00:30:43.376
But and the monster is web assembly.
00:30:43.376 --> 00:31:00.056
Okay, so really going broad, finding new contacts to go deep with, understand if it's something for you, if there is something at all, if it's something you could really rock on for a while, and if so, double down.
00:31:00.056 --> 00:31:06.756
If not, come back up, find that person again or a different person to go broad again and and find where to go deep again.
00:31:08.432 --> 00:31:09.896
Yeah, sounds like a plan.
00:31:13.250 --> 00:31:13.613
Have you?
00:31:13.613 --> 00:31:18.292
So we've been talking a bit about, about Gaming again and again.
00:31:18.292 --> 00:31:20.538
That was the beginning of the discussion.
00:31:20.538 --> 00:31:22.942
Have you thought of going back to that?
00:31:24.092 --> 00:31:27.875
You know only recently what really sparked it.
00:31:27.875 --> 00:31:30.761
I kind of just left it as it was because I had had.
00:31:30.761 --> 00:31:31.604
I had.
00:31:31.604 --> 00:31:43.771
Coding is as close to video gaming as I've gotten, as far as like a flow state, like being able to code and create things, whether it be a script that just copies files around or Whatever else.
00:31:43.771 --> 00:31:46.538
But I've never dived into application development.
00:31:46.538 --> 00:31:50.018
It's just been a domain that I've For whatever seems like.
00:31:50.018 --> 00:31:51.990
Maybe it's forbidden fruit in my mind, I have no idea.
00:31:51.990 --> 00:31:59.059
But very recently I've got more application where I'm Teaching my son math and I saw this thing on Twitter.
00:31:59.059 --> 00:32:06.999
It's this game developer who created this little video game for a son to do just basic arithmetic, you know, and I was like that would be.
00:32:06.999 --> 00:32:13.239
That would have been the best way for me to learn as a kid, and so there's been interest in there, but I've never revisited it.
00:32:13.239 --> 00:32:16.674
Perhaps it's time I might find a new Passion in that.
00:32:16.674 --> 00:32:19.170
But yeah, that's a really good question.
00:32:20.292 --> 00:32:30.862
You know, and you haven't been tempted to go toward your, I want to say, I don't want to say first mastery, but the mastery of, of DevOps and infrastructure, etc.
00:32:30.862 --> 00:32:32.203
In the gaming industry.
00:32:34.011 --> 00:32:34.795
No, not really.
00:32:34.795 --> 00:32:36.332
That would be.
00:32:36.332 --> 00:32:37.536
That would be a good parallel.
00:32:37.536 --> 00:32:42.299
I had a couple people that made that jump the company where I learned a lot of this stuff.
00:32:42.299 --> 00:32:44.075
One person left.
00:32:44.075 --> 00:32:47.809
He was a sysadmin and worked with me pretty closely, or my team.
00:32:47.809 --> 00:32:57.324
I was a tech lead for the DevOps team, and so we we had to basically connect with all the like the DBA team and very fractured, siloed, typical organization, right.
00:32:57.324 --> 00:33:02.730
But he went to Blizzard, which is now owned by Microsoft, but so I was jealous of that.
00:33:02.730 --> 00:33:08.002
I've had rockstar games reach out to me in the past, but the relocating was always a no-go for me.
00:33:09.413 --> 00:33:11.289
Yeah, maybe it has changed, maybe not.
00:33:11.289 --> 00:33:16.583
Well, maybe the industry sucks, but that's, that's a different.
00:33:16.583 --> 00:33:19.740
Do you see yourself?
00:33:19.740 --> 00:33:31.836
Continuing this direction of mixing is different the technical writing, the
community, building the expertise that you have and continuing mixing those.
00:33:31.836 --> 00:33:37.530
Or are you going to face a pivot again soon and say, hey, I need something else?
00:33:39.847 --> 00:33:47.797
That's the thing that's been in the back of my mind for a little while, which is do you disappear?
00:33:48.346 --> 00:34:04.073
There is something that is kind of appealing to that, where you can just disappear into the ether of development for a little while, because I've been in the public eye for a little bit since my PowerShell days, but I do enjoy the teaching.
00:34:04.133 --> 00:34:15.333
I think I'll have it to a blend at some point, but I would like the ratio to be more engineering, like more of the deep work, more of the engineering, the quiet heads down type problem solving.
00:34:16.445 --> 00:34:26.338
So my next pivot, if anything, would be if I can change my current role to have more of that time or a role that has more of that built in.
00:34:26.338 --> 00:34:35.072
But still, I think I would always had a really good question posed to me when I was trying to iron this out, which was what makes you think you're so unhappy when your current role?
00:34:35.072 --> 00:34:41.932
Because it seems like you get to do all the things that you like to do under the role and it just takes a while to admit or to realize that you can.
00:34:41.932 --> 00:34:47.855
That's kind of the weird thing with autonomy is to realize the freedom that you have in it.
00:34:47.855 --> 00:35:07.117
But I did come to the realization that, yeah, I think even if I was full-time engineering, I would probably still teach to a degree Like I enjoy it too much to let it completely go, yeah, but I'd probably pivot a little bit more to more engineering in the future.
00:35:08.186 --> 00:35:09.349
Two questions on my mind.
00:35:09.349 --> 00:35:11.295
Which nasty one should I pick?
00:35:11.295 --> 00:35:12.630
Yeah, I'd pick that one.
00:35:12.630 --> 00:35:14.626
What would be?
00:35:14.626 --> 00:35:15.889
How did you put it?
00:35:15.889 --> 00:35:19.418
An overpivot in this regard?
00:35:20.547 --> 00:35:37.074
An overpivot would probably be to try to force my way into a software engineering role inside the Big Tech, which has got a lot of gates, you know, with the engineering role, with coding, interviews and stuff, and try to stress this is something that I've done in the past, a very familiar territory.
00:35:37.074 --> 00:36:00.434
So if I were to overdo it this is exactly what it would look like is I would buy and it's not like I already did this, but I would buy a whole bunch of software engineering books and then I would force myself to do lead code for like two to three hours a day for six months and force my way into a software engineering role, not give any thought to what that role would do or if I would enjoy the coding that I was doing in that role.
00:36:00.434 --> 00:36:04.275
That would be kind of an example of an overpivot in this scenario.
00:36:05.806 --> 00:36:07.010
Makes a lot of sense.
00:36:07.010 --> 00:36:11.311
I don't want to say being there, I don't know, but rings a bell.
00:36:11.311 --> 00:36:16.273
You mentioned teaching quite a bit.
00:36:16.273 --> 00:36:20.891
You, I know you've written technical books.
00:36:20.891 --> 00:36:25.239
You have created many courses on Perl site.
00:36:25.239 --> 00:36:28.333
Do you know in-person teaching as well?
00:36:29.646 --> 00:36:32.213
I used to do in-person teaching, more so when I worked.
00:36:32.213 --> 00:36:42.445
Well, I do some of it for work now when I speak at conferences or do workshops or like user groups, but I did a lot more when I worked in an office and I would do a lot of like lunch and learn type stuff.
00:36:42.445 --> 00:36:46.356
So I've done some in-person, but more of the in-person has been informal.
00:36:46.356 --> 00:36:50.414
Most of my instruction stuff has been online and virtual.
00:36:51.485 --> 00:36:56.278
Okay, how did you, because you've been at it for a while, how did you deal with this?
00:36:56.278 --> 00:37:15.277
Mostly going online, mostly not seeing people interact with your content, mostly being asynchronous and getting the feedback, if at all, later and not while they're experiencing it, not being able to piggyback on sparkling eyes and saying, hey, they start to get it.
00:37:15.277 --> 00:37:20.003
Or seeing faces make grimaces and say, well, something is not right.
00:37:20.003 --> 00:37:23.534
I've got to jump in and add a new example to this.
00:37:23.534 --> 00:37:33.211
I assume you had this experience before and then, slowly, with the technical writing and the video and such it, transitioned to this different kind.
00:37:33.211 --> 00:37:35.197
Can you speak with that a bit?
00:37:35.197 --> 00:37:36.005
Yeah?
00:37:36.065 --> 00:37:42.842
So the teaching, it was a kind of a natural extension because it's all I knew.
00:37:42.842 --> 00:37:48.425
To be honest, like I had done my very first, we'll go all the way back.
00:37:48.425 --> 00:37:49.967
So that help desk job that I had.
00:37:49.967 --> 00:37:57.971
My second project was to implement a help desk system and there was a free one called Spiceworks.
00:37:57.971 --> 00:37:59.994
So Spiceworks is still out there.
00:37:59.994 --> 00:38:03.983
I actually interviewed for them and almost moved to Austin.
00:38:03.983 --> 00:38:08.652
So I was almost a Texan but I decided to stay here for my wife's families here.
00:38:09.940 --> 00:38:20.985
But anyway, in that they have this awesome community feature where it's just a community of everybody uses the product or, you know, you don't have to use the product to have the software or to have part of the community, just log in.
00:38:20.985 --> 00:38:23.963
It's this form, you know, like the old school forms.
00:38:23.963 --> 00:38:33.807
And I started to become kind of a lurker on there really early on because I didn't mind, my boss at the time Worked part time so he
was only there a couple days of the week.
00:38:33.807 --> 00:38:38.947
He was a firefighter as well as this like network administrator, saw a lot of time.
00:38:38.947 --> 00:38:45.460
I was just on my own to figure stuff out and I heavily relied on the community, ask questions, found a lot of stuff that you know.
00:38:45.460 --> 00:38:48.489
Some more people had problems with, and then I started to.
00:38:48.489 --> 00:38:51.146
I have a feeling I need to give back.
00:38:51.146 --> 00:38:58.630
You know, like a reciprocity, a style of a giver started to emerge where I needed to.
00:38:58.630 --> 00:39:03.744
I needed to give back because I had taken so much Knowledge from this community and so I started to write up.
00:39:04.626 --> 00:39:08.853
My project says how to is in the community, and so I wrote my very first one.
00:39:08.853 --> 00:39:13.121
I was called windows Imaging.
00:39:13.121 --> 00:39:17.067
Windows 7 with the fog projects of the fog project is like an open source imaging tool.
00:39:17.067 --> 00:39:21.733
It's like insanely complicated to install on Linux, and I had like a semester on Linux.
00:39:21.733 --> 00:39:24.204
I was like, okay, I at least know how to install.
00:39:24.204 --> 00:39:24.626
You want to?
00:39:27.043 --> 00:39:29.846
And so that's where it all kind of started and I started to teach.
00:39:29.846 --> 00:39:37.155
And when I got into the power shell in the scripting, a lot of that was just, I started a blog and I started to put that out there.
00:39:37.155 --> 00:39:58.635
And eventually I was sitting in a class one day and I was, my wife and I were starting about thinking about starting a family and if she would keep her job or not have her job, and so I just started to ponder, like, what are some other ways that I could have income and plus, I had just started like was just a startup company at that time was 2014, 2015.
00:39:58.635 --> 00:40:03.351
And I talked to the instructor of this class as I was like, what do I need to do to do what you're doing?
00:40:03.351 --> 00:40:07.927
And he very bloody said he's like I wouldn't do what I'm doing.
00:40:07.927 --> 00:40:13.362
I would do video courses is like I would reach out to To play with site and do that.
00:40:13.443 --> 00:40:33.664
and I just read the four hour work week and which in bolded me to just ask anybody anything right and I was living by that mantra, and so I reached out to one of my the people that I had watched courses for for the SCCM this is some center configuration manager and his name was Adam Bertram and he had a Twitter profile.
00:40:33.664 --> 00:40:36.190
So I just hit him up and was like hey, how did you become a plural site author?
00:40:36.190 --> 00:40:45.103
And he's like I just talked to this guy, his name's Adam Blake, and so I went over to Adam Blake's Twitter profile, was like hey, I become a plural site author.
00:40:45.103 --> 00:40:47.387
And they like, fill out this, this interview.
00:40:47.606 --> 00:41:01.784
And funny thing was I don't know if you know who he is, but Don Jones, who's a big figure in the the power shell space for many years, started a conference and all that did the comfort circuit for many years and that Ended up becoming a mentor of mine later on.
00:41:01.784 --> 00:41:06.853
But he was the one that did my audition interview for plural site.
00:41:06.853 --> 00:41:07.920
Wow.
00:41:07.920 --> 00:41:27.255
And so I had to do a demo of five minute thing of just like what's your style, like how do you present yourself, like how's your speech, and I got the green light by just recording it on my laptop microphone and ended up investing in the gear and you know finding technology I was interested in and then recording content on that.
00:41:27.255 --> 00:41:33.028
Eventually it got to be too much to do with a small family and a job, but I was able to.
00:41:33.028 --> 00:41:34.972
I think I have like five total courses.
00:41:34.972 --> 00:41:38.083
Only a couple of them are still active, but that's kind of how that all.
00:41:38.083 --> 00:41:39.688
Just they just came about.
00:41:40.681 --> 00:41:41.882
Yeah, this is awesome.
00:41:41.882 --> 00:41:47.554
Did you imagine some point pivoting, overpivoting, probably toward just creating content like this?
00:41:48.121 --> 00:42:07.643
I thought about it because I knew a lot of the people were making way more money than I was with my full time job doing that, but I just didn't have enough steam to okay to pivot over to that part of it was, you know, I started a family and I didn't like the process of being independent and having to worry about health care and all that stuff, and so that kind of kept me in and check.
00:42:07.684 --> 00:42:13.528
And then I had some what really derailed it, what I had some health issues in 2018.
00:42:13.528 --> 00:42:24.626
That just made it impossible to do kind of like anything other than just tread water, and so in that, a lot of stuff just kind of fell the way side and Extra quick, their activities was one of them.
00:42:24.626 --> 00:42:27.596
One of those things it might come back at some point.
00:42:27.695 --> 00:42:28.177
Never say never.
00:42:28.177 --> 00:42:36.692
Yeah, we've talked a little bit about the, about becoming more senior right now in the past, but that's that's your.
00:42:36.692 --> 00:42:38.474
Your your present now.
00:42:38.474 --> 00:42:50.735
And if a junior came to you and asking the questions you were asking your mentors now, is there a piece of advice you would give almost everyone and say, hey, start there.
00:42:51.260 --> 00:42:57.132
I would say the fact that you're reaching out is you're gonna get an answer and you're gonna be able to be successful.
00:42:57.132 --> 00:43:02.070
It's the people that don't reach out that are gonna remain stuck and stay junior.
00:43:02.070 --> 00:43:06.148
So just building your network and talking to people, because there's not gonna be any.
00:43:06.148 --> 00:43:07.471
It's all contextual.
00:43:07.471 --> 00:43:13.731
It's all situational, but if you can find the right people that have been where you are, they'll help you through it.
00:43:13.731 --> 00:43:20.731
So reaching out is that key piece of advice is what I would give to the juniors and I love it.
00:43:21.231 --> 00:43:21.893
This is so true.
00:43:21.893 --> 00:43:23.054
Thank you so much.
00:43:23.054 --> 00:43:25.121
Thank you, josh.
00:43:25.121 --> 00:43:36.481
It's been fantastic going on this roller coaster of your life and your activities and over pivoting and, but still falling on both feet and having a bit of a About this.
00:43:36.481 --> 00:43:37.405
That is good.
00:43:37.405 --> 00:43:38.347
Thank you so much for that.
00:43:38.347 --> 00:43:39.621
You're very welcome.
00:43:39.621 --> 00:43:40.463
Thank you for the time.
00:43:40.463 --> 00:43:44.393
Where would be the best place to find you online and continue this discussion with you?
00:43:45.222 --> 00:43:48.791
I'm most probably active on acts at Josh Duffney.
00:43:48.791 --> 00:43:51.869
That's my digital home for the most part.
00:43:52.561 --> 00:44:04.047
Okay, well, either a link directly to that, and I guess we can find pretty much you, we can find you pretty much everywhere from there and follow the tree, the branches of the tree, absolutely anything else you want to plug in.
00:44:05.101 --> 00:44:05.380
That's it.
00:44:05.380 --> 00:44:06.041
That's it for me.
00:44:06.041 --> 00:44:10.586
Yeah, I'm just on there sharing every bit of this journey on Twitter.
00:44:10.586 --> 00:44:15.032
I try to be pretty transparent and show what I'm learning, what I've missed, what I've failed.
00:44:15.032 --> 00:44:17.635
So, yeah, hopefully see you there.
00:44:17.635 --> 00:44:21.943
Teaching still yeah, thank you so much.
00:44:21.943 --> 00:44:23.670
Thank you very much, it's been a pleasure.
00:44:24.400 --> 00:44:28.780
And this has been another episode of the first journey we see each other next week Bye.
00:44:28.780 --> 00:44:31.264
Thanks a lot for tuning in.
00:44:31.264 --> 00:44:33.967
I hope you have enjoyed this week's episode.
00:44:33.967 --> 00:44:38.092
If you like the show, please share, rate and review.
00:44:38.092 --> 00:44:41.735
It helps more listeners discover those stories.
00:44:41.735 --> 00:44:50.652
You can find the links to all the platforms the show appears on on our website dev journey dot info slash, subscribe.
00:44:50.652 --> 00:44:53.021
Talk to you soon.