Autoscaling is a simple concept. Automatically add resources when needed, and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up Autoscaling yourself, you know it's not that easy, especially using the native Autoscalers on platforms like AWS and Heroku. That's why you need JudoScale.
JudoScale is Autoscaling as a service, and they make Autoscaling simple and easy, as it should be. You can use JudoScale on AWS, Heroku, Render, Fly.io, and more. It's free for low traffic apps, and unlimited plans start at $25 per month. Autoscale on easy mode at judoscale.com. Hello, and welcome to another episode of The Bike Shed, a weekly podcast from your friends at the thought about developing great software.
I'm Joelle Kimville. 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? Well, I may have mentioned this before, but I have gotten involved with this organization called The Loose Ends Project that connects people who have unfinished crafts left behind by loved ones to people who have finished those crafts. So I got connected, really nice woman who lives just like an hour away from here and has a hand pieced quilt that her grandmother started.
Her grandmother, I think, passed away in the 60s. So it's been sitting on a shelf waiting to be finished for my entire life plus several decades. So I've been working on that, and it's been slow. And I sort of had a revelation this weekend when I was working on it, which is that I've been really nervous about it because it's like this family heirloom made out of old clothes from people who lived forever ago. And it's very special to this family, so I want to do it justice and take good care of it and finish it as well as I can.
But I've been getting a little frustrated because it was all done by hand, and it was made out of old clothes. So the fabrics are all different types and textures and weights, and the pieces are not really precisely cut, so they're not all the same size. Exactly. They're very close to the same size, but not exactly, which is made. I mean, it's impossible to sew them together perfectly.
It's the thing that I finally accepted. But it's also just difficult to, it's not like a mindless project. It involves a lot of problem solving on every seam, and each seam is about an inch long, and there are thousands of them. This is going to end up being bigger than a king-sized quilt. Wow.
And so I had been struggling a lot with like some anxiety over whether I was doing a good enough job on it and whether somebody else should do better. And this week I came across a bit where some of the pieces were sewn together incorrectly, which made other things not fit where they were supposed to. And that would have been done by the original crafter, original quilter. And as I was undoing those stitches to fix them, I was like, okay, yeah, the person was working on this before was also a human and made mistakes. Yeah, yeah.
And it's also highly possible that the reason that it never got finished is she got frustrated with the same things that I'm frustrated with right now. So this is not like, I don't know, it's really easy to build up in your mind that someone else is great at something that you're struggling with with absolutely no doubt. But realizing like, oh, it's entirely possible that this woman got frustrated with this quilt and just stopped working on it because it was too frustrating. So any progress that I can make is helpful. And just having it done rather than the absolute most perfect result, which is not possible for a human made thing, it's good.
So it was really helpful to remind myself that it's not like the person that did this before was the president of quilts and will be disappointed by my progress. They were human and I'm a human and we're doing a human project. And that has really helped me sort of relax a little bit. It doesn't make the project go any faster, but it makes me feel less stressed about how so it's going. That's really powerful.
The way that imperfection helps you to connect with the original creator of this quilt. Yeah. And it was, I don't know, it's a frame of thought that I could maybe use on code in the future, not only like having the confidence to believe in the work that I'm doing, but also having compassion for when I run into terrible code. Right. Right.
Sometimes we're the opposite, right? We're not the person handed an heirloom and being like, oh, can I live up to the potential of this? You're someone who's got some experience and you handed something that at first glance is not the way you would have done it. And you're like, oh, this other person is just not not professional. And realizing, no, they were in a context and they made some decisions within that context and building that empathy.
Yeah. And, you know, most of the time everybody I've worked with is really doing their best. So this person did their best. And this is what it is. And I'll do my best and see how that ends up.
So you're still treating the project with a lot of respect, but also you realize that there's humanity here and that perfection is not the goal. Yes. Absolutely. Yeah. So that has made me more relaxed and I've been actually working on it more because I don't feel the anxiety and pressure that I was putting on myself before.
That's a hobby project that's bound up with a lot of deeper feelings. Oh, yeah. Yeah. Yeah. And it's like the woman who it belongs to, she's about the age of my parents and it's her grandmother's will.
And she's talking about like the fabrics that are in it are dresses that she remembers her aunts and her grandmother and like her ancestors wearing. Wow. And she has children and I think she might have grandchildren and is wanting to like, you know, preserve this in a usable form for those families. So it's like this one quilt that I have been trusted with crosses like five generations. And that's so much family history right there.
Yeah. Yeah. It's also a beautiful, I'm really excited about it. It's really colorful. And I'm sure you're going to do an amazing job with that.
Well, thank you. I'm going to do my best and it's going to be great. What's new in your world? So this week, a new coffee shop open just around the corner from me on the other side of my block, which is really exciting and maybe a little bit dangerous. They had their soft launch midweek this week.
And I was like, you know, it's too in a walk away. I should show up for the soft launch. I don't typically get excited enough about, you know, new restaurant openings or whatever. Like go check out a soft launch. But like, it's a coffee shop.
It's right around the corner for me. I should get up early and go there. And so as I turn the corner to where the coffee shop is, I see there's just a line along the sidewalk, like halfway down the block. Like a line for the new iPhone or something, something like that. Yeah.
Oh, no. So, you know, and they're like, it's the staff's first time sort of working together. So they're also working out like the ordering system, but also just a lot of buzz in the neighborhood. So everyone's lining up there. They're running out of croissants, but eventually they didn't get a chance to try some of their pastries.
And yeah, I look forward to maybe becoming a regular there. Yeah. So the pastries were good. Did you get coffee too? I did.
Yeah. So what level of coffee person are you? Because I think there are people, you know, and as some people who's like a can of folders and as long as it caffeinates me, whatever. And then other people who use like very precise scales and thermometers to make sure they're burning the coffee exactly the way they wanted to. So brunch spectrum, sorry.
Where do you live? I enjoy coffee at all levels of the spectrum for years. I drank folders at home. I will absolutely drink gas station coffee on a road trip. But that might be a different category.
I know a lot of people who are a coffee solvers who make an exception for road trip. Yeah. Surprisingly, I find that I don't really like Starbucks. Their coffee is a little bit burnt without saying too much. I, that doesn't surprise me.
They're coffee is great. Yeah. Yeah. Sorry, Starbucks. But you know, it's not because I turn up my nose that they're basic coffee.
I will happily drink other forms of basic coffee anywhere else. Yeah. So I don't go to a new coffee shop and be like, Oh, no, the fruity notes in this one. We're just a little bit too far back of a palate or anything like that. Yeah.
Where is this coffee grown and how I was hoping for notes of cacao and this one here in More Elderberry. I don't know that I would recognize all the rare coffee, but yeah, cool. That's exciting. I feel like walking to strengths and delicious pastries and coffee would be kind of dangerous, but exciting for me. Yeah.
I love the ritual. I love the sitting on a warm drink, especially this time of year in the Northern Hemisphere. Yeah, definitely. I love holding a warm cup. I don't know if you ever know when you go to a diner and you get those like special like diner mugs.
Oh, yeah. The classic and they just have like bottomless coffee and you just get to hold those. It feels so great in the hands. It does. It does.
It's a whole like full sensory experience. Yeah. Yeah. Yeah. So I don't know the coziness of coffee.
Maybe I should say is what I'd like rather than the commissure aspect of it. Well, I think that's fun and that gives you room to really enjoy it in a lot of context and rarely be disappointed. Yeah, that's true. Do you ever work from a coffee shop? Are you like a bounce around kind of a motor or you have my set up at home and I like it kind of mostly do it from home.
Occasionally I work from a coffee shop and I might want to do a little bit more. I think that having some variety getting out of the house more can be good. That's fair. You know, sometimes shifting locations is great for, I think, increasing focus for ironically introducing change helps to not distract me. That's interesting.
I am the absolute opposite. I go to a coffee shop. I'm going to listen to every conversation around me whether I want to or not. And notice every person who walks in and out and I'm not super productive in a coffee shop. I also really like to have a second screen for coding.
Yeah, that's fair. I'm sure that there are people who do, but I would not feel great carrying a monitor and took out the shop. I don't think I would feel comfortable doing that either. Yeah. And then, you know, you face all the questions and the coffee shop from people who are like, what are you doing?
What's your job? And then how to describe your job to them, which is not straightforward. Yeah, we were talking about this the other day, how pretty much all the different titles that our industry uses for our job, things like developer or architect, engineer are not terms that originated within our industry. They're all loans from other industry and we've just tried to sort of get a metaphor to apply. How do you feel about these titles and how well do you think they apply to the work that you do?
Well, if you ask me what's written on, you know, like HR paper work or something, I think it's software developer. But in general, if you ask me what my job is, I'm probably going to answer it differently every day. Because some days, you know, the engineer metaphor feels correct some days. It feels like I'm really engineering a piece of software. I don't really have a good context for what engineering means other than the one semester I was an engineering major before I switched.
But it feels like, you know, working on different pieces of a system and making sure they all come together feels like engineering to me. But I know that professional engineers who do like civil or mechanical or whatever are all these different kinds of engineering, I've heard reactions from them that doesn't feel good to them, which is understandable. You know, they have to complete certain levels of education and exams and licensing and all of this stuff before they're allowed to call themselves an engineer. And we just, you know, open up VS code and have a lot of. Have you seen Lil Wayne's project where he interviewed a bunch of engineers across different disciplines to try to explore that question?
Are coders engineers? I had not you said Lil Wayne did this? No, not Lil, not the rapper. You can see why it was so confused. I mean, honestly, that would be amazing.
That would be. I was like, I've heard about this. No, Hillel Wayne. OK, yes, I do think I've seen that one. We can look at the show notes, but it's really interesting.
I think as software developers, sometimes we have a little bit of imposter syndrome and we're like, oh, you know, the engineers have all this rigor and everything. And they're they and their works sort of are like, no, there is no rigor here. We're facing a lot of the same messes that you're facing and a lot of the same situations solutions. There's some things that they see us do in our industry. They're like, oh, I wish that our industry can copy that.
And then vice versa, something they're like, oh, if I were to transfer to software, I would love to bring this from my discipline of engineering. So it's a really fascinating read. I'm honestly happy that engineers sort of responded that way. You know, it makes me feel better to know that people are not out there angry at us reaching the word engineer. They says not as many as I could imagine.
Yeah, but I do think that, you know, to some degree that title isn't entirely accurate. When you say that, you know, there's some days where you feel like you're doing more sort of engineering versus other days, you feel like you don't. What are the things that feel sort of engineering to you? Does the parts that have a rigor to your job, the parts where you do more planning before execution? I'd say anything that ends up with me drawing a diagram feels more like engineering, but I feel like, you know, talking to you, you are maybe drawing a diagram right now.
I don't know. Big diagram. Love diagrams. Yeah, I think, you know, if I'm having to do more planning, especially drawing things out and documenting things and integrating multiple systems always feels more like engineering to me. It's like getting like a system that you own to talk to a third party API feels more of an engineering thing.
Yeah, we're even like, I have two systems like the project I'm on right now, we've got to react front end and rails back end, we're using inertia. And anytime I'm trying to get those to work together, it feels a little more like engineering. But the more I talk about this, the more I'm like, I don't actually know when I feel like an engineer versus a developer versus a coder versus programmer versus sometimes I describe my job as just, I have to push a lot of buttons. What about you? How do you build out the engineering title?
Oh, I kind of think different feelings about it over the years. In some ways, I almost associate a little bit more as a corporate title. Interesting. I think if you're at a more kind of startupy place, you're more likely to use a developer or at least back in the day, whereas if you were to be a corporation, they likely use engineer for the same role. Yeah, I feel like corporations probably have more of a need to distinguish among different jobs than startups or even consultancies like ours.
You know, like within the development group, it really doesn't matter specifically how you are contributing to the code base. You are a code base person and therefore you are a developer. Whereas I think at a larger, more labored organization, there's more of a need to differentiate things and to say this is what engineering means here. And this is what those people do. Have you ever tried to debug an issue in production while switching between your error tracker, log viewer and APM tool?
Maybe you know how painful it is when you can see the error but can't find the relevant logs or when you see slow performance, but it can't connect to the root cause. Scout monitoring is all in one platform built to make your life easier with log management, performance tracking and error monitoring coming soon. All of your data will be together at last. You'll go from bug to fix in one place. The result, less context switching, faster debugging and monitoring that actually helps you ship code instead of distracting from it.
No DevOps team, no problem. Scout works with your existing stack and gives you insights in five minutes, not hours from bug to fix in one place at ScoutAPM.com. Which I guess leads to the role of architect. Which oftentimes in a large organization isn't just a like senior version of engineer, it's like a separate role that's almost more focused on the planning aspect of things. Yeah, in my experience, architects don't get to write a lot of code, but they do have a lot of opinions and have to go to a lot of meetings.
Interestingly, I think there's fewer, no, maybe there are diagrams there. Now, I'm thinking, you know, comparing a traditional architect to, you know, designs and plans buildings to a software architect to design and plan software. I think there was a movement in the early 2000s where that was seen as a sort of ideal for the industry to move towards, sort of similar to how an architect creates blueprints and then the developer or construction team implements them. The idea that architect would basically create a UML diagrams that could be almost a directly transferable into code that would then just need to be implemented by coding team or perhaps even by programs that could directly transform things.
I feel like, and this is maybe biased because of what I do, but I feel like there's a traditional architect that's going to call a person who does building since they're software architect. I imagine there are fewer unknowns in the planning of the building than there might be in the planning of software, which maybe architects are like, what are you talking about? But it's like tile and nails and shingles have not changed a ton in the past five or 10 years, whereas the internet and web development technologies change pretty quickly. See every JavaScript framework. Yeah.
Yeah. Although it's changing. It's not because a lot of things from sort of all the different frameworks that came out in the 2010s are just sort of repeating trends that were existing in sort of desktop in the 90s. So I'll talk to developers that have been in the industry for 20, 30 years. And you know, something that sounds like a cool new trend.
They'll be like, yeah, no, that's basically just, you know, the name, some protocol or some system from the 90s. And like, yeah, they're just redoing this again. I think another difference, the diagram that comes to mind when I think about MVP that I've seen a million times and maybe you haven't, we can link to a version of it of where, you know, you build a skateboard and then a bicycle and then a motorcycle and then a car. Right. That's like the idea of iterations.
And that doesn't translate well to building physical things. You know, like if you were trying to build a car and you started with a skateboard, you would be very much going in the wrong direction. And I think software is a little more flexible in that you can turn a skateboard into a bicycle a lot more easily than you could turn a physical skateboard into a bicycle, which I think in some ways makes things easier and it's always makes them harder. Yeah, the fact that you're not sort of always working from one sort of unified design from the beginning. Yeah.
You're starting with one thing and then sort of as the app is live and in motion, you've got to swap out the engine or add new wheels or whatever without breaking things and without stopping forward movement. Yeah. Like a renovation in a house is a big thing that often involves moving out and disrupting a lot of things. Refactoring an app ideally is going to be fairly transparent to the end user and happen a lot more often. I'm not just refactoring, right?
Like adding new features should also be a thing that doesn't break the app or cause you to have to shut things down for an hour while the new version goes live or something like that. Yeah. And someone was coming to my house to fix and or upgrade things as often as we deployed a feature about fixes to software, I would get pretty frustrated. I mean, it would be nice to have constant improvements and fixes, but it also probably wouldn't be worth the disruption to actually using the house. I had a plumber come to my place a few weeks ago to replace a rusted pipe in a very old building and they had to like turn the water off entirely.
So they're just like, sorry, for all of today, you just cannot use the water in your house, you know, no using the sink, no using the toilets, no showers, just, they're all telling me just to get out for a whole day. Yeah. And we can't do apps that way. No, I mean, some people do. Sometimes you do there are, you know, websites that are just completely unavailable for upgrades and there's some kinds of upgrades that you have to do that way.
Yeah. Replacing a pipe is not a major upgrade than doing the equivalent of that software should never lead to a complete outage. We should not kick you out of the house and turn off your water to upgrade your internet pipes. I like that metaphor. Somehow we've not really taken a lot of metaphors from plumbing in the software industry, despite taking a lot of other metaphors from different building trades.
We flush caches, right? We flush things. You know what? That's fair. Yeah.
Yeah. You guys can talk a lot about streams data flow similar to water. Yeah. Yeah. Unix system.
We'll talk about piping. There are pipes. Like, I think that those metaphors are all related to like tools or stuff we do and not what our job is. Yeah. Let less than the titling.
You're not a software plumber. No, although sometimes it does feel like it. So I think that there are some words that did originate with software that don't feel like they capture what we do completely to me. Mm. You have an example.
So I said I was a coder or a programmer. I do write code. I do program, but that feels like part of my job. Honestly, that feels like calling a surgeon, a cutter and stower when like those are, you know, necessary actions to a surgeon's job, but they don't at all encapsulate the work or really where the expertise I mean, there's some expertise, but it's very sort of low level compared to where's where the true expertise, the job lies. Yeah.
I do a lot of sewing. I'm very good at cutting and sewing. Do not let me do surgery. Keep that in mind. Yeah.
Yeah. I mostly cut and so fabric. Never tried it on a person don't want to. Yeah. So like coding and programming, I think for someone who is not at all involved in the industry might be the best way to describe what we do.
But I feel like the time that I spend actually typing out code versus the time that I spend thinking about it or talking about it or researching it is minimal. I could call myself a programmer, but programming isn't actually what I spend most of my time or effort doing. And it's doesn't always feel like the most valuable part of what I do. It's just sort of the way that I express the solutions I come up with. That's really interesting.
That's sort of division between the sort of deeper thinking and the just mechanically turning it into code. How do you feel about maybe the idea that that's sort of the perfect niche for tooling like AI to say, you're still doing a lot of the planning and thinking, but the conversion into text instead of you typing things, some of the program doesn't, whether it's, you know, maybe it's in LLM, but maybe it could also be some sort of more deterministic program that converts plan into code. I'm sort of an AI skeptic, such hater, to be honest, but I've been trying to be open minded about it. And I'm not totally, you know, it's not like I've never asked Chet GPT, why on earth is this not doing what I wanted to do? For me, I think, which might sound contradictory to what I just said, but like, although it is a small part of what I do, I feel like it's an important part of what I do, both because I kind of enjoy it.
And because sometimes good thinking happens while you're doing the typing and the writing. Maybe the idea that you can't separate the sort of lower level coding from the higher level thinking, they have to be interleaved with each other. Yeah, I said I don't really call myself a coder or a programmer, but I also like, at least in the spaces where I've worked, there's not been anybody that I would refer to as that, right? Everybody who is writing the code is also thinking deeply about it. And they're pretty intertwined.
I think doing the designing and then passing it off to a tool to implement it feels weird to me. And it feels weird sort of in the same way that it would feel weird to like do all the planning and then pass it off to like a junior developer. You're like, I'm doing all the good decisions, you go implement this. And it feels like, I don't know, a weird separation that makes me uncomfortable for ways and reasons of having trouble expressing. So that sort of seems to go back almost again to that early 2000s dream of a like deep thinker is going to create UML diagrams for how the software is going to work.
And then either some deterministic program converts that into software or a more junior person is just doing the coding part of it. But the design is not up front through sort of rigorous diagramming. So that sort of view of software is one that you tend to shy away from. Yeah. And it sort of aligns with like the idea of waterfall software development, which, you know, taken to its extreme is like a big chunk of time planning and a completely separate big chunk of time implementing and then a completely separate big chunk of time testing.
And I don't like that at all. I know that there are industries and even niches of software where that is the best way to do it. But I feel like all of the parts that have to be more intertwined and cyclical for you to really address what you're trying to do because almost never is your final product the same as what you went into it. I think you were going to build. And so if I design the first idea and then hand it off to a tool to implement when it comes back to me, it's either not really going to be what I thought it was or it's going to be exactly what I thought it was and I'm going to realize this is what I need, which if I've been implementing it myself, might have, I might have come to that realization pretty early on and been able to, you know, adjust my path as I went rather than wait for the tool to give it back to me and then realize what's wrong.
So I guess I really like the tight feedback loop that happens in my own brain when I am designing and implementing or that happens in a conversation when I'm pairing with someone and we're designing and implementing at the same time. I think what I'm hearing is that you're not a fan of waterfall taken to extreme, but you are a fan of extreme programming. Don't put words in my mouth. Sorry, that that plan was too good to pass out. Yeah, that was good.
Yeah. Have you experimented all with something like that with like you, the human doing the design and then using a tool to sort of implement what you've come up with? I think I tend to sometimes naturally do that on my own where I will sometimes, like you said, do some diagramming up front, do various analysis techniques to help me like break down some more nebulous requirements into like actually, how do I want to solve this? So for example, if I'm working with a UI that's going to have a bunch of sort of complicated states, I have to think about, I might sketch out a state machine diagram that helps me think about what about the empty state? What about the error state?
Things like that. So in a way, that's at least giving me broad parameters to work in. Yeah. I have been experimenting with some LLM tools, particularly ones that have a planning mode and that can be really interesting. So you have this sort of back and forth conversation where you're building up a plan of sort of what you want the behavior to be, how you want to accomplish it.
And then once you're happy with the plan, you let the LM execute it. And so you do get some of those feedback cycles in the planning mode, but then you can let the agent run and execute the plan once you're done. So it's a little bit of a little bit of both worlds. I'm still working on finding a flow that works really well for me, but it's been, I think a pretty interesting way to approach the ISA development. Yeah, I think my reluctance to use a tool like that is also, you know, I will admit, I do like to control things.
And it feels like letting go of some control. But I think it's also just, I don't want to outsource part of the job that I enjoy to a tool. That's fair. And part of what I enjoy is doing a lot of little different kinds of things throughout the day. So, you know, spending an hour coding something and then sometime thinking about it and then sometime talking to somebody about it or writing about it and then going back to coding or testing keeps me engaged.
Whereas I think if I had to focus on a, you know, one piece of it and then get a tool to do some of the other pieces of it, I would be a little bit bored, I think, we're frustrated. So the coder program or side of things is not sort of the all encompassing title, but it's definitely a part of what you do and you definitely identify with that. Yeah, I think so. And I do sometimes identify with engineer and I do sometimes identify with developer, although for someone outside of the industry, when you're talking to them, that can be confusing. And depending on where they're from, they think you're either, you know, building shopping malls or raising money for a nonprofit, which are development in different ways.
Are there any titles from other industries that you wish that we borrowed? I don't know. I'm trying to think it's like the things that we do, we plan things, we design systems or solutions. We implement those. I think also though, a lot of the human side of what we do is hugely important, as far as like, you know, working with a client or if you're not a consultant, a stakeholder and listening to what they are asking for and knowing how to have a conversation with them to determine what you really should be building, you know, which sometimes is what they were asking for, but usually isn't and solving problems and finding pain points and figuring out what will make a human's life better or easier or more fun or happier or all sort of like vague, squishy parts of the job that I think are, don't feel encompassed in any of the titles that we have for it.
Yeah. I know that the agile movement in general sort of moved, like you were saying away from that distinction of like plan or implementer and tended to prefer taking more inspiration from traditional trades and crafts where I think the idea is that you blend some of those roles together and implementation is like you were saying intermixed with planning with the deeper thinking. Yeah. So in some ways we are pulling from the crafting tradition in the way that we think of ourselves as people who write code rebuild for the web. Yeah, I think just like in crafting or any sort of like creation of a physical object, there are some places where people do both parts, you know, they plan and design and then also implement.
And there are also places where those are really separated. I want to be an artisanal coder, I guess. I just want, you know, custom designed handmade websites. Yeah. Need that organic Ruby.
Yes. Yes. Farm to table. Queries. So we talked about for our industry development in general, but I want to focus a little bit of our on our role as consulting developers at the bot.
Yeah. Because the bot as an agency that clients hire us our role as always exactly what you expect from just a random developer in our industry. How would you describe maybe some of the extra parts of the role as a consulting developer? That's a really good question. I think I think when I go into an engagement with a new client, ultimately, like the big vague overarching goal is honestly to get them to a point where they don't need me anymore.
A successful engagement with the client ends with them being able to carry on with their business and their application without me, which means that it's a lot of the same work that you do as a developer when you're not consulting, but it's also a lot more of the human work. So I, you know, want to work with whoever I'm working with to determine what problems you're trying to solve and how can we solve those and design those solutions to implement them. But I also want to share as much about my process as I can with the people that I'm working with, whether they are developers or startup founders or product managers or whatever, the things that I do to help them, I try to also make sure I either am teaching them how to do themselves or am teaching them how I approach them and hopefully enabling them to evaluate the same kind of work and other people.
Gosh, there's a lot to consulting. My brain is going a little faster than my mouth right now because there's also, you know, sometimes we join a project that's been going on for a while. And so the like business needs are pretty clear and the big problems to solve are maybe more technical or team process wise. But sometimes it's earlier on and part of what we're helping them figure out is like, how do you make this successful? What are you building and why and how is it going to contribute to your goals?
And how can we make sure that we're building the best thing to contribute to your goals and not just you told me what to build and I'm going to implement it and give it back to you. Sort of coming in as someone who has expertise, but also keeps an eye on those broader success metrics. How do we make you the client successful at whatever it is that your business is trying to do? And so yes, our work is shipping features. This is a little bit bigger than that.
Shipping features might be a way to help you reach your goals, but it might also be bringing in outside expertise that you don't have in house yet on specific aspects. So maybe you'd like some expertise on performance work or on structuring large applications or integrating it back in front of it. Or even just a little bit of that more for agile process that, hey, we're building up a business, spinning up a team, but we don't really know how to run a software organization. Yeah. There's a lot of people have great ideas to start a business that needs technology and their great ideas are in totally different industries.
You know, so they've never run a software team before, but they've got all this, you know, expertise in medicine or writing or bicycling or whatever. And so helping them bridge the gap between like what you're an expert at and what you need your team to be an expert at and how to communicate that and how to work in sometimes a totally different way than they've been working in before. I've done engagements where coming in specifically to help with testing, a team that has a lot of expertise in writing code, but maybe doesn't come from a background where testing is a common part of their development cycle and they're looking to introduce that. And so part of my role is to help introduce it to the code base, help introduce best practices, pair with a team, help them pick up some of the sort of the disciplines of writing tests.
I've done other engagements where a team has been sort of very junior heavy and hiring senior people sometimes takes a while. And so there's a gap of maybe six or 12 months where they just need a few extra senior people to help balance how many juniors they have in the organization. And so that's where I come in. I'm here for six, 12 months, sort of filling in a more of a like senior developer team leadish position to fill that gap. But then also it can be a mentoring role where you're taking that time, trying to help lift up those junior developers to hit mid level over the course of a year.
I've been currently on a project with something similar where it's not junior developers, but it is transitioning, they're transitioning from a bunch of microservices in a bunch of different languages to a Rails model. And so they have all these amazing senior developers with experience of various technical stacks and a lot of domain and company experience. And we're helping them switch to Ruby on Rails. So these are developers familiar with other languages who have expertise in other languages. Yeah.
And they've brought you in as not necessarily architecture, the domain expert, but the Ruby expert to help all of this gel together. Yeah. You know, we're doing feature work. We're building alongside them, but also to help sort of guide them to the Ruby way and the feedback and highlight opportunities for taking advantage of some of the cool tricks that Rails can do that you don't know about if you don't know about. So that's been really interesting because it's a different kind of mentoring.
It feels a lot closer to a peer relationship because, you know, some of these people have been doing this far longer than I have. And the depth of their expertise in their area is enormous. And so trying to sort of approach the mentoring in a, I don't know, it just feels like a different angle rather than like teaching someone how to be a developer in general. And Ruby on Rails is what we're using to do that versus teaching someone who knows how to be a developer, how to be a Ruby on Rails developer. It's been interesting.
So now that we're in the opposite relationship, right? Come on to a new project and they're using a stack that you're not familiar with. And so I think part of our job as consultants is we have to be pretty fast at ramping up and pretty fast at picking up new languages. And that means really leaning on the client's team if we're thrown into a stack where we're not familiar with some of the technologies. Yeah.
Actually now that the way you said that makes me think that like a big part of what we do as consultants is help people learn how to learn because I think that's something that we're pretty good at as consultants is learning, right? Because we're always joining a new technology or a new application or a new team or something. I think a lot of the examples that we've talked about are helping a client team member learn something, whether it be a new technology or a new role or just, you know, in general software and how things work. So many dimensions to this. Part mentor, part fast learner, part business person, part product person, part code architect, part therapist sometimes.
It's a lot of good things. It's not surprising we can't think of a word for all of that. Yeah. Yeah. Now it makes sense.
Before we wrap up, I've got one last question I'm serious about. If you were ever to leave Thoughtbot to take a software role at a more traditional product company, what are one or two skills that you think are, I don't want to say unique, but that you have learned through consulting that you think would make you a better product developer and that you'd be like, you know what? That's a really valuable thing that I took from my time at Thoughtbot. Well, I think it is asking good questions are usually also hard and kind of questioning things. Not just saying like, okay, you said duetix, I'm going to do x.
But saying, okay, why are we doing x? Did we think about why? Is there half an x we could do that would be more efficient, you know, get us most of the way they're faster and things like that. Yeah. So being the annoying person in the meeting who won't start asking questions, I think who's that main skill.
It's a good skill to have. And do we get to it? It's not annoying. That's also a skill. Indeed.
On that note, shall we wrap up? Yeah, I think so.