IndieRails

Robby (clip): These are problems way beyond Ruby on Rails or Laravel or any of this stuff. This is geopolitical issues. Humanity is having this moment.

Jeremy & Jess (intro): Hey everybody, I'm Jeremy. And I'm Jess. And we're two developers, business owners, and friends exploring the world of independent business and Rails. Welcome to IndieRails.

Jess: All right, everyone, welcome to another episode of IndieRails. Today we are recording live from day two at Rails World in Austin in 2026, right?

Jeremy: Yeah.

Jess: So we've been on a blur here. We've been going from talk to talk and just hitting so many people, but we're lucky enough to bring in a couple of guests.

Jess: We have Matt Swanson of Arrows and we have Robby Russell of Planet Argon.

Jeremy: Hey guys.

Matt: Yeehaw.

Robby: Hello. Yeehaw.

Jeremy: Howdy, partners. I guess that's how we talk down here now. Yeah, I guess so. Is that what it is?

Jess: Yeah. And thank you guys for joining us because I think, like, Jeremy and I both just talked about how our brains are just full of stuff.

Jess: And I think we would, it would be a slow podcast if we were just sitting here ourselves trying to think about what to reflect on.

Jess: So hopefully you guys can spur the juices and get us going with your insights and feedback as well.

Jeremy: Helps to bring on people that are also podcasters, I think. Yes.

Robby: Yeah.

Jeremy: Other talkers.

Robby: I'm used to asking people questions. Yeah. So give me a spare—

Matt: All right. So thumbs up, thumbs middle, thumbs down.

Jeremy: Uh-huh.

Matt: David's keynote.

Jeremy: What if we didn't go to David's keynote?

Matt: Well, then you're going to have to take a guess.

Robby: Okay. Thumbs middle. Did anyone not go to the keynote? I did not. You were not there?

Jeremy: I was there. I was there. That was front row.

Jess: Yeah, I was there.

Jeremy: I'm going to go thumbs up. Yeah. Okay.

Matt: I think a keynote should be energizing. It should be inspirational. I don't think it should be something that you don't have an opinion on.

Matt: So whether you took good or bad from it, I think that did the job of a keynote.

Jess: It definitely did the job of getting people talking.

Robby: Yeah.

Jess: Not just at Rails World.

Robby: No.

Jess: Yeah, yeah.

Robby: I also give it a thumbs up. And I don't think the energy going into the conference, say even the day before, there was already the anxiety of AIs. It's already there.

Robby: So I think some people were hoping for a relief valve. And that's not what he delivered. And so I think it's okay for him to come out and share his perspective.

Robby: But he also comes at running a business in a very different way than most of us are living in. Most of us are not in an environment where we're rebuilding our apps every few years and starting from scratch over and over and over.

Robby: Most of us are taking care of software that's been around for a while. So as a counterbalance, that's what most of us are doing. So that's what he's doing. And we can learn from that and watch him do things like that.

Robby: But it doesn't mean we're all in the same boat.

Jeremy: Yeah, totally.

Matt: Well, I think the strength of Rails has always been that the framework itself is extracted from businesses and real projects.

Jeremy: And what comes with that maybe is not always said is that those businesses were operating in a certain context.

Matt: And so while it's great to get contributions from GitHub, if you don't run a business that's shaped or scaled like GitHub, you maybe don't have the same problems.

Matt: And, you know, certainly things do scale down to smaller companies in smaller situations.

Jeremy: But that's not always the case. And that's fine.

Matt: You know, I think that's something to take away, especially this week is there's good to take away.

Matt: But you have to apply it to your own business, your own team, your own individual sense of what my day-to-day work is.

Matt: And I don't know, there's like an interesting parallel probably because the thing that I think people get excited about with agents is that they have the context of your code base, your business a little bit.

Matt: So in a way, I think like more people should be probably thinking about thinking about that and maybe that is more of the future of some software is like, you know, a great example I think is Mike's CVE skill.

Matt: It was you take that and put it into your context of your project and you get a great result versus him trying to say, well, this is what we did at Basecamp to analyze this incident.

Matt: It's like, well, I don't have my servers on AWS, so before he kind of like couldn't do that. So that to me is kind of like the vibe I'm taking away from it.

Jeremy: Anything that you think you'll apply back at Arrows from so far that you've seen?

Matt: I think I was not terribly surprised by the direction that things were going because I think I was sort of feeling that myself. Yeah. You know, it started the summer and so I don't know.

Matt: I mean, I think we've been more willing to reevaluate decisions that we made about the tools we're using. We're still, you know, mainly building on Rails.

Matt: I don't know that I'm going home and immediately rewriting the back end or anything, but I think for us it's been more like we're more open to being more ambitious than we were before. We have a team of two people.

Matt: And so before that meant tradeoffs like we're going to use Hotwire because we don't want a two language tool chain. But now it's like, well, we're more willing to do that.

Matt: So you kind of have to reevaluate some of the stuff.

Robby: That sounds healthy. Yeah.

Jeremy: Yeah. Yeah. I wasn't even thinking about that. Like I even when they were doing the CFP and I submitted a Hotwire, you know, talk and then it got accepted in the intervening months.

Jeremy: It feels less and less relevant in some ways. I still like Hotwire in some ways, but it does feel like, OK, was that worth doing?

