Hello and welcome to another episode of The Bike Shed, a podcast from your friends at the thought about developing great software. I'm Joelle Kenville. And I'm Sally Hall, and together we're here to share a bit of what we've learned along the way. So Sally, what's new in your world? Oh, many things I know in my world. My kids graduated high school last week at twins,
and they graduated high school, and getting ready for college, and it's a wild time. It's kind of exhausting, but it's also pretty exciting. It's a big milestone. It is, it is. I feel like, you know, it's been something we've been looking at for 18 plus years.
And I realized the other day I was talking to my wife about something, and was like, we could just deal with that after the kids leave for college, which used to be a like, way in the future thing. And now it's a eight weeks from now thing. Yeah. Yeah. Does that mean they are moving out?
They are. They're both going to colleges fairly close by. Well, one's about 25 minutes away, and the other one's about an hour away, but they'll both be living on campus, moving out, living with remains the whole thing. Well, that changes the dynamic at home for you as well. It certainly does. It's going to be a lot quieter here.
Get a whole new room to take over for your knitting projects. I'm going to try not to totally invade their spaces until they've like finished college and are real adults, but we'll see. We'll see. Like in this sort of transitional period. Yeah. Yeah.
Get to come home in your bedroom still there. Yeah. You should have a place to sleep at Christmas, I think. Uh-huh. So what's new in your world?
I went hiking recently, climbed a mountain. Cool. And it's one of those mountains where you end up doing a lot of scrambling. You're walking through a boulder field and you're sort of picking your way through rocks, rough times over rocks. You might have points where it's more or less just a big slab of granite that you're kind of like walking over, especially as you reach towards the top of the mountain.
That's a really fun way to hike, I find. A little bit of a technical challenge. Makes it interesting. And I found that was just a really fun time. That sounds fun. It also sounds like something I would injure myself doing.
Did you come out safely? I did, yes. It's nice. I am intensely clumsy and there's no way I would get through that without at least one injury, but hopefully it'd be minor enough to be worth going again. I know for some of that, uh, poles can be really helpful. I know a lot of people use poles.
Honestly, I find it much harder coming down. My brain's going to do cool. I would stay up high school for that, but. You'd still injure yourself with poles, you said. Oh, I think I would. I think I would. I think I would.
Like, stab myself at the pole sex. Oh. Yeah. But I guess they are dangerous in that way. Yeah. Yeah. I'll be fine.
We're actually going to Yellowstone next week and we'll be doing some hiccuping. So hopefully. Nice. I skipped out without any major injuries too. Where were you hiccuping?
On your bike or? This was a mountain knock in New Hampshire. Cool. I thought that was beautiful. It's apparently one of the most hiked mountains in the US.
Oh, wow. Not about what you hear about, but it is just a little enough of a challenge and close enough to some large metro areas that are very accessible. And so people show up there and hike the mountain. Sounds really fun. So there's a difference between just sort of hiking to enjoy the trail and sort of hiking to try to reach a mountain.
Yeah. People sometimes compare career progression with climbing a mountain, working your way up through a variety of titles, getting ever fancier, advanced your titles. Yeah. In our industry, it's kind of interesting because you reach a point where you often get pushed into the management track. Although many organizations also have a sort of specialized IC track where you can get sort of beyond senior while still staying at the individual contributor type rule, where you don't have people reporting to you.
Yeah. And that's something we introduced a few years ago. I thought about, right? That's right. So thought has a sort of regular developer role, a senior developer, and then our sort of senior plus role is called principal developer.
Yeah. And it's been interesting sort of seeing us as an organization grapple with what that means, especially a consulting company, because it's kind of different than it would be in a product company. Yeah. Although, honestly, even within a product company, there are a lot of different ways to interpret that role. Also, there's a little bit of hand waving around what the titles mean.
Yeah. You'll often see sort of staff engineer also sort of thrown into the mix, depending on the company. Some might sort of merge those two roles together and call it just staff, just call it principal. Some will sort of split them and say, you are staff and then beyond staff, you're principal. So there's a lot of hand waving around what those titles mean in terms of the gradation. And then also in terms of the actual role, what are the ways you're trying to
have impact? What they all have in common, though, is that you're looking to have broader impact rather than beyond just writing good code. So you're not just shipping more and better as a single person, but you're also not managing a team. So you're finding some other way of having an impact at a team or organization level that is not management. Yeah. I think this is not a direct comparison. So the metaphor falls pretty quickly. But when I
think about it, I sort of think about it in terms of academia, where it's like, if you go and get a PhD, that's not just what you did as an undergrad, but more of it. It's sort of a different approach to like, how can I contribute to this field in a meaningful way that I'm interested in? And not just like, I'm going to do harder homework, which seems kind of similar, because a principal, it's not just like he's the guy who gets the hard tickets. It's like a broader thinking holistically about things and contributing to the company and the field in ways that interest you in like progressing the work. Does that sort of align with how you see it? Yeah, I would say so. There can be sort of a
lot of different ways that you can push on that. I think part of what you were describing sounds a little bit like what I think back in the day used to be termed an architect. I've not really seen that role much in the past decade, but that often was kind of a senior plus person who was involved a little bit more in thinking broadly about the system as a whole and how to align strategy to engineering. Yeah, my, whatever I think about architect and the term of software engineering, I think of this one guy I worked with decades ago who was an architect. I can never figure out what he did, because it mostly seems to be wandering around and eating other people's sandwiches. But that's pretty sure that's not actually what his role was supposed to be.
I think that architects sometimes have bad reputation in the industry for a little bit that the like, what exactly would you say you do here? Or just sort of a little bit too disconnected from the work and sort of pie in the sky thinking about structure. That doesn't mean that sort of work isn't valuable, but yeah, that particular manifestation that I think often had a bad reputation. Really, I think the role would ideally be more like that high level thinking, but also sort of a bridge between like the ICs who are not involved in that and the other pieces of the team that maybe aren't even developers. Does that provide any with you? Or is that something that you think
of as part of your role as principal? It can be. I think where things are a little bit different internally at Thoughtbot is that we're not developing software for ourselves, or at least not in that sort of full-time way that product organizations would. So there's a little bit less of that aspect of the role for myself internally at Thoughtbot. I have occasionally been in a little bit of role like that for a client, depending if that's what they need. But oftentimes that's a role in an
organization that you want someone who has sort of deeper organizational ties where they have some of that history of how things are that often helps them to be more effective in a role like that. That makes sense. So what does the principal role look like for you? So there's kind of multifaceted because there are sort of internal versus external aspects. But all of them are grounded in having an impact that is beyond just doing excellent work for clients through coding. So that can be a various forms of acting as a multiplier on our team.
That can be through various forms of having a broad impact on the industry beyond Thoughtbot. And that can also take a few different forms with our clients. But again, the core of it all is impact that is beyond just doing solid technical work sort of that day to day. Yeah, which I feel like kind of in my mental academia framework, which I'm not sure why I came up with that. I've never really been in academia, it's sort of like the difference between teaching classes and like the work a professor might do outside of the classroom and research or collaboration or visibility for their area. One thing that we encourage principal developers to do
within Thoughtbot is to pick an area of focus, an area where they want to have maybe outside contributions within the company. And for me, that area is sort of content and teaching, because those are both areas that I find a lot of meaning in. And so that involves a combination of both myself pushing the limits of what I do in that area. So speaking of a lot of conferences, writing blog posts, taking gnarly technical topics and making them really accessible to developers, either internally at Thoughtbot or something that's more public. But the flip side of that is the enablement side. And so that is helping other developers at Thoughtbot to do the same. And so
some of that is maintaining editorial guidelines. I've done some things around supporting coaching people who are interested in speaking at conferences. So the CFP process can be intimidating. One of the ways that we can help people through that. Yeah. And I think that sort of highlights one of the
things that's different about sort of the principal role is that going from developer to senior developer is sort of an expected path. If you are a developer and you've been working long enough and improving your work and contributing to the company and whatnot, eventually you will become a senior developer. Whereas principal developer is not something that everybody is going to end up even trying to do. It doesn't necessarily interest everybody. It's sort of a way to distinguish people who are already really interested in doing that kind of work. It's not just like, well, you've been a senior for five
years and you're so good at it. So let's make your principal now. Right. For most of the people thought about who have been promoted into that role, that's often a recognition of contributions or delivering things at a level that are significantly beyond the expectations of just the senior developer role. Especially in either sort of pushing the capabilities of what thought does in a particular direction or enablement of others. And again, it's that you're doing important things or you're helping
other people do things even better than they are right now. And that sort of dual track of it is how a lot of impact that happens that is not management when you're looking beyond just daily shipping code at a high quality. Yeah, absolutely. Now that sounds like a lot going on. And I know it's a lot going on because I see the work that and the efforts and the results from the work of the principles that I've been looking to interact with. How do you cram all of that
into a work week? How do you make time for that? How do you make space for that? So one thing that's really nice about is we get that investment day Friday. It does involve being very strategic for that time. Part of that does get eaten up by more meetings because part of what the role of
all tries to do is to help translate strategic goals from company management into actual impacts on the ground. And so that involves them attending those meetings, getting a little bit more of that context of like, here's what we're trying to do. Here's how we're thinking about certain problems that are ahead of us. And then finding ways to convert those into more practical things. And sometimes advocating for them within the team. So some of that happens in addition to then,
you know, perhaps pitching a talk to a conference or running an internal workshop on how CFPs work. Coaching someone on a project that they're doing. So all those things kind of stack up pretty quickly. Yeah. Do you find yourself doing much of that in your off hours? If off hours is even really a concept for you?
I think there's a gradation. Things like doing a conference talk always spill over into my person time. It's just my process is very time-intensive. And it is partly a work thing, but partly also a thing that I enjoy. And so I don't mind that some of that spilling into personal time. And so that's
a thing that will go extra. Other things I keep very strictly to stop on time. Or if there's things I'm doing for a client, then they stay strictly within the client time. How do you think the role would be different in a product company? So I think there's more expressions of the role within a product company. There's a website that
will link in the show notes. It's staffinch.com talks a little bit about what this role is like. And there's a particular article on their titled, What Do Staff Engineers Actually Do? That I find is really fascinating because it really gets at this sort of multi-dimensional aspect of the role. So I'll read all sort of just the headings from here. They're really interesting. And then we
can dig into those if those are particularly interesting to you. But one of them is setting technical direction. Another one is mentorship and sponsorship. Third one is providing an engineering perspective to decision makers. Fourth one is exploration. And then finally being glued,
which is sort of all those extra things that help to catalyze a technical team. It seems like many of those are extra relevant in a moment when AI is having such a huge impact on our field. As far as technical direction and engineering perspective and things like that, that CEO might want to have a principal engineer in the room when they're deciding now everybody must use AI. Or we're going to have a token leaderboard or something like that. What are your thoughts on that?
I mean, if you want a technical expert in the room, right? That is absolutely something that you're going to want, especially at a larger organization. And especially at an organization where maybe a senior leadership within the company doesn't have as much hands-on connection with some of these things. That does mean that your principal engineer who's going to show up in the room needs to know what they're talking about, though. That means keeping up with a lot of these things. And some of this can
be delegated. But part of the role is you have to sort of stay sharp and be able to speak to changes in technology, be able to think about ways that it can adapt. And so I think what you're getting at is the engineering perspective side of things. But another thing that was mentioned in that article is the idea of exploration. And so getting a sense of what's possible, having a little bit of creativity of like, here's different ways that we could maybe leverage a potential technology or knowing what the pitfalls are. Even if you don't necessarily go all the way super deep to be able to have
that conversation with senior management. But then also maybe with the engineering team, when they're setting their goals for growth or your setting, here's where we need to be as a team. That's going to matter a lot as well. What advice or questions to reflect on would you have for someone who is considering whether or not that's a role they'd be interested in or have they want to pursue? One of the things that can be a little bit challenging, especially at a place I thought about, where senior developer is a totally fine place to stop your career progression, or at least sort of title progression. It's not like you're going to be like, oh, you haven't moved on,
and like two years, you're on the list to get cut or something like that, which is the case of some companies. So when you start moving up towards that principal role, you start having more responsibilities, more things you have to work on, and that might be more than you want. And what can happen a little bit in that transition that's really challenging is that as you're moving towards principal, you start really exceeding expectations for your current role. And you were just knocking it out of the park. And then once you hit that promotion, all of a sudden, those things become baseline.
Yeah. You're no longer exceeding expectations. Because that role was meant to give a label to what exceeding all those expectations were. Yeah. Yeah. And maybe you want to say, I'm just going to, that's my new baseline. I'm just going to
sit there. Or maybe you want to start pushing to see, can I start exceeding expectations again? That can feel like a lot of pressure and that transition can be really challenging. So that's definitely something I would tell someone who's looking to go that direction to be aware of, in terms of how they navigate that emotionally, but then also just in terms of what the pressure and the workload feels like. But like, are you comfortable doing what you're doing now? If you started exceeding
expectations and you were feeling really good about yourself and that became baseline, would that be something that feels disappointing to you? More broadly, I'm thinking in terms of impact, what are the things that are really meaningful for you? Do you like just having impact by shipping stories and just being really good at that? Do you want to start having impact that has a broader range? And if so, what are the things that opportunities you see right now on your team, where you can have some of that impact? Maybe not as big as you would like to in the future, but right now that you
find are meaningful. And so really thought provoking things to think about. I feel like something in my brain is like, maybe when I can sleep for college. Maybe I will have room in my brain to sort of pursue some of that when a kid's like a college. But maybe I won't. And that's fine. And
maybe I like being a senior engineer. Maybe that's just where I'll stay. We'll see. And you've had a variety of roles within thoughtbot, right? Because you've been a team lead at one point.
I was a team lead at one point. So yeah, I did explore going down sort of, I think we think about it a lot as sort of like a fork in the road when you get to a certain point. You're either going to go down the management high level track or the IC high level track. So I tested the waters with the management track. I was a team lead for about a year and realized that it just wasn't the right fit for me.
I felt it was a combination of like, I wasn't sure that I was doing a very good job of it. But also like, I think it stressed me out more than I needed to. And finally, I just realized like this, this form of working with other people is not what I like. I love working with other people. I love mentoring and teaching and being taught a mentor. But like the formal HR reportable
relationship just felt very not how I like to work. And so thankfully, thoughtbot is kind of place to let you try something and then change your mind. So it wasn't like, well, you're in management now. Good luck. I was able to sort of gracefully step away from the team lead and go back to staff or senior developer. Yeah. And it's been interesting. And so like, I'm definitely at a
police now where it's like, okay, I've been with about four, seven years at this point recently. I've tried the team lead thing. Management isn't for me. And I thought about principal engineer. I think I'm not super interested in that yet either, because it's just like a level of focus that I don't have the resources for in my brain in life right now. And it's taking me well,
but I'm okay with that. And I am not a principal developer and I'm not focusing on being a principal developer, but I can still do interesting things at work and outside of work. Absolutely. Turns out they let you want to podcast, even if you aren't. Don't tell anyone.
And it's been fun to sort of like explore like, if I did want to focus deeply on something, what would that be? And sort of hopping around and trying different stuff and saying like, what catches me? What feels like it gives me a new level of purpose in this work. Yeah. And you might find throughout that that maybe you find yourself drifting towards situations that are sort of broader leverage. And then maybe that sort of you start drifting
towards more of a principal direction. If you find that you do more of these things than they're meaningful, maybe you start putting more conscious energy towards that and then it becomes an actual path that you're looking forward. Yeah. So it's interesting to have gotten to a point in my career where it's like, there's not an obvious next step and I sort of get to think about it and explore or just stay comfortable where I am and not have an official formal next step. That could be a very uncomfortable place. Yeah, sometimes it is uncomfortable, but sometimes it's also really freeing.
Like, I know that I'm doing a good job at my senior developer duties and I've become comfortable enough of them that it's open so easy, but it's like a it's a well-worn path. You know, when I when I stumble into a dark corner, chances are I've been in this dark corner before and I know where the lights are. And the things that I do outside of that, it's like, because there's not the pressure to like, you need to make it to this next level before you hit this many years or you're out of here. Right. And because it's widely acknowledged within Thaba, the principal is not for everybody and not something that everybody's going to be interested in pursuing. It doesn't feel like
there's pressure to like, Oh my God, I have to figure out what my principal focus is going to be. And instead it can be like, Oh, I think I want to explore maintaining an open source project for a while. And then, you know, that gets to a point where it's wrapped up and I'm not really excited about it anymore or handed off to somebody else or makes it completely obsolete or something. Then it's kind of like, okay, well, what what's next? What else do I get to think about now?
Which isn't to say that you don't have that freedom as a principal, but it feels a little bit more playful in this senior role. There's definitely in terms of what I sort of try to go deep on. There is a mix of interest and strategy. Yeah. Right now I'm some of that aligns because a lot of the stuff I'm exploring on the AI side of things, there's some personal interest there. But then also,
there's a lot of questions that our organization has that our clients have. And so being able to be that person in the room who has the answers say, I played around with this thing. Here's the results I've gotten so far. Or I keep up with these aspects of the industry and here's sort of roughly the three buckets that strategies have fallen into that people are using this tool in the past six months is a valuable thing to provide. Yeah, yeah, it's absolutely true. You mentioned earlier that
more at the beginning of your career, you had a really positive interaction at a place that had a principal engineer. What are some maybe aspects of this particular person's expression of the role that stood out to you? I think they were good at sort of like if we had a tricky piece of work we were doing and maybe they're not involved in actually writing the code for it, but like pulling them into a conversation and saying like, Hey, I'm struggling with this, there are a few different approaches and I'm not really sure what to think. I felt like they were always really helpful for like, Okay, well, here's something that maybe another team is doing that I've involved in that you don't know about that might reflect on that. So a little bit of glue there, like here's, you know, different teams are working on different things and here's how they might interact and here's someone that you could talk to about that or sort of like a broader perspective or sometimes just like super deep knowledge on something I just didn't know about. And this person never approached it as a like,
Okay, I will dane to offer you some of my golden nuggets of principal knowledge. And it was more like, Hey, I'm here, I have some resources and some skills and some knowledge. What can I do to help you? And that sort of aligns with all of my beliefs about leadership is that it's less about authority and prestige and more about like support and service to the rest of your team. And so yeah, the principal that I can remember that I really got a lot out of working with was really good at that was really approachable and helpful and knowledgeable. And also did a lot of like this sort of teaching
perspective that everybody hates in high school where it's like, I ask you a question and then you ask me a question back to guide me there. But it was less annoying in this context, I think. That's sort of a socratic approach. The website I referenced earlier that had that article about different aspects of the job also offers four archetypes that most staff plus roles fall into that I really fasten I do love, you know, turning things into a taxonomy. So the four archetypes are the tech lead, which is not a management position, unlike the team lead position at Thapat, but is someone who's really sort of connecting with the team to try to execute a particular strategy. There's an architect who's a little bit more around that earlier conversation
we had of sort of balancing strategy with the technical leads and trying to like bridge that but in a more of a planning sort of role. You have a solver who is often someone who's got deep expertise and can sort of have any type of problem thrown at them. And so they, when there's sort of a hotspot in the company, a problem that needs to be solved, need for focused specialized attention, you can just throw them at it. And then finally, there is a right hand who's sort of a bridge between leadership and various technical teams. And although it's not necessarily always embedded within a single team, they can sort of float around a broader organization and sort of be sent to deal with a particular issue or like you're saying make themselves available as a resource to a particular team because they have context on a problem. They can work with a particular team to maybe
set technical direction on where the team wants to grow. They might be a broader bridge between let's say the executive team and a variety of engineering teams. So it kind of varies a lot throughout. But the breakdown into archetypes I found was a really interesting way to put that. Yeah, that is really interesting. I imagine that one person could also probably move between
those archetypes throughout a career. Yeah, definitely. And I imagine that most principal developers have a little bit of all of those in them. I know that when we were initially creating the principal developer role at that bot, one of the things that we wanted to be part of that role was the idea that you have the sort of breadth of experience and knowledge that we can throw you at just about any project that comes our way. Sometimes we're we've got projects and we have to staff them. We have to find like a person who's a good fit for it. And sometimes there are more
challenging projects that come in that just have a particular shape that's not good for most people. And part of what we wanted with the principal developers is to say we have one or two people in our back pocket who we feel comfortable throwing on just about any project and that can help balance out those, especially when something unexpected comes up. Yeah, yeah, there are definitely projects I've seen where it's like we'll take a special soul to make this work out. One thing that's interesting I thought about I think in that vein is that we have often historically thought of our different roles based off of how they can be staffed. Historically, the distinguishing part between developer and senior developer was do you have the skills where we feel confident staffing you solo on a client, whereas people who just had the developer title typically we would want them to always be on a project where they had one other thought barter. So there's just a little bit more support going on.
Yeah, and when we've had apprentices in the past, the difference between an developer is that a developer is expected to be someone who can be built for on a project where is it a premise which generally not charging for their time because they're not at the level where they're really contributing that way yet. Right, they're there to learn and we don't want them to have the pressure of having to generate a value to justify a global time. And so clients like it because it's effectively free labor, but it's maybe not as much as thought by developer would be they're usually they're paired with a mentor. So they have much tighter support and that will pull a little bit of the mentors focus. So I don't know, maybe the mentor is 90 or 95% as effective as they would be without an apprentice. But if an apprentice is 30% effective or 50% effective and
they're not their time's not paid for, it's not on top. It's good deal. Which of those architects do you identify with the most these days? I'd probably say a little bit of the tech lead, a little bit of the right hand because a lot of what I've tried to do is lean into more of the enablement side of things. So try to lift up our team technically as much as possible while also trying to align to the strategic vision that the management team has. Because I think that I'm pulling from both of those
archetypes in the way that I probably most often express the role. That makes sense. And that sort of aligns with how I see your work too. So I probably would guess the same thing. Well, shall we wrap up?
I think this is a good place to wrap up.