TRANSCRIPT 🔗
WEBVTT
00:00:00.160 --> 00:00:03.359
Hey, it's Jason, host of the Code with Jason podcast.
00:00:03.520 --> 00:00:04.480
You're a developer.
00:00:04.639 --> 00:00:06.240
You like to listen to podcasts.
00:00:06.400 --> 00:00:07.759
You're listening to one right now.
00:00:07.919 --> 00:00:13.679
Maybe you like to read blogs and subscribe to email newsletters and stuff like that.
00:00:13.839 --> 00:00:14.960
Keep in touch.
00:00:16.079 --> 00:00:23.440
Email newsletters are a really nice way to keep on top of what's going on in the programming world.
00:00:24.239 --> 00:00:26.800
Except they're actually not.
00:00:27.199 --> 00:00:36.399
I don't know about you, but the last thing that I want to do after a long day of staring at the screen is sit there and stare at the screen some more.
00:00:36.640 --> 00:00:40.240
That's why I started a different kind of newsletter.
00:00:40.320 --> 00:00:43.679
It's a snail mail programming newsletter.
00:00:43.920 --> 00:00:44.479
That's right.
00:00:44.560 --> 00:00:51.600
I send an actual envelope in the mail containing a paper newsletter that you can hold in your hands.
00:00:51.840 --> 00:00:59.280
You can read it on your living room couch, at your kitchen table, in your bed, or in someone else's bed.
00:00:59.359 --> 00:01:02.159
And when they say, What are you doing in my bed?
00:01:02.399 --> 00:01:04.879
You can say, I'm reading Jason's newsletter.
00:01:04.959 --> 00:01:06.159
What does it look like?
00:01:06.560 --> 00:01:12.640
You might wonder what you might find in this snail mail programming newsletter.
00:01:12.879 --> 00:01:20.480
You can read about all kinds of programming topics like object-oriented programming, testing, DevOps, AI.
00:01:20.719 --> 00:01:23.760
Most of it's pretty technology agnostic.
00:01:24.159 --> 00:01:42.000
You can also read about other non-programming topics like philosophy, evolutionary theory, business, marketing, economics, psychology, music, cooking, history, geology, language, culture, robotics, and farming.
00:01:42.239 --> 00:01:46.239
The name of the newsletter is Nonsense Monthly.
00:01:46.560 --> 00:01:50.560
Here's what some of my readers are saying about it.
00:01:50.879 --> 00:01:57.120
Helmut Kobler from Los Angeles says, thanks much for sending the newsletter.
00:01:57.280 --> 00:02:00.879
I got it about a week ago and read it on my sofa.
00:02:01.120 --> 00:02:06.400
It was a totally different experience than reading it on my computer or iPad.
00:02:06.719 --> 00:02:12.159
It felt more relaxed, more meaningful, something special and out of the ordinary.
00:02:12.960 --> 00:02:15.199
I'm sure that's what you were going for.
00:02:15.520 --> 00:02:18.879
So just wanted to let you know that you succeeded.
00:02:19.199 --> 00:02:20.800
Looking forward to more.
00:02:21.919 --> 00:02:31.520
Drew Bragg from Philadelphia says, Nonsense Monthly is the only newsletter I deliberately set aside time to read.
00:02:31.759 --> 00:02:44.159
I read a lot of great newsletters, but there's just something about receiving a piece of mail, physically opening it, and sitting down to read it on paper that is just so awesome.
00:02:44.479 --> 00:02:46.240
Feels like a lost luxury.
00:02:47.360 --> 00:02:57.919
Chris Sonier from Dickinson, Texas says, just finished reading my first nonsense monthly snail mail newsletter and truly enjoyed it.
00:02:58.240 --> 00:03:03.120
Something about holding a physical piece of paper that just feels good.
00:03:03.520 --> 00:03:04.479
Thank you for this.
00:03:04.639 --> 00:03:06.240
Can't wait for the next one.
00:03:06.560 --> 00:03:16.319
Dear listener, if you would like to get letters in the mail from yours truly every month, you can go sign up at nonsense monthly dot com.
00:03:16.960 --> 00:03:20.080
That's nonsensemonthly.com.
00:03:20.879 --> 00:03:22.159
I'll say it one more time.
00:03:22.400 --> 00:03:25.599
NonsenseMonthly dot com.
00:03:25.759 --> 00:03:29.280
And now without further ado, here is today's episode.
00:03:52.000 --> 00:04:00.479
Okay, so when you're teaching this stuff, when you're teaching about psychological safety, who are you teaching this to, like managers or other people?
00:04:00.639 --> 00:04:01.520
Tell me about that.
00:04:02.000 --> 00:04:03.199
Okay, it's a bit of a mix.
00:04:03.280 --> 00:04:08.479
I'm typically talking about people on the individual teams and their first level of management above them.
00:04:08.639 --> 00:04:12.560
Occasionally I'll do this at higher levels of management, but generally it's at the base.
00:04:13.120 --> 00:04:19.199
And I'm introducing all of this concept as a way, as information, so that they can start building on it.
00:04:19.519 --> 00:04:24.720
Because once they understand this and they can put a label on things, it becomes a lot easier to talk about it.
00:04:25.120 --> 00:04:37.360
There is an approach called affect labeling that says, and this is an actual psychological study tech approach that we can talk about that says if I can put a label on something, it automatically weakens its effect.
00:04:37.600 --> 00:04:44.160
So if I can say I am feeling uncomfortable, now I'm actually feeling a little bit less uncomfortable just because I said that out loud.
00:04:44.240 --> 00:04:45.360
That's affect labeling.
00:04:45.519 --> 00:04:48.560
And I know it sounds stupid, but it's an actual thing.
00:04:49.439 --> 00:04:50.480
Yeah, that's interesting.
00:04:50.800 --> 00:04:53.120
I I heard about that many years ago.
00:04:53.360 --> 00:05:05.519
Um, you know, a a friend of mine, uh we we there were one or more occasions where like things were getting weird and uncomfortable in a social situation.
00:05:05.759 --> 00:05:07.439
He's like, things are getting weird.
00:05:07.680 --> 00:05:09.040
You just say it out loud.
00:05:09.279 --> 00:05:14.639
And he said to me, like, you know, just saying that out loud makes things a little bit less weird.
00:05:15.199 --> 00:05:16.319
And it really does.
Load full transcript
00:05:16.720 --> 00:05:25.360
That there have been studies that back this up that show that the activity in your brain actually feels more comfortable and better if we can put a label on something.
00:05:25.439 --> 00:05:27.040
It weakens the whole effect.
00:05:27.279 --> 00:05:27.439
Yeah.
00:05:27.680 --> 00:05:30.800
So I start off particularly with anxiety and stress.
00:05:30.959 --> 00:05:40.879
I'm starting off, and if we can put some labels on things, if we can explain why things work the way they do, then we can have better conversations about it and it it starts to feel a bit better.
00:05:41.759 --> 00:05:42.399
Yeah.
00:05:42.800 --> 00:06:01.120
I if I may just digress for a moment, uh I I I'm just gonna wildly hypothesize that the reason for that is like if if that hasn't been said out loud, um, then maybe I think that I'm the only one who thinks that.
00:06:01.360 --> 00:06:20.720
Um, but if it's said, if if it's stated and gotten out in the open, now everybody knows that everybody else uh is aware um uh of this state of the group or whatever, that things have gotten weird or that uh whatever.
00:06:21.040 --> 00:06:29.439
Um and the fact that everybody knows it, everybody else knows it, uh creates a little bit of comfort.
00:06:30.319 --> 00:06:34.319
Yeah, and again, I don't know why it works, but it certainly does.
00:06:34.720 --> 00:06:36.240
So I'll I'll start off with that.
00:06:36.319 --> 00:06:37.600
I'll just explain some of the science.
00:06:37.759 --> 00:06:40.720
Sometimes I'll dive into neuroscience hacks for how you feel better.
00:06:40.800 --> 00:06:45.759
So if you're feeling stressed in the moment, you'll do some really quick hacks that will let go of that.
00:06:45.920 --> 00:06:47.279
I'll give you an example of one.
00:06:47.519 --> 00:06:57.439
One of my favorites is that if I pick something up, I've got my phone here, and I just move it from one hand to the other, back and forth like this, this is called bilateral stimulation.
00:06:57.920 --> 00:07:10.959
If I when you're feeling really stressed, if I were to hook you up to an fMRI machine, what we would find is that the right hemisphere of your brain is lit up like a Christmas tree, and the left hemisphere is largely idle when we're feeling stressed.
00:07:11.360 --> 00:07:19.680
And by doing this, passing an object back and forth, we're forcing the left hemisphere to wake up and talk to the right hemisphere, and it calms us right down.
00:07:20.480 --> 00:07:21.040
Interesting.
00:07:21.360 --> 00:07:25.439
So that's a really simple neurological hack that we can do, and I teach a whole bunch of these.
00:07:26.480 --> 00:07:26.800
Okay.
00:07:27.680 --> 00:07:30.079
I I gotta dig deeper into that.
00:07:30.319 --> 00:07:37.040
Um remind me, w what are the responsibilities of the two hemispheres of the brain?
00:07:37.199 --> 00:07:51.759
You know, one of them is like the logical analytical side, and the other one is like holistic and so, first of all,
this is drastically oversimplifying because the reality is that if you actually injure one part of your brain, the other part will take over for everything.
00:07:52.000 --> 00:07:54.399
So there is a little bit of everything going on on both sides.
00:07:54.480 --> 00:07:57.199
So this is a dra drastic oversimplification.
00:07:57.360 --> 00:08:02.959
But having said that, the right side is largely creative and the left side is largely logical.
00:08:03.600 --> 00:08:06.079
And the left side also has your sense of time.
00:08:06.240 --> 00:08:12.959
So when you're really feeling stressed, you often lose sense of time, and that's because the left hemisphere is largely idle.
00:08:14.720 --> 00:08:15.920
Okay, interesting.
00:08:17.040 --> 00:08:18.560
Um okay.
00:08:19.199 --> 00:08:20.160
Yeah, all right.
00:08:20.319 --> 00:08:24.560
Um and what other kind of stuff do you do you teach teams when you work with them?
00:08:25.680 --> 00:08:27.360
Yeah, well, I'll I'll teach a lot of stuff.
00:08:27.519 --> 00:08:28.560
We'll talk about motivation.
00:08:28.639 --> 00:08:41.120
So there's the the self-determination theory motivation model, which goes from fully intrinsic, people are fully motivated, all the way on to the the far end to a motivation where people have no motivation to do anything.
00:08:41.279 --> 00:08:44.639
And if the work actually gets done, that was just a random chance.
00:08:45.840 --> 00:08:47.279
And we've got all these layers in between.
00:08:47.440 --> 00:08:53.759
Because we often just talk about intrinsic and extrinsic motivation, but the STT model actually calls it out into seven separate steps.
00:08:53.919 --> 00:08:54.080
Uh-huh.
00:08:54.240 --> 00:08:57.120
So we've got different kinds of motivation at different times.
00:08:57.840 --> 00:09:02.080
And so I'll often talk through this when we're trying to figure out well, why is the work not getting done well?
00:09:02.240 --> 00:09:08.480
Well, perhaps because we're sitting you know, on the fairly far on the left where we're relying on external motivation.
00:09:08.799 --> 00:09:10.000
You know, the carrot and the stick.
00:09:10.399 --> 00:09:12.159
If I don't do this, somebody's gonna hit me.
00:09:12.320 --> 00:09:15.200
Or if I don't, if I do do this thing, I'm gonna get a reward for it.
00:09:15.279 --> 00:09:18.240
That's the worst, the least effective form of motivation.
00:09:18.399 --> 00:09:18.559
Uh-huh.
00:09:18.799 --> 00:09:22.159
Whereas over on the far right, it would be I'm doing this because I love it.
00:09:22.320 --> 00:09:26.000
You know, I'm all excited about the tools, I'm all excited about the thing I'm building.
00:09:26.159 --> 00:09:26.720
Look at this.
00:09:26.879 --> 00:09:29.519
I'm fully motivated, I'm off on the far right.
00:09:30.000 --> 00:09:32.080
And then we've got all these things in the middle.
00:09:32.320 --> 00:09:35.519
So I'll often talk about that, the motivation model as well.
00:09:36.720 --> 00:09:45.679
Um and this is a fairly different question, but um, do you do you do these things uh like on a self-employed basis?
00:09:45.840 --> 00:09:47.360
Do you work for an agency?
00:09:47.519 --> 00:09:48.879
Like, how does all that work?
00:09:49.200 --> 00:09:50.159
I am an independent.
00:09:50.240 --> 00:10:00.000
I have come in through other companies uh for a lot of work, particularly the the really big companies, the Fortune 500, they don't want to hire a direct, so they they go in, they hire through a middleman.
00:10:00.399 --> 00:10:01.440
Yeah, okay.
00:10:01.759 --> 00:10:25.679
Yeah, um I'm curious because I've done consulting myself, you know, on and off for many years I did freelancing, and then more recently I I have done what I call true consulting, where uh you you're getting hired just for access to your mind, basically, uh not for implementation work.
00:10:26.399 --> 00:10:35.919
Um and to me it's like the the the better you can do with your sales and marketing, the better the whole picture is.
00:10:36.320 --> 00:10:40.639
If you can get good, high-paying clients, then everything else can be figured out.
00:10:40.720 --> 00:10:42.799
And if you can't, then nothing else matters.
00:10:42.960 --> 00:10:45.120
So that's where it all starts with me.
00:10:45.440 --> 00:10:50.720
And the root of all the sales and marketing is what service do I offer?
00:10:51.120 --> 00:11:00.240
Um, and obviously, inseparable from that is who am I to whom am I offering this service?
00:11:00.799 --> 00:11:01.200
Right.
00:11:01.440 --> 00:11:26.720
Um, and you know, initially I was like, I want to help people with problems and I want to help them solve their problems, but I kind of realized that like um the the the people and the organizations who need my help the most are the ones who are the least likely to seek it out, the least likely to appreciate it, the least likely to use it, and all that stuff.
00:11:28.159 --> 00:11:49.279
Um, and so I'm like, okay, actually, I think I want to go after more high performing teams and help them do even better because paradoxically, I think it's the highest performing teams who have the most capacity for improvement, which makes sense because they're gonna be like the smartest, most conscientious people.
00:11:49.840 --> 00:11:56.159
Um, they're they're high performing because they have a large capacity for performance.
00:11:56.320 --> 00:12:09.360
And the people who are, you know, the organizations that are just disastrous disastrously dysfunctional, they are that way because of of the people who make up that organization.
00:12:09.679 --> 00:12:15.120
Anyway, in seeking out these high performing organizations, I never found them.
00:12:15.279 --> 00:12:31.039
Um, you know, never in my life have I have I really found um I I hate to say it, but like never have I really found all that high performing of an organization.
00:12:31.360 --> 00:12:37.519
Um approximately every organization is dysfunctional.
00:12:37.919
--> 00:12:51.519
Um there's maybe I I don't know if I've encountered a single exception uh to an organiz uh every organization that I've that I've encountered is some degree of dysfunctional.
00:12:51.759 --> 00:12:56.559
And this whole experience has just been very discouraging.
00:12:56.960 --> 00:13:01.039
Um, because it's like, man, you can't help anybody in this world.
00:13:01.279 --> 00:13:02.879
I know that's not true.
00:13:03.120 --> 00:13:07.840
Um but I'm just curious because it sounds like you know, this is work that you do do.
00:13:08.080 --> 00:13:13.039
People hire you for this stuff, uh, they they engage with you, it sounds like.
00:13:13.200 --> 00:13:22.879
So I'm I'm just very curious from somebody in my perspective who's had those experiences, what what kind of experiences uh have have you had?
00:13:23.360 --> 00:13:30.080
Well, I've found that I agree with your statement that every organization is dysfunctional and they're all dysfunctional in slightly different ways.
00:13:30.320 --> 00:13:36.639
But every company within it, any company of any size, has pockets within it that are astounding.
00:13:37.440 --> 00:13:45.200
And if you can find those pockets and then disseminate what they're doing and spread them across the organization, you can start to make some real change.
00:13:46.639 --> 00:13:53.519
So when I come into an organization, I'm typically looking for where are those pockets that are doing absolutely amazing work already.
00:13:54.159 --> 00:14:06.480
And how can we use them at a minimum, how can we use them as a reference point and say Because when you come into a company and you say, if you just do these practices, if you set up continuous delivery, if you set up all of these things, you'll get better results.
00:14:06.559 --> 00:14:09.919
And they say, Oh, well, no, that would work somewhere else, but that won't work here.
00:14:10.320 --> 00:14:17.360
So I'm looking for those pockets within the company that are already doing astounding things, and then I can say, look, it's possible in your environment.
00:14:17.600 --> 00:14:19.519
Look at this team over here.
00:14:22.320 --> 00:14:35.759
Have you ever Okay, so yes, that's um um had have you ever uh had a situation where you're talking with a team and it just feels like you're not even speaking the same language?
00:14:36.080 --> 00:14:47.120
Like uh the the concepts that you're wanting to refer to and teach and stuff like that, it's just you're not even in the same ballpark, and so it's it's hard to even communicate.
00:14:47.279 --> 00:14:48.799
Like I'll give a quick example.
00:14:49.039 --> 00:15:02.639
I worked with a team that would talk about refactoring a lot, um, but then I discovered that to them, refactoring was experimentation with new design patterns and stuff like that, building new features.
00:15:02.799 --> 00:15:10.080
It's like, well, that that's not remotely what refactoring is, um, and and various things like that.
00:15:10.320 -->
00:15:15.360
And it was it was really slow going because of that.
00:15:15.600 --> 00:15:18.879
And in this particular situation, this is a different thing.
00:15:19.039 --> 00:15:21.039
No, they didn't ask for my help.
00:15:21.200 --> 00:15:28.320
And so I was this person who was there trying to help people who didn't ask for or even really want my help.
00:15:28.559 --> 00:15:32.159
Anyway, there's not a specific question there, but do with that what you will.
00:15:32.480 --> 00:15:38.639
Well, certainly I've come into lots of teams that first of all didn't feel they needed my help or weren't interested in my help.
00:15:38.799 --> 00:15:41.600
And I'm always looking for what's the quickest win I can get.
00:15:41.759 --> 00:15:53.840
Because if I can get one quick win, even if it's just how do you improve your daily stand-up a little bit, then all of a sudden now they're listen willing to listen to me and they say, Okay, that one little thing that you said it was minor, but it was an improvement.
00:15:53.919 --> 00:15:54.639
We like that better.
00:15:54.879 --> 00:15:55.840
Do you have another one of those?
00:15:56.000 --> 00:16:02.000
Yeah, let's do another quick win and another quick win, and pretty soon we're we're breaking into actual revolutionary change.
00:16:02.799 --> 00:16:10.559
But the story that you were telling about refactoring reminded me of a time I went into a team and I I had been asked to come in and show them TDD.
00:16:11.120 --> 00:16:18.080
And I came in and I started talking to them about TDD, and I explained that it was really a quality practice, not a coding practice.
00:16:18.399 --> 00:16:24.240
It was all about how do we improve our quality and the dis the quality of our design and all this, and they said, Let me just stop you right here.
00:16:24.480 --> 00:16:26.000
We don't have a quality problem.
00:16:26.159 --> 00:16:27.679
We write perfect code.
00:16:28.320 --> 00:16:32.480
And I was trying not to laugh inside, but I said, Okay, tell me more about that.
00:16:32.559 --> 00:16:33.519
You know, this is awesome.
00:16:33.600 --> 00:16:37.919
If you're writing perfect code, I want to know more about it so I can spread this across the rest of the company.
00:16:38.639 --> 00:16:47.679
And so, well, what it turns out is that they hadn't had a bug reported in production in a long time, which is still excellent, really, really good, but it's not the same as having perfect code.
00:16:48.000 --> 00:16:49.759
So we talked, we talked about it a little bit.
00:16:49.840 --> 00:16:52.799
I said, would it be alright if I just showed you the technique?
00:16:53.039 --> 00:16:58.799
And if at the end of this you decide it's not going to give you any value, then I walk away, no damage done.
00:16:58.960 --> 00:17:00.879
And they said, Yeah, okay, we'll listen to that.
00:17:01.120 --> 00:17:05.039
And about two hours later we'd found about a dozen bugs in their production code.
00:17:05.920 --> 00:17:06.400
Wow.
00:17:06.640 --> 00:17:08.160
How do they react to that?
00:17:08.640 --> 00:17:15.920
Uh well at first they were defensive and they said, Well, no, no, that really doesn't satisfy the definition of a bug because it wasn't reported by the client.
00:17:16.079 --> 00:17:25.200
Okay, so now we start to unpack a little bit of this, because in their mind, what the bug meant was different than what I meant, just as your example with the refactoring.
00:17:25.920 --> 00:17:29.519
So we unpacked that a bit, and I said, Well, does it do what you expect it to do?
00:17:29.599 --> 00:17:30.480
Well, no, it doesn't.
00:17:30.640 --> 00:17:31.920
Then it's a bug, isn't it?
00:17:32.720 --> 00:17:38.640
And so we went back and forth through this, and by the end of the session, they were now really interested in learning more from it.
00:17:39.440 --> 00:17:41.440
Interesting because I'd had a quick win.
00:17:41.920 --> 00:17:49.039
We'd found a bunch of bugs, and they weren't convinced that they really were bugs because nobody'd ever encountered them in a production environment.
00:17:49.359 --> 00:17:53.279
But they agreed that they weren't doing what they expected the code to do.
00:17:54.880 --> 00:17:56.400
Different question.
00:17:56.559 --> 00:18:02.240
How do you how do you get time with the people who you're working with?
00:18:02.559 --> 00:18:06.880
Because I found that that's always a challenge.
00:18:07.119 --> 00:18:14.559
Um maybe the manager doesn't feel like they can afford to allocate a lot of time to to just learning.
00:18:14.720 --> 00:18:18.559
Maybe the individuals, you know, they're under a lot of time pressure all the time.
00:18:18.720 --> 00:18:22.799
Everybody is, and so they don't feel like they can afford to spend some time.
00:18:22.960 --> 00:18:25.359
Um, what has been your experience with that?
00:18:25.680 --> 00:18:28.480
Well, I just come in and I presuppose that I've got the time.
00:18:28.720 --> 00:18:31.519
And this is actually a phenomenal psychological trick.
00:18:31.680 --> 00:18:37.039
If I just come in and say, I'd like you to book two days on your calendar because we're gonna do this thing.
00:18:38.240 --> 00:18:42.880
And nobody really questions because I'm not coming in, I'm not asking for permission.
00:18:43.119 --> 00:18:46.160
The only thing I'm asking is for them to actually book something on the calendar.
00:18:46.400 --> 00:18:48.160
I didn't ask for permission to do that.
00:18:48.319 --> 00:18:50.079
I didn't say would it be okay?
00:18:50.240 --> 00:18:58.559
I said block two days on your calendar and we're gonna do this, but I also qualify it with at the end of two days if you decide you don't like this, I won't ask you to do it again.
00:18:58.960 --> 00:19:08.319
So I've just I've limited the scope of the experiment, I've put a time box on it, I've made it very short, and I've made it very clear that if you don't like this, you don't have to do it.
00:19:08.559 --> 00:19:12.160
And everybody
thinks I can put up with any old crap for two days.
00:19:12.799 --> 00:19:16.240
And by the end of two days, they're usually asking if they can do a third day.
00:19:16.720 --> 00:19:17.039
Okay.
00:19:18.160 --> 00:19:20.880
How long do your engagements tend to be?
00:19:20.960 --> 00:19:23.519
Do they do they span days or weeks or months?
00:19:24.240 --> 00:19:41.200
Because okay, I've had the experience of doing uh corporate training or you fly into some office and you spend three days or five days or whatever teaching, usually some factual topic, like here's uh you know, learn Java or something.
00:19:41.279 --> 00:19:48.160
I never taught that, but something like that, and then you fly home and no one ever speaks to each other again.
00:19:48.559 --> 00:19:51.599
And honestly, I think that's kind of madness.
00:19:51.759 --> 00:19:56.160
Uh but anyway, how do you that's where you need the reinforcement?
00:19:56.319 --> 00:20:09.440
So when I pitch something, well, I'm pitching a training class, it's you know, I I say first of all, I need a little bit of time getting to know the teams because I don't want to throw them straight into training until I know them, because otherwise I'm gonna teach them the wrong things.
00:20:10.240 --> 00:20:12.000
So I need to know where the pain points are.
00:20:12.160 --> 00:20:20.000
So a little bit of observation, then I go into a training class, and then in the quote, I say we're gonna do multiple days of mobbing with each team.
00:20:20.319 --> 00:20:22.079
Because that's when I reinforce it.
00:20:22.640 --> 00:20:29.839
Because I know that if I just teach it and then I walk away, they're gonna say, That was fun, but I don't know how to apply it to real work.
00:20:30.160 --> 00:20:31.599
That's why I do mobbing.
00:20:32.559 --> 00:20:32.799
Okay.
00:20:33.200 --> 00:20:38.799
So I'll I'll sit with them and we'll actually apply the concepts that we did in the class to real work.
00:20:39.200 --> 00:20:43.200
And now they have a much better chance of actually doing the things that they were doing.
00:20:43.839 --> 00:20:44.640
Interesting.
00:20:44.960 --> 00:20:54.160
Well, this is encouraging because, you know, it from my perspective, very few people do this kind of work.
00:20:54.319 --> 00:21:00.960
Um, most most freelance programmers just do like staff aug programming, coding by the hour kind of thing.
00:21:01.039 --> 00:21:02.000
That's fine.
00:21:02.240 --> 00:21:11.839
Um, very few people do do some kind of consulting where they're trying to effect some kind of organizational change.
00:21:12.000 --> 00:21:18.960
And so when I was doing this kind of work, it was very lonely because I hardly knew anybody else who was doing that kind of work.
00:21:19.119 --> 00:21:22.559
I don't think I really knew anybody else who was doing this kind of work.
00:21:22.799 --> 00:21:31.759
And I was just met with I wouldn't exactly say failure after failure, but non-success.
00:21:33.440 --> 00:21:38.319
Um,
I don't want to make it sound like everything's been perfect for me.
00:21:38.960 --> 00:21:39.359
Oh, great.
00:21:39.519 --> 00:21:40.480
I don't that's good to do.
00:21:40.640 --> 00:21:42.799
I don't want to make it sound like everything's been perfect.
00:21:42.880 --> 00:21:51.039
I've had times where I spent months with a group of teams and we got them to a really good place, and as soon as I leave, they did a reorg and undid everything.
00:21:52.079 --> 00:21:52.319
Right?
00:21:52.400 --> 00:21:56.160
So I've had cases like that where the the success did not last.
00:21:56.559 --> 00:21:59.759
But usually it's because it's because a leader changed position.
00:22:00.559 --> 00:22:03.599
And the new leader that came in didn't like those things anymore.
00:22:04.720 --> 00:22:05.039
Okay.
00:22:06.559 --> 00:22:07.200
Yeah.
00:22:07.920 --> 00:22:08.559
Yeah.
00:22:09.039 --> 00:22:22.400
Um the Jerry Weinberg, he said something like, uh, despite everybody's best efforts, uh, hardly anything of of substance ever changes, or something like that.
00:22:22.640 --> 00:22:25.519
It's like, yeah, that that kind of tracks.
00:22:25.680 --> 00:22:34.319
You like push with all your might uh for as long as you can and everything budges one millimeter or something like that.
00:22:34.559 --> 00:22:37.599
Um and it's hard not to get cynical.
00:22:38.160 --> 00:22:41.440
Um but I guess yeah.
00:22:41.759 --> 00:22:47.359
But but the the teams never get as far as I want them to as quickly as I want them to.
00:22:47.519 --> 00:22:49.039
But they all make progress.
00:22:49.440 --> 00:22:52.880
And if they are better when I leave than when I arrive, then we're winning.
00:22:53.039 --> 00:22:55.680
Even if it's not as much better as I would like.
00:22:56.720 --> 00:22:57.359
Right.
00:22:57.599 --> 00:23:03.440
Something I always remind myself is an improvement is still an improvement.
00:23:03.759 --> 00:23:04.240
Mm-hmm.
00:23:04.960 --> 00:23:17.119
Even if it's and and a lot of things Yeah, you're comparing it to what you wish would be the case, and obviously everything's always gonna fall short of what we wish were the case.
00:23:17.279 --> 00:23:20.559
Um, but maybe from their perspective, sometimes this happens.
00:23:20.640 --> 00:23:29.920
Like from your perspective, very little happened or nothing happened, but from their perspective, it was revolutionarily transformative.
00:23:30.559 --> 00:23:31.200
Right.
00:23:32.559 --> 00:23:36.079
Yeah, but just generally, are the people on the ground, are they happier with the work?
00:23:36.160 --> 00:23:37.519
Are they actually accomplishing more?
00:23:37.599 --> 00:23:38.720
Did they learn something?
00:23:38.960 --> 00:23:41.200
Are we getting better at delivering value to our clients?
00:23:41.359 --> 00:23:54.799
As long as we're moving the needle in the right direction, then we're willing to I have to ask this business question also, because I ask it of everybody I encounter who's who's self-employed.
00:23:54.960 --> 00:23:56.640
Um, how do you get your clients?
00:23:56.720 --> 00:24:05.599
I'm guessing it's some form of uh speaking and in writing and stuff like that is is uh ingredients in the recipe.
00:24:06.240 --> 00:24:06.720
Yes.
00:24:06.960 --> 00:24:10.720
Um I spoke I've been speaking at conferences for probably 30 years.
00:24:10.960 --> 00:24:15.119
Um I I blog a lot, I post on LinkedIn a lot.
00:24:15.279 --> 00:24:19.039
Um I found about two years ago my market changed.
00:24:19.680 --> 00:24:26.799
And so let's before the market shifted, I was working primarily with the big Fortune 500, the the massive companies.
00:24:26.960 --> 00:24:33.759
I had some small clients, but I was working primarily, spending most of my days with the big companies, and for them it was all referral.
00:24:34.160 --> 00:24:41.680
All my work came from I I'd say that I was available and somebody I knew would have some work and I could just get pulled in.
00:24:42.400 --> 00:24:44.160
About two years ago that changed.
00:24:44.640 --> 00:24:50.000
And all of a sudden the big companies stopped hiring, and now I was focusing on the the mid-sized companies.
00:24:50.319 --> 00:24:52.400
You know, maybe a hundred million dollars in revenue.
00:24:52.559 --> 00:25:01.119
Which doesn't sound mid, it still sounds like a pretty big company, but compared to the Fortune 500s that are making billions every quarter, they are much, much smaller.
00:25:01.440 --> 00:25:09.200
And so moving into that space has required a lot more blogging, a lot more LinkedIn type of content.
00:25:09.440 --> 00:25:12.720
Because it's a different getting to that audience is different.
00:25:13.359 --> 00:25:13.680
Okay.
00:25:14.480 --> 00:25:16.960
Man, that is so interesting.
00:25:17.279 --> 00:25:18.720
Um, okay.
00:25:19.680 --> 00:25:26.799
Sometimes I find a guest who I wish I had, you know, three or four hours with, and and you are such a guest.
00:25:27.039 --> 00:25:32.240
Uh I wish we had I've I could probably talk with you for days and days.
00:25:32.400 --> 00:25:35.839
Um, but we're we're getting close to time.
00:25:36.160 --> 00:25:43.680
Um before we go, is there anything you wanted to touch on that we haven't uh that we haven't touched on yet?
00:25:44.160 --> 00:25:46.160
Well, we've we've talked about an awful lot of things.
00:25:46.240 --> 00:25:53.200
I I realized looking back through all of your past guests that you spend a lot of time talking about the technical, and we really didn't get into a lot of the technical here.
00:25:53.519 --> 00:25:56.640
I see that Ruby is a recurring theme in your podcast.
00:25:56.720 --> 00:25:58.319
I love Ruby and I write a lot of that.
00:25:59.119 --> 00:26:05.920
Um I I write a product called JiraMetrics that extracts all kinds of useful stuff out of Jira, all written in Ruby.
00:26:06.079 --> 00:26:09.119
So we could spend hours talking about that stuff as well.
00:26:09.839 --> 00:26:11.039
Yeah, okay.
00:26:11.359 --> 00:26:16.079
Okay, well, I hope that um you'll be up for another episode sometime in the future.
00:26:16.160 --> 00:26:28.640
Um and very last question: any links or anything like that you want to share with people so they can find out.ca is my main website, and from there it goes off to everywhere else.
00:26:28.960 --> 00:26:29.279
Okay.
00:26:29.440 --> 00:26:30.480
So awesome.
00:26:30.640 --> 00:26:32.720
Well, Mike, thanks so much for coming on the show.
00:26:32.960 --> 00:26:34.079
Well, thanks for having me.
00:26:34.240 --> 00:26:34.880
It's been fun.