Matt: It's hard. Like, what is the shape of conferences? It's like, I'm sure there's still value in getting together with people talking about practices and things that have worked for you.

Matt: So maybe it just maybe it just shifts and, you know, it's not so much that everything is wrapped up with a language or a tool as the glue that's holding people together.

Matt: It is more of practices or some different identity or something like that.

Jeremy: So for me, it's the friends I made along the way. Exactly. Right. How about you, Robby? Well, actually, before we get into that, I really liked your keynote.

Robby: It was great. Thank you.

Jeremy: I appreciate that. Yeah. It's a good thing to hear.

Jess: I'm curious how long. For the listener, do you want to try to get a TLDR on it?

Robby: Yeah. OK, TLDR.

Jeremy: Tell me more about my talk. Let me try to do that.

Jeremy: Robby, yeah, I feel like I resonate with where you're coming from a lot just because I'm thinking in terms of consulting a lot. And I know that's what you do with Planet Argon. You've been in that space a long, long time.

Jeremy: And you kind of set the stage of thinking about people's workshop and like the environment that we're in, which we're building and how important that is to what comes out of out of the workshop.

Jeremy: And now it's not just the workshop designed for humans, but also for these agents. And I guess I heard a lot of things that were about what was good for often for people.

Jeremy: Sometimes now like there's even more incentive or like more like alignment with the business to say, oh, you know, what's good for, you know, token usage is good for, you know, for us.

Jeremy: And so some in some ways, I don't know, I guess the whole concept of maintainable software, like I felt that coming through from from you, but also applied and it's going to be a new era that that still matters.

Jeremy: So I think it does. I still care about that and it was good to hear.

Robby: Thank you. Yeah, I think the, you know, my spending my good portion of my summer thinking about this and what does it mean to show up and do work?

Robby: And I think we often find ourselves looking at metrics and engineering teams that are related to like number of issues closed, bug fix, you know, how often your PR is getting merged, deployments.

Robby: Yeah, I think these kind of, and there's, those are all metrics that are really kind of easy to, to measure, which is why they get measured. And that's how we compare ourselves and, or see how much more productive our team is.

Robby: But when you talk with a lot of teams that are struggling right now because their PRs are getting bigger and messier and everybody's afraid like to ship things.

Robby: And I'm like, well, is it the code that's the thing that you're afraid to merge? Or is it that your production environment won't protect you from mistakes?

Robby: And how do we, where do we need to be thinking more?

Robby: Like does having, say, an agent help out with shipping stuff or regardless of agents or other human beings shipping more stuff, if you add a bunch more engineers all of a sudden, you lose a little bit of context.

Robby: Yes, but then how do you just make sure that you're focusing on making sure that your overall platform, your workshop is, uh, as safe to make mistakes in. Right. And cause you're going to make mistakes. Yeah. Agents makes mistakes. We make mistakes.

Robby: We just, we have a sense of feeling accountable to the work that we're shipping. And so that's why we're, people are nervous about like, well, if I approve this PR and I didn't really understand it, that's a problem.

Robby: Cause I'm on the hook for it still, that might be arguable because maybe agents are allowed to apparently just hack Ruby gems or whatever. And nobody seems to be getting in trouble for that.

Jeremy: I don't understand. It does feel like there's a re, uh, like a renegotiation around the, um, accountability for developing software.

Robby: And I don't know what that means.

Jeremy: Yeah. Like, uh, if Claude built this and I can go to the business owner and say, shrug my shoulders and be like, I'm sorry. Like Claude did that.

Robby: Like, that's not me.

Jeremy: I didn't write that. Yeah. Uh, so sorry, but it's not my fault. Yeah. In some ways it feels a little bit like that. And almost like the business owners are saying, yeah, that's okay.

Robby: As long as we go faster and it's cheaper. Yeah. I think that's, I think that's accurate. I, well, they, until something goes wrong. Right. And they're like, let's make sure this never happens again. Right.

Robby: And so, and then everybody gets paranoid and then you start adding all these checkpoints and slows down your pipeline again.

Robby: So I, uh, think about, so anyways, my, a big part of my talk was talking about, yeah, like the workshop and we want to encourage people to like spend some time.

Robby: I'm improving their workshops and building tools that, that your agents can use, that your coworkers can use.

Robby: Just, I think there's, we, I think if, if we're able to hand off a lot of these other types of things, whether or not you enjoy handwriting code or not, write features or work on bug fixes, do you have a little bit more capacity to spend more of that time focusing on things that you're curious about improving for yourself or for your coworkers?

Robby: And I think if you can channel some of that anxiety into something productive, I think that's actually maybe a healthy thing. And I think that will make you more valuable for that organization. Yeah.

Robby: Um, if you're the one doing that stuff and a lot of organizations don't have a dedicated platform team to focus on those types of things. So who does that when you're a team of three people or 20 people and, you know, maybe Matt can speak to that.

Robby: Like how do you think about that? Do you, you're like, as you said, you were able to spend more time maybe even using different tech stacks that we wouldn't normally ever touch because like, I don't actually need to know. Yeah. I know how it's, I know it's running.

Robby: We've got some analytics here or something, but like some people are still like nervous or they don't feel like they have the authority to just start doing stuff.

Robby: And I don't know, I, maybe cause I am also a business owner. I have that perspective.

Jeremy: I'm like, just fucking do it.

Robby: Yeah. Just do it. Just, just make your job easier.

Matt: Make, make everybody else's job easier. I like to think, I think I like the motto that's like, if something is painful, you should do it more. And like, that's where, that's where growth is. Right.

Matt: And so it's, you know, in that is like, yeah, something is painful. Right. It, you know, but you have to push through or like experience the pain. I know Jeremy was talking a lot in his Hotwire talk about like, you have to sample.

Matt: The hot sauce. Take a bite and feel the burn. Yeah. Feel the burn. Right. Yeah. And it's the same. I think it's the same for a lot of this stuff.

Matt: Like on our team, uh, we have a designer and I've been pushing and maybe pushing too aggressively, but to say like, you've designed this, like we, we, we were all on board with it.

Matt: Like you should go just implement it and even not just implement it.

Robby: Like you should just push it.

Matt: Yeah. Nice. Because I think it's natural for, for a designer who even is willing and eager to implement, to just say like, Oh, I implemented it.

Matt: But like, I still want the engineers to sign off on it. And I think it's our job as the engineers to, uh, say, no, you push it. And if something bad happens, we need to fix whatever bad, right?

Matt: Is it, is it, Oh, it got deployed and it, it blew up, had weird performance characteristics because you didn't understand the database querying stuff.

Matt: And it's like, okay, well that's something that we can solve and move the knowledge out of the engineering team into like the product or the, you know, the workshop, the factory, whatever metaphor you want, you want to use.

Matt: And to do that is like hard, right? Because you have to admit that something will go bad. Yeah. I've struggled myself with this of like, I, for a long time in my career, like I would feel bad if I shipped a bug, right?

Matt: Because it's like, I'm tying my identity to this, yeah, to this job and this thing. And it's like, Oh, I did bad. Like I am bad. Right.

Matt: And yeah, like that's obviously, you know, it can sound silly if you zoom out or see someone else say that like, Oh, I shipped this bug.

Jeremy: Like I'm such a bad person.

Matt: Like, what are you talking about? It's just, it's just the code. But I think getting over that and realizing that like, instead of, you know, feeling bad about that or feeling anxious or like, this is going to be painful to not review code or not look at code.

Matt: It's like, you'll feel the pain and then you can, you know, use your engineering skills to fix that. And then you're going to end up in a, in a hopefully better, better spot.

Jess: Yeah. Like the talking about the pain or the annoyance, right? Um, you know, cause agents are not going to remember things.

Jess: So if, if you have to tell it over and over again, the same thing, like how to fix something that blew up or just how to remember to do something correctly, then hopefully then I think this is part of your topic was to document those things so that it doesn't happen again and that the agents can see it and take the right path.

Jess: Um, another thing I was going to ask is tell me the title of your talk again. The most valuable engineer is not shipping features or something like that.

Jess: So when I first heard that title, I assumed that, um, it was going to be about, uh, engineers being like more managers, like more product engineers.

Jess: And cause that's kind of partly of where my personal role has gone over the past year or so.

Jess: So, but I was surprised to see, and it made a lot of sense that it was not that you weren't working on the app.

Jess: It, it was that instead of pushing the glamorous feature, you were, you were fixing the thing that enabled people to continue to build and, and make features.

Robby: And that whole perspective is just thinking about like, Hey, don't wait to get promoted to be responsible for these things. Like I think a lot of companies, like there's not a role specifically for that.

Robby: So just become that person that's making, that's helping your coworkers or your agents ship features more smoothly. And, and I don't think we have the answer.

Robby: I knew that when I was preparing this talk, I could not give like a very prescriptive answer. Like, here's how you organize your things for Claude Code to do this the right way. Cause the stuff is moving under our feet.

Robby: So I think those are the problems we need to like spend some time thinking about and look a little bit, I can't say, is that more downstream as you think about your environment or what can we learn from these bigger companies?

Robby: And like, how are they, it's, it's great that Fin is able to have 40% of their PRs get automatically approved and just shipped without a human reviewing them. Most of us aren't there yet. So what could we be?

Robby: And like, I think that's a good question to be asking ourselves. And I'm like, what, what we're having the conversation with our own team. I'm like, why am I reviewing this PR that your Claude wrote with my Claude at some point?

Jess: I'm like, you're not even using different LLMs.

Robby: No. I'm like, what we're like, why do we do PRs the way we do? I heard one person talk, uh, how they were thinking about PRs with including details. To assign to the bots.

Robby: So like after your agent deploys something that it then also has the instructions on how to validate or verify what said, like what is supposed to happen in production.

Robby: So it actually had followup tasks to verify. And if not, then like try to roll back or something. And I'm like, we need, we need to have some interesting creative ideas.

Robby: Cause I don't think the tooling is there to support that quite yet. And there's no frameworks or platforms that are like, use that one specific thing.

Robby: And I think there's a lot of people that are really good at optimizing for one person knowing it like, this is my factory. Yeah.

Robby: But when most of us are playing team sports and we're like, we're figuring this stuff out.

Matt: Yeah. I think some of the anxiety is around like, oh, there's no practices. Everything's out the window. I don't know what to do. And I don't, I don't know that that's actually true.

Matt: I think a lot of times you can look at what we had in the past as a practice and you can almost even just one-to-one instead of a coworker was supposed to do this.

Matt: It's like an agent was supposed to do this. And you know, if that gives you some stability or some sense of the thing, like, I think that is an interesting path for people that are feeling anxious or like, I don't know what the process is.

Matt: It's almost like, well, you can just still do the process.

Matt: I think the difference is that an agent is like actually the most obedient, the most reliable of a coworker in, in some sense, like if you can figure out what, if whatever tooling happens to be of the month or whatever, something that says when you submit code, like you need to test it in all browsers, you need to test it on mobile.

Matt: You need to record a video of you showing me that you clicked through, like that is going to be better than a regular teammate, maybe not on their best day as a teammate, but certainly on their, on their median day.

Matt: Right. And like, I'm guilty of this too. Like there's times when, you know, we've all written a feature. Code looks good. And then you realize you've shipped it and you're like, oh, I didn't actually go in and continually test this. Right.

Matt: Even if I wrote unit tests, even if I wrote system tests and all that.

Matt: And so I think that's like an interesting foothold for people that are, that are struggling with some of this is like, you don't have to necessarily throw out all your practices, but like maybe there's changes you need to make to allow an agent to just follow your practice.

Jeremy: So yeah. Yeah. I think it's hard to, I was thinking about kind of what you were saying about taking responsibility.

Jeremy: I think early in my career, I realized that the key for my growth was to take more and more responsibility of more than my bosses were telling me to, to go ahead and like, you know, document in every incidents that we had in production, but even when they didn't ask, even when they didn't know to, to do that or realize that the site had been down or something like that, but I wouldn't, I'm going to do this practice.

Jeremy: And then that made me better. And so everything that I've been pushing for and been rewarded by for decades has been take more responsibility, do more, take on more.

Jeremy: And now this feels, it feels like a little bit like, uh, now it'd be less responsible. And I know you're saying, don't, that's not what it means, but it, it's what it feels like.

Jeremy: It's like, you know what, throw it all out. Who cares anymore? You know, like I can just blame the bots, you know, I can just like tell the clankers to do this stuff.

Jeremy: I don't have to look at it and it means like all the things that I've been rewarded around for years and everything that made me feel good about what I was doing goes away.

Matt: And what, what's the point?

Jeremy: And change on a dime, right? Yeah, right. Yeah. Yeah.

Jess: Overnight, one year, let's change it all around. Well, you can do that if you're building a personal calculator tool, but maybe not if you have a 10 year old production app that customers that pay you hundreds of thousands a year.

Robby: That's true. You know? Yeah.

Jeremy: They don't even know what Rust is. That's like a thing, right?

Matt: They know what Rust is. They know what Rust is, but yeah. So I think people are imagining that now, you know, we have to change so quickly or like there's so much turmoil. And is it, is it just about the rate of change?

Matt: Because we've always had the issue of tech that we've always had the legacy app that is not on the latest Rails. And, you know, but it felt like people were not coming to Rails World, seeing a new Rails feature, going back.

Matt: My Rails app is three versions behind and having like an existential crisis. It was more just like, this is the reality. And, you know, maybe that's the spark you need to, you know, start pushing that boulder up the hill.

Matt: So I'm just curious if anyone, is that, is that really the, the difference is just the speed or are we, is there something other, other than that, that is causing the more existential questions?

Jeremy: Well, there is a speed at which like humans can't survive. Like there are speeds you pass out, you know, uh, physically.

Jeremy: And I feel like, uh, that's like, yes, it can be speed, but after a certain point, it's not linear, right? It's like, yeah.

Jeremy: And the effects on a, on the, are just the cognitive load and the difficulty around managing that becomes, so it might just be, but I think there is a threshold to handle, uh, you know, a rate of change to handle it after which, uh, becomes just untenable.

Matt: So I don't know if, if there is something else other than that, but I get, I hear what you're saying. I do hear what you're saying. I'm curious, Robby, because a lot of your work is legacy systems and upgrades and things like that of what, what your take would be.

Robby: The, I'm trying to, I don't know that I fully understand your question, Matt.

Robby: Uh, and so I, I don't think I can answer it to the fidelity that I would like to, I would say just with like the existential dread or that the feeling that people have, I'm like, this isn't a programming problem.

Robby: Like this is way beyond, I think if we're in some ways, I think we're like navel gazing a little too much and be like, this isn't just us. Like this is a lot of people in a lot of careers and a lot of industries.

Robby: And like, they're like, am I going to have a job in customer support? You know? And it's like, do I have to start driving a Uber? Maybe that's how you, and then we're in Austin and they're like, that's not a thing.

Robby: And so just like all these like kind of fail safe things, like, well, in a, in a pinch, I'll start delivering food. And they're like, well, there's going to be a bot for that.

Robby: And so it's like, yeah, I think this is the existential thing is more on a macro level, way beyond just like whatever our, you know, benevolent, uh, Rails person, you know, has to say on his top.

Robby: I mean, like, I think people are just looking for something to, we, we feel like a interesting connection to the people that we work with and have a little bit of a, like why I met these people at this conference.

Robby: I've seen them speak so I can feel a certain way about how they are talking about change in our industry and I can reject that because it feels, but like, these are problems way beyond Ruby on Rails or Laravel or any of this stuff.

Robby: This is, this is geopolitical issues. Humanity is having this moment. And so I don't know how to, I don't know how to have that conversation. So I can be like, where, where am I?

Robby: I'm working on these apps that I know clients are paying for me right now to, to have my team work on them and they're just like, Hey, this is what we're working on over the next three to six months.

Robby: Like they're, those companies are having their own existential crisis of like, where's, what's their company going to look like? How do they stay in business? So we're those kind of like, we have a mutual shared, let's not all fail together. Yeah.

Robby: And then of course we can get into the economics of AI companies and our retirement programs and plan— pensions all getting attached to them. And so we're also have to see these things be successful. Otherwise we're screwed. Yeah.

Robby: We didn't sign up for that necessarily, but we also didn't, I don't know. It's a weird, I didn't, I don't know. Yeah. So I can spin out if I spend that. I'm like, all right, well, I guess I'll try to lean in on the optimism a little bit.

Robby: I'm like, well, we saw, we still got our workshops to take care of, workshops to take care of.

Robby: Let's just work on some small improvements here and there and just keep learning and having conversations and try to remember that we're a bunch of humans trying to figure this stuff out.

Jeremy: Yeah.

Matt: I think you're right. And maybe, maybe if I can somewhat summarize, it's like, it's not just the speed, it's the scope. Right.

Matt: So maybe in the past, it's like, you've come out of a RailsConf and you have tech debt and it's in maybe one area, but it's like, in the scope of your project now, it's like everything. Everyone's like, reevaluate, everything. Yeah. Right. Yeah. Everything.

Matt: And, and Robby, you're correct that the scope expands even out of our programming, out of my particular day job into the whole company to, you know, your friends and family and their company and the economy as a whole.

Matt: So, and so maybe, you know, I think that's a good perspective that maybe that is the thing that is causing the dread is maybe not, not just the speed, it's the scope of it.

Robby: Yeah. We're in interesting times. Uh, maybe we'll look back and be like, it was great to, we got to live through that era. And I don't, I don't know.

Robby: Uh, I didn't, it's funny cause I joined, I got into this industry, not thinking that it was as, as a hobby thing. And then I, people would start paying me for it.

Jess: Yeah.

Robby: And now 25 years later, almost it's like, might that not be a thing anymore at some point? And I'm like, am I owed this? I'm like, look at all the work I did to get to this point. I'm like, I didn't go to college for this. I never had any college debt.

Robby: I I'm just been like kind of fumbling my way through this career for a long time. So I'm just like, I'm happy to still kind of be around, I guess. And that's cool.

Jeremy: Um, but it's not guaranteed to be a thing forever. Yeah. I'm definitely grateful. Similar thing. Like, didn't think this was going to be my career. Just like it was my hobby.

Jeremy: And then I found out I could make money at it and I loved it and I couldn't stop. Uh, and then turned out, you know, like I could make a career out of this 25 years later. I'm very grateful. And if that's what that is, then it's worth it. Absolutely.

Jeremy: I would be sad to lose it, but it's still good enough. And a lot of people hate their jobs. I know so many people that just hate what they do. And I've loved what I've done for a long, long time.

Jess: So I know I consider myself. So I'll switch topics a little bit.

Jess: Um, cause I don't know if I've heard anybody talking about this, but I've experienced it within our companies is that, you know, we talk about the speed, the AI with agents and how we can push more code, but then that creates a bottleneck in the PR.

Jess: But now everybody's getting comfortable with like just pushing PRs and not reviewing those. But one thing I'm running into is that my customers can't keep up with the features.

Jess: So like there's, that's, that's another problem to solve is, uh, what, what are you building? And, and, uh, are you making the right choices? Like you have all this power now to build these features. Yeah.

Jess: Are you, are you building the right things? Are you building the things that your customers need? Can they even absorb those things? Because they have a hundred other things to do in their business and their workflows.

Jess: And they're like, Oh, I'll, I'll even like try to do some customer research. I'll call them up and say, Hey, have you tried this new feature?

Jeremy: No, I hadn't, I hadn't had time to try it yet.

Jeremy: Uh, let me attach onto that, not just customers, but I have a friend here who was telling me last night that, um, he's, he runs a small, uh, team for a product and he told the CEO, uh, like recently we're, uh, we're running our, our backlog, our bug backlog down to zero.

Jeremy: Uh, you've got like weeks left until we're coming, knocking on your door saying like, what are the next features?

Jeremy: Cause we're like getting down to zero bugs and like that we like needed to deal with.

Jeremy: And so like all, like that's completely changed, you know, like the, the owner of the business CEO or whatever you like, he's a thought, like, you know, I've got ears or whatever to like deal with this or like, I can always stay out in front.

Jeremy: And now the team has progressed to a point where they're going to be knocking on the door very soon saying, what are we building now?

Jeremy: So it's like both business owners and customers, how do they stay out in front of what can happen there? I I've not experienced that so far. Like I'm definitely seeing higher velocity.

Jess: I have personally felt that like with client work, but, um, it seems like that might be happening more.

Matt: Yeah. Are y'all seeing any of that at arrows? We're in kind of a different spot.

Matt: Cause we, at the start of the year, basically started a new product and in a way we, we felt that like we needed to like rethink what we were offering, given that we can see maybe some trajectory in other industries from what has happened in the software industry.

Matt: So I don't know yet. I think we're still, we're still finding our customers and we're still, you know, obviously we are shipping things out much more quickly, but I think that's also the nature of being early. Right.

Matt: And, and we have pilots that are going on and we have customers in Slack that are telling us what's not working. And, you know, we're turning around and shipping things, you know, in a few hours.

Matt: But, uh, to be honest, that was not a new thing necessarily when you're early. Right. And with Rails, you could always kind of turn things around more quickly than people expected.

Matt: If you were making small changes, if you sort of, uh, didn't have a bunch of existing data or existing customers or existing workflows or, you know, that, that sort of thing.

Matt: So I don't, I don't know that we've, we've seen that yet, but, um, I think it definitely is going to be a thing for people.

Matt: Like it's always hard to get people to adopt new processes, software developers in this industry is, uh, these are folks that love doing that almost. Yeah.

Matt: And, and certainly, you know, uh, a more regular business person is not, is not, you know, that hyped on it. I'm sure if you go talk to them, they're like, Oh, are you using AI in your business? And it's like, Oh yeah.

Matt: I searched with, with Claude or I, I, I chat with, you know, ChatGPT or something in a way you're, we're sort of privileged in that we are almost like, you know, two years ahead of some of the other, the other fields.

Robby: And so maybe that's part of, uh, what your advantage can be is, it's bringing that, yeah, bringing that back in my, in my space, the, uh, because we, we work on a lot of, uh, retainers with clients.

Robby: So we kind of like a approximate budget we work with them each month. And so we've usually been able to kind of like scope that in a way that that's kind of based off of the capacity of our clients.

Robby: Like when I say capacity of like their, not just budget, but like mental capacity and attention because quite often clients end up being a bottleneck and that's historically been an issue for us.

Robby: Like, like we can, we, yeah, we could build, we could bill you more, but you're going to be a bottleneck unless you have some more people.

Robby: But we know that you're an important person in your company and you can only respond to so many questions and tickets and be part of conversations with us or review something or be a final sign off or something.

Robby: And so I think we've had to learn how to remove them a little bit from needing to be involved in all the approval process.

Robby: So we have to build that trust, which relies on a lot of human letting them know that we understand where their goals are. So be like, Hey, we ship this, it's out there.

Robby: Just want to let you know, FYI, you don't have to do anything like, so we're, we're trying to get our team to think more about like, let's show that it's working in production, take that little video. Yeah. Like, look, it's working. You don't have to think about it.

Robby: Like what, what's, so they don't have to be a final sign off on some of that work.

Robby: But as far as the, the throughput or being able to do more, uh, the, the, how we're using that extra time or capacity with the budgets.

Robby: So if we're able to ship features a little bit faster with our little AI agent buddies, then the questions always end up being more like, okay, how can we, what are the things did we not get a chance to really take care of here? How can we do a more thorough job with this?

Robby: Like how, like, let's go back and our, another question I was talking about, I was mentioning this earlier in a conversation, but I'm always like, if someone else had to come in and review this code base, what things would they highlight that we've, we've been kind of negligent about?

Robby: Because there's probably things where things were our workarounds and I kind of touched on this in my talk a little bit, but I think we have time to do that kind of stuff a little bit more right now.

Robby: But I, I do hear from folks where they're like, great, we got our engineering team. They can, they can push through a lot of things, but we don't know how to market, sell this stuff to people.

Robby: We have a one client that like super, they've got a nice, big, healthy budget and we've built a bunch of stuff with them on a new, we don't do a lot of greenfield projects, but we did work on one this year.

Robby: Um, and which is a fun story because like that was a project that we almost weren't going to get because they weren't sure about moving forward on this project.

Robby: And then our project manager vibe coded an MVP for them and they sent it back and they're like, that sounds exactly like what we want.

Robby: Like our project manager just took that extra initiative and spent like a couple hours, working on a MVP thing and it's been like, I think we made $150,000 on that project so far. So thank you, Michael for that, uh, clever idea there.

Robby: I think the sales process is a little bit different for us now too.

Matt: I think it's been a little bit different for us now.

Robby: Yeah.

Jeremy: Yeah. Yeah.

Robby: And I'm like, well, we can't solve that with AI necessarily. Like, well, where's the customer base? Like, yeah, we can build things really quickly. Yeah. You've got all this stuff there, but like you need to find your customer.

Robby: Like you've got all this stuff there, but like you need to find your customer and that takes time.

Jess: And I think it's going to take a while for, uh, businesses and managers to sort of catch up because they're used to this backlog of things that takes six months to build.

Matt: And, and now there's a different velocity. Yeah.

Matt: Well, and it's part of the job as a software product builder or a business owner is show the value to them in the world and their language that they understand because they ultimately, they didn't care about the technology before.

Matt: They don't really care, but maybe they slightly care if it is AI because that's a hot buzzword that they want to make sure they're not getting left behind.

Matt: But certainly none of your customers care about what model you're using, what harness you're using, what skills you're using. And that's always been the case. Like they don't care what version of a database you're using or what language or framework.

Matt: And, and, and, you know, that, and I think that's, uh, just worth, worth keeping in mind that like, that's part of our job is, is to translate that back. And, you know, this is a transformational technology.

Matt: So of course that means that the, the answers are not well-written, right? I think in the past we could, we could all probably off the cuff.

Matt: You know, describe why a web app might be better than a spreadsheet for some business process.

Robby: Is it?

Matt: Well, depends. Does the spreadsheet have an AI chatbot in it? Yeah. Right.

Matt: But I just think going forward, it's like, it's not yet clear necessarily, like how, how do we best use this technology to help business outcomes and where does all that fit in?

Matt: And so that's just, I think adding a little bit to the, to the uncertainty or the feeling like, Oh, I used to have the answers for how to sell consulting services or to, to, to know what tool to pick.

Jeremy: And now it's just a little fuzzy. Robby, uh, you, um, highlight a new framework in your talk called WUTS I think it's called, is that right?

Robby: Did I pronounce that right? Yes. You got to say it loudly and quickly. WUTS, that's, uh, kind of my need to give a silly name to a sequence of otherwise normal human behaviors.

Robby: Uh, so WUTS is W-U-T-S and it stands for wonder unpack tinker and share. And you can find out more information at wuts.wtf.

Robby: I bought my first .wtf domain name. Nice. And so I'll be sharing some stuff there. I actually was working on some, uh, like Claude skills and stuff for it, but I decided I wasn't going to publish them immediately.

Robby: But I want to test them a little bit more, but the idea is just more about scratching that curiosity it's like when you're working on things, like let's learn more about our infrastructure. Let's learn more about why that one weird thing is doing the thing. Just having a little bit more of a framework.

Robby: That's not tech stack specific. And, um, because I have a tendency just to like jump into solving problems. I like, I love the endorphins of that.

Robby: And I don't always care to understand why things are the way they are. And I think that's also been detrimental for me at times.

Robby: And so I've been, been thinking a lot more about that over the last many months and wanted to try to like give myself a little bit more structure for that.

Jeremy: And I thought I would share it and see if it resonated with people. Yeah. That's cool. Yeah. That's interesting. That is like my go-to is to like, try to understand why things are the way.

Jeremy: That's like, just like, why are things this way? Like, uh, yeah, I think like doing tons.

Jeremy: Like I'm the kind of person that before building a feature, I would like do research on like, how, how has everyone solved this, you know, in history before, before even sitting down to implement, that's always like been my approach.

Jeremy: But I know it's not, not everybody.

Robby: Um, and, uh, yeah, just having like, yeah, like being curious and asking those questions and then tracking that stuff down.

Robby: Just, and I, and I was in for, because in the talk, it was more focused towards people that are inheriting code bases or inheriting other people's decisions.

Robby: And that, and a lot of people joining projects don't understand why things are the way they are. They assume that they're the way they are because they should be the way they are. Yeah. And that's not necessarily, uh, uh, I think a healthy way to look at it.

Robby: I think we should be able to question things. You can also not be that annoying question person on a team. That's why did we do it this way?

Jeremy: Why did we do it this way?

Robby: Like, that's not super. So do want to encourage people to like go answer those, some of those questions themselves and not subject your teammate to that.

Robby: Uh, but I do think the, the, the tendency is just to like not ask or to not inquire more.

Robby: And I think, I think right now, because, because AI, I think there's, there's this interesting thing where I think we're, we're going to become less curious. I worry that we'll become less curious and I, I don't think I want to give up that.

Robby: I don't know if that's that skill or value. I think that teams could benefit from right now. Cause I think that will then allow you also just to readapt and think about how your job's going to evolve.

Robby: And again, like be the person that's asking or inquiring or sharing their, that was a big part of it.

Robby: It's not just asking questions, but also then sharing maybe like a tool or useful resources or documentation or play playbook or something like doing a little bit more than just being like, Oh, I figured this out for myself.

Robby: And then I'm going to just going to keep that information in my head. I don't think that's as valuable as just taking that extra step. And like, does everybody else know how to do this now?

Robby: Now our agents can also maybe take advantage of this new tool that we, I built that simplifies things or been set up actually does what expect like, yeah. I know that people are like, what do you use been set up? They're like, no, it doesn't really work the way we work at our office.

Robby: I'm like, you know, it's a bash script, right? Like you can make it do whatever you want. You have complete control. Like why can't you do this in one command? That's true.

Robby: And that just seems like such low hanging fruit that I, I don't know. So I've used that as an illustrative example there, but I, you know, so I just want to encourage people like simplify it for yourself and for your coworkers and for your agents.

Jeremy: Yeah. One thing I've been thinking about a lot, cause I've worked on a lot of legacy code bases for clients.

Jeremy: A lot of times, uh, we're changing direction architecturally, like, and with, especially with Claude and stuff, it's going to keep doing more of what see it already.

Jeremy: And so I've been trying to figure out like, okay, I need to, I've already identified several things that I know we're not going to go with this old pattern, but it exists all these other places in the code base.

Matt: And I need to sort of audit that and then write. No, we're not doing this, but it's also for people.

Jeremy: Like we're not, we've decided not to do things this way anymore.

Jeremy: And we had that conversation, you know, over zoom or whatever, but it never made it into documentation or whatever to say, like, this is, don't look here. Like if you see this, don't copy that. We're not doing any more of that.

Matt: We're not going to remove it right now. Um, but don't do more of it. Yeah.

Matt: I think the interesting thing there is like in the past you had to have a certain team or be a certain size to really justify like automating or writing your own custom dev tooling to do that. Yeah.

Matt: Now a lot of time and energy. Yeah. There's the classic joke of, you know, I, I, I spent eight hours writing the script to save me, you know, 15 minutes. And you know, how many times do you have to run it?

Jess: Right. To pay off.

Matt: Realize that benefit. Yeah. Calculus just changes a lot on that. So like when I hear that, that example, Jeremy, I'm thinking like, yeah, that's great.

Matt: And in the past you would have just told people like, don't like, you know, which are the bad files.

Matt: And, but I don't think we would have really said like, does it really make sense to write an automated script that will reject a commit that if it does it that way, or, or it was simply too difficult. Right.

Matt: Because you didn't have the ability to just, you know, you could have that, you could have some, something run a cheap model check to say like, are you using the old pattern before you, how do you, how do you hard code that in?

Matt: Especially in a language like Ruby where you have, you know, dynamic metaprogramming stuff involved. So I don't know. I think that's just like a good example of like, that is still engineering work. That is still value and judgment in your experience.

Matt: That is still, you're making a decision to do something. You're still applying, you know, the strangler fig pattern or something.

Matt: You're still saying like, oh, I see the value of CI and linting and how can we automate a check so that we remove the human judgment from it. So to me, that's just like, it's more exciting.

Matt: It's definitely different than the day to day, but I don't, I don't think it goes away. I think, you know, for me, the biggest realization of the past several months is that, you know, software is more than just the software construction.

Matt: There's, you know, on one end, there's the product and the user and the user experience. And then on the back end, there's like quality assurance, there's verification, there's rollout, monitoring, all that.

Matt: And, you know, while the software construction in the middle is getting kind of squished, I think engineers will have to choose which direction they head. Yeah.

Matt: And I think, you know, for people that were more into the craft of the code, the technical, like I just, I just like the puzzle solving nature. Like maybe you shift toward verification.

Matt: How do we, how do we, you know, how do I spend my time writing a simulator that can test, you know, this external API integration in an automated way that before we would never do.

Matt: You know, those people can go that way. And people that are more want to focus on the business outcomes or the product thinking, or I don't care about the code. I don't want to look at the code. I can look at the finished app and I can polish the last little bits.

Matt: Like maybe they're shifting more toward. More to the human side. More toward the product. You know, what typically would be a product manager or something like that.

Matt: And, you know, I think that's, that's been my realization and my hope that people will sort of take away from some of this is like the software construction part is maybe going away, but that doesn't mean that the role of software is going away.

Matt: You just need to sort of find something else.

Matt: And, you know, I think once you find that you can achieve some, you know, similar flow state in one of those two domains, I think it becomes a little bit less scary and you can sort of see that the future is, is maybe not as, not as uncertain as you might think.

Robby: Flow state.

Jeremy: That's the thing that's killing me the most. I'm a flow junkie and I lost it this year. Yeah. You know, like my flow's gone. I'm burned out every single day. Like, just like toast. My brain's fried.

Matt: Yeah. Like from so many work streams and stuff. And I miss flow so much. Yeah. And I struggled with that too.

Matt: And like, it's only in the, you know, recent weeks that I've started to have more sessions that are like that, where you can, where you can see, or you get the satisfaction of like, oh, this is cool.

Matt: When I can spin up a cloud agent that records a video of its, of its thing and does a better job, you know, testing and documenting than I, you know, I think eventually something will click.

Matt: I mean, for me, another good example was like, if you've ever tried to debug a customer issue and you've had like a fully realized setup where you give your agent a read-only production database access, you give it access to your, you know, to your AppSignal errors or your, your logs.

Matt: Like just seeing that go, it's hard to go back to it. Yeah.

Matt: I kind of felt like some sense of flow of like, I set up all the pieces in motion and then I watched it go and it was like, it was satisfying my brain in the same way.

Matt: And so hopefully you'll find, you know, something like that, because I think, you know, that, that will be important going forward because, you know, so many people did get into a flow state.

Matt: You're in the headphones, you're, you're, you're, you've got your beautiful editor with your code color scheme, your keyboard, your keyboard switches that you've dialed into perfection and you just go and, and, you know.

Jess: My VIM bindings. Exactly. Yeah.

Jess: I, that reminds me of someone I've read was talking about the term of an architect and how an architect designs a building, they plan the building, but they don't, they're not on the ground doing the work.

Robby: Yeah. And I feel like that's, that's where a lot of us are.

Jess: But they get to put the cool photos on their, their portfolio.

Robby: Exactly. Look what I built. Yeah. Look what I designed.

Matt: The finished product. Yeah. So they take it, you get to take their pride. Yeah. But it's not too different now.

Matt: It's the same, you know, I shipped this feature and you know, whether I wrote the code or not, you're, you're, you're very rarely reporting the code to customers in a, in a release or even to your own team.

Jess: Like we have a release channel where like, Hey, this feature is now live.

Jeremy: You don't tell them what class you wrote to do it. Exactly. Yeah. So. True.

Jess: Well guys, this has been a great conversation.

Robby: Thanks so much. Robby, Matt. Going in the spur of the moment. Yeah.

Matt: Thank you, Jess. Thank you, Jeremy. And thank you, Matt. It's been a delight to chat with you both.

Robby: Buzzsprout for putting the podcast together. Yeah. They always come through. Yeah. They do.