The Adam Sand Report - Thursday, July 30, 2026

What's going on everybody, welcome to the live stream. I do these streams at 9 o'clock at night so if they suck I don't have to worry about having offended anybody because I know that, uh, that these were late at night so it wasn't, uh, taken away from your prime viewing time. But if you're here, what I like to do is I like to run through just coding loops, things I'm working on, using some new set of skills lately I just like to connect with other people who are doing the same. So this is me just building live in public, and it's an opportunity for me to connect with others who might be interested in what we're up to. So that's your kind of thing, would love to chat. If you're hopping in, I'll probably, uh, I'll probably touch base with you, and I'd like to hear what you guys are working on. And if you guys have any questions, or more importantly, if you guys have ways to help me, I would appreciate that. I'd much rather gain from others that know more than me than to pretend I know everything. So yeah, with that, without further ado, we are going to jump in and start sharing our screen. I want to do these lives more during the day at some point, but I just more or less kind of do them to see what happens. We never really know what's actually gonna go down on the live stream, so that's that. All right, so we are going to go to— where are we here? All right, so I use this little coding agent to essentially help me plan out my days. So it's telling me which linear issues we're going to work on today. So last true is 2 out of 3 close, was they a real domain under you Full. Okay, finish ADA 462, design lead modify 157. Okay, payoff from the 448, rebased on the Hosain's main grip loop on draft. Okay, Lane B, January loop. Okay, can you please write the spine in contract, post the spine as a downloadable, um, in the contract? Put the contract on the Linear issue. The spine is sub fourth character prompt. I will initiate 3 sessions in Slack for you to coach along. Should you ever see anything that should not be on a live stream, you know, so I don't get cooked in front of my friends. So I see some people are hopping in. We'd love to know where you guys are from, uh, what you guys are working on, what you guys want to see, if you guys have any questions, or if you guys have any advice. I'd love to hear that, um, and then we'll go from there. So, um, what we are kind of working on so you guys can kind of see it, is this. And right here. So the idea is that most CRMs that you see out there are going to look something like this. Stuff on the left, then information in, in the side, right? So you can see contacts and a contact, you have lists of contacts, you add a contact. So This is like the same bifold thing that everybody else can see. You'll have deals, you have tickets. This is the roofing flow, it depends on which customer you're working in, right? Um, so you're going to see— this is what you're going to see. But I have a concept for something different, which is this, okay? And the idea is, what if What if Tony Stark ran a— when I was running my cleaning business by myself, I was limited to what I could do in a day. I was able to hire or partner. What if Tony Stark ran a cleaning business, a roofing business? This is a question that I would ask.

Where is it?

Right here. What if Tony Stark ran a cleaning business? That's the question.

wireframe.

I need a manipulable projection. 1974 Stark Expo model scan complete, sir.

Uh, how many buildings are there?

Am I to include the Belgian waffle stands?

That was rhetorical. Just show me.

Uh-huh.

Um, what does that look like to you, Jarvis? Not unlike an atom. In which case, please, I'll be here. Highlight the Unisphere. Lucifer pants. Get rid of them.

What is it you're trying to achieve, sir?

I'm discovering, uh, correction, I'm rediscovering a new element. I believe the reason there's landscaping, the shrubbery, the trees, exits, entrances. Structure of protons and neutrons using the pavilions as a framework. Dead for almost 20 years, still taking me to school.

The proposed element should serve as a viable—

so the question being, what if Tony Stark ran a roofing company? Do you think that Tony Stark would sit down in front of his mouse and in front of his keyboard, and he'd go pick up the phone and hold it against his head like this and go, okay, name Adam, last name Sand, email adamsand@email.com. Is that S-A-N-D? Yes, S-A-N-D. Phone number 780-555-1234. No, he— oh, add a deal, click roofing, click Repair, click. Have you filed an insurance claim? Customer has filed an insurance claim. You know, like, that's not how Tony Stark would run a roofing company if he had one. And so how would he do it? Well, I propose that he would do it a little bit like this. He would probably do something a little bit differently. So he wouldn't have a CRM that looks like this, where you've got your deals and you've got your contacts and all this kind of stuff. This is like— anybody can build this. This is super easy. This isn't how Tony Stark would run a roofing company. I believe he would run something like this. And so this is an example of what I think the future of software looks like, is the user interface generates itself. So when you say schedule this week's jobs, it would just allow you to talk through what you want to do. So you— it would— the user interface would generate itself live. So you could just drag the jobs over here and then decisions will be made. If you're in inside sales and the phone rings and you're just like, oh, like this video right now is being live transcribed. Somebody here could click the button on YouTube or LinkedIn or Instagram or wherever this is being streamed, and they could click a button to see the live transcript right? So if this video can be live transcribed, so could a call. So when she says her address is at 4172 Hazelwood Court, why can't it just pull up the Google Maps right there? And if she's describing her problem, why can't it generate an image based on typical roof designs to try and, like, ideate on where the actual leak is? When she says what her email is, why can't it just type the email in itself? Like, why do all of these circumstances not exist today? This is the question. And so when we're talking about— when we're talking about a roofing business and it says like, when we can see that the appointment's here, if we say, hey, does 10 AM work tomorrow? And they say yes, why do we have to click and book the appointment? It's being live transcribed. Every call is So why can't the agents just do the work? Why can't the interface generate itself? If you want to add the weather, why can't we just say, hey, I want to see what the weather's going to be, and have the user interface generate itself so that while you're working, you could also just see the weather? Oh, I don't know what— of course I'm in the middle of making this, so I broke something with the weather. I should check. Of course, of course, could do this. Let's see, um, please add the weather. I've probably broke something in the middle of while working on it because I'm actively building. Yeah, oh, it worked on this one. Okay, perfect. Oh, and the new weather updates have changed, but it does now— should be defaulting to the larger of the, uh, of the buttons. So this is kind of what the weather is going to be looking like. I'm working on what this actually looks like, but this pulls from the live weather API. So why can't the software that you're working with just generate its own user interface live on the go? And so this is literally in the middle of being worked right now. Um, we're building this, and this is something that's live, but that's the whole concept. Is why is it that we have to generate— like, why do we have to work through the typical CRM framework where we're the ones clicking around, jumping inside things? You know, again, this is just, this is just a backend more or less. Like, why do we have to work inside CRMs and user interfaces like this when it could just as easily be like this? And so we're also working on some other stuff like, you know, bringing in, uh, Slack where you can talk with people and agents at the same time. Like, this can just exist inside the CRM, similar to Slack, but also being able to talk with our agents. And the agents do the work. We don't do the clicky clacky moving around. We just make decisions and the user interface generates itself. That's the concept that we're working on. If that sounds like something cool to you, would love to hear you in the chat. Would love to have a conversation with everybody. I would love to see what you're working on. If you guys have ideas, then by all means, throw them out there. Knowing that, let's go back here. Okay. It has been building. Okay, so it's built out. Okay, user sessions. This is— okay, so now I just got to move this for one second. So that I can safely make sure there's nothing showing that shouldn't be.

Alright.

So we have our linear issues created. We have our context. So we're gonna say here, Marcus, this is our— I'll use voice— is our Coding companion session for ADA 462. I will run the prompt in our coding agent, but you will be here to supervise the first spine. Okay, we're going to do another one. So this is a Hermes agent that I co-work with that's just kind of like acts as a partner while I'm doing it, and so I'm just opening up multiple sessions. This is our code coaching session for the second session, which is appearing to be ADA 532, and then we'll go Okay, so we have two session— oh, there we go, ADA 186. This is our third session for tonight, which is working on ADA 186, and we'll serve as a code coaching session so you can keep us on track with the three different lanes.

Okay.

So now I can take my goal prompt right here.

This is—

what is this? This is not anything to do with iOS, correct?

Okay.

Oh, wait a minute. I think I was already working on this. Yes, this is it. Actually, for those of you who in the room are, who are roofers, it would be great to connect with you guys because this is actually highly relevant. This is a, a new prototype for what I'm working on for the production flow. Essentially, the idea is that in the canvas, if I go to production— production, yeah, production manager— and I go schedule this week's jobs, right now if we drag a job onto here, the agents just instantly go to work. So they're ordering the material, right? Because like this is linked to the job, so it's ordering the material, it's scheduling the crew, it's letting the customer know, and it's like moving the stages and everything like that. Like the agents go and do the work. So the problem is that what if you just want to mock up the week and you want to say, oh, you know what, you know what, I don't think we should do John on Saturday, it's, it's too steep of a job, right? I should probably do that next week, right? And then you want to like not have that. So we don't have a way to stage and then trigger the agents to work. So this is an ugly prototype, but what it is is this me saying, okay, So you could— this is, uh, because I was simulating a, simulating a failure, so I'll reset the session. So the idea is like, okay, well, this is it mocked, but now if you want to stage this one over Friday, you'll see they go staged, right? And you can see the modifications that you're making here showing up in this ticker. But the idea is then you'd have your staging tray where you could lock in a number of decisions, or lock in and deploy the batch, and it would then go and trigger the agents to work then. So then now this action is true. So the whole idea is like, would that be a good flow? And the idea is that, what do you need to see? And so the question for the roofers in the room, if you're here, is how do we think in order of magnitude? How do we cut the work that you have to do to feel confident about scheduling a job from 10 minutes down to 1 minute, or from 30 minutes down to 3 minutes. And I actually just remembered I have a good transcript for this that I could go and dig up. And so I should go into our playlists and go to all playlists, go to My courses, and this would have been the one with our buddy Abner. Oh, that's not it. Would it have been this one? Nope. So when is it winning Wednesday? Maybe it was Platform Tuesday. Yes, this would have been the one. So we're going to pull down the transcript. I go— and your comments live would actually be quite helpful with this. We're going to go for the, um, the Canvas demo feedback roofing production. Hey, you— I think you were actually here. This session, Josiah. You actually saw this, so I would love your feedback as well. Okay, and file. Say, um, let's say, review the transcript. Um, what are you working on? View. View the transcript where production, production was discussed. It is provided. And you know what else, where I could give it some context would be if I went into another meeting that I did, which was a production consulting.

I did.

Where was that one? Where did we discuss here? This one would get— would be good.

Go docs.new.

Transcript copy. Ah, production, VP consulting session 2. And let's go back and get the previous one from that. Production, we be consulting session one. We're going to add those and we're going to say prototype. I'll read your comment in a second, Josiah, and then I'll also review two consulting sessions which discuss real-world feedback and issues that happen in real life, real-life roofing production at the $15 million revenue level. And we're probably going to go give it, uh, Hill Estate Max for this. All right, I'm going to come back to the session in Slack. I'm going to give it the same context. All right, building a sweet little tool to keep track of our leadership training. We're doing John Maxwell's 21 Laws of Leadership. I love that. Law of the Lid, Law of the Big Mo, Law of— oh man, Law of the Lid, Law of the Big Mo. Law of Subtraction, I think it is. Like, I, I would love to go back. I remember the 5 Levels of Leadership where it's like position, permission, performance, people development, and pinnacle. But the 21 Laws are hard to—

hard to riff.

We create a workbook for people to fill out each week. We had no way of keeping track of who was finishing on time, who needed to be kicked out of the group because there was bonus for finishing. Super simple way, the link for each week, long, they tap their name Arts and Computer as well as what time. That is awesome, man. That is super cool. I love that. I love that you guys doing— so how are you, how, how are you doing? How, like, what is some cool stuff you're learning about building it? In addition to your prompt, I give it these 3 transcripts. This would be good for you to learn as well because these are, uh, transcripts from 2 consulting sessions that we did with a client who's running production at a $50 million level, doing 5 to 6 jobs per day, as well as a direct feedback session that I did with a client of ours showing him the prototype. Addition. Yes, Navigation Respect. I love that book.

I gotta go back to—

that's one of those books that when you're like young in business and you're like, which business books should I read, it tells you like Win Friends and Influence People and The Power of Thinking Big and, um, the, the, like, Rich Dad Poor Dad. And we'll tell you, like, John Maxwell's 21 Laws of Leadership and Awaken the Giant Within. It's like one of those books, it's like the originals, right? Napoleon Hill, like this kind of stuff. And, uh, it, it kind of like brings you into this, this world where you feel inspired and motivated. And then you— and then like you, you go and you're like, really, it's like, man, those classics, you got to go back to them. Please review and add to the agent vault. This is good context. Or anything product related around building for us a successful production department. No, of course, don't put the links here. I'll take a look while we're absorbing All right, so ADA 462 is underway. Received. It is cranking. All right, now What was the second contract? All right, produce loop and gen 6G conformance fixtures, ADR, do under Docs Assistant, Wayfinder, GRILL docs, not implement runtime, do not, not 8173. Oh, I see you're sending me the photos. Man, simple throwaway software. I love, I love your commitment to it. So you got some Supabase, some Vercel, some Cloudflare, some S3 bucket.

Love it.

Very cool, man. Man, you are an animal.

I love it.

I absolutely love it. Okay, so we are doing a Wayfinder session. Okay, so we probably won't use the goal session— the goal prompt here.

We come here and we'll probably go high.

High is good for a Wayfinder. I would use Opus because I miss Opus 4.8, but Opus 5 has been the absolute bane of my existence. I actually hate Opus. All right, so let's go let it out, and it's probably Session kicked off. Okay, let's go to our third session, which is implement your Show Work Trust labels to sit in Action Service 1 and Canvas Design. Okay. All right, third session here. What did I copy the wrong thing?

There we go.

All right, rock and roll. Someday I'm gonna jam on one of these with you, dude. I would love to. A long day tomorrow. Would have saw your last second as well. Hey man, thank you so much for coming here. Um, definitely do the, uh, the like, subscribe, and comment. You did that, so thank you, and we'll see you on the next one. Okay, so what is it thinking here? Go receive design elevate. Gertel P1 is legitimate. Runtime check. Transfer using real-to-real traces. Layer contract jobs rail. Hey, average jobs 4 to 5 weeks out, multi-day jobs, 7 days property, weather fixtures per day. Okay, so right now it is just getting the layout contract, right? Running 3 lines, got it. See you later, buddy. Now, never hurts to have some good music. I made my own playlist so that way I don't get shut down for any property— what do they call those— copyright rules. So you guys have to let me know if you guys like my, uh, like my music. Let me know if the music's too loud. I don't know how it comes through when I share the audio with you guys.

I don't know if it's overpowering.

I can also connect my headphones. have available information they need to make good decisions so that while human beings still belong at workplace, they can still make the decision—

have empathy for their customers and have empathy for their teammates but without driving much more of a game than this random insert into it. Really concerned about how most softwares are just designing more ways to see information.

So for those who are just joining, the way I like to explain this, that Hermes agent, the marketer, kind of acts as that driver.

I'm not on the floor until like 3:40 at night, but I'm building, I'm posting, you know, consulting sessions that I'm doing with customers where I'm guiding them.

Business.

Every day I spend 3 to 4 hours talking directly to groups of people, you know, helping them with their businesses.

For me, it's like, how do I take that, all of these consulting sessions that I'm doing, and say, you know, like in this example here, like all of these questions that I end up answering, right? How to recruit, how to host hiring fairs.

But going to the core of the device and the food and the pump and the battery and the bottom, that turns into things linear. So if you look at all of our solutions, we have, um, production techniques that are very different, the layers of what they do.

Tons and tons of issues here that we're working through.

And then the snag is taking out those issues. Marcus is the Hermes HQ guy. He'll speak to you in context. He helps you with those problems. I give you a phone number.

So if you're here watching this right now, turn the volume down, and I give you a phone number, let's say 780-863-4652.

I'll give you another phone number, 780-963-4112. What was the first phone number?

I don't need you to participate in the chat to try and put it in the chat.

So if you don't remember, that's because our brains are lucky enough to remember an 8-item grocery list, but a 250,000 to 1 million token context window, the equivalent of like 3 Harry Potter books, there's just no possible way that I can keep track of the issues that have been generated from Wayfinder sessions, Grow Me with Doc sessions, PRD sessions, or the product requirements documents.

I turn those PRDs into issues.

There's no possible way for me to keep all of that in my head as context at once.

There's no way for me to read, translate, interpret, and essentially internalize what code is being developed in 3 different branches of coding at a time. So Marcus, the Hermes agent, he basically works as a companion through my sessions where I can then say, hey, this is what we worked on, this is what we did. I can also say, hey, here is an hour-long transcript of me consulting a roofing business owner or property manager or vice president of sales on this infuriating issue and how to make sure that this contract This is what makes it into the product. They can take that hour-long transcript, you know, find issues in linear and 17 product decisions you've already made and the code base and take that all into context and basically be my companion.

Then we work across several coding sessions. I generally take down 3 lanes at a time. I've done the thing where I have like 9 agents in 3 boxes, totally chaotic.

And then all you end up doing is having to go back and fix all the stuff as well.

And there's an argument for like, okay, well, you can work on that ahead of time, you can make it before ahead of time, fixing that later is faster. Completely awesome. I actually really do care a lot about quality, so I really want to be accountable. But you see here, of course, that title of that changed, right? We see now we have the 1. What we do see— now the thing is, where's the information? We have the loading screen. We have the create box. Beautiful. Ah, this is where we're going to be— slide out. Okay. Then we also have our 15th grade. Interesting. Okay, okay. But I still think it's too much information. I really just don't want too much information on the page. I don't want you to have to squint.

Okay, and then this is the footprint.

Very cool. Okay, it's going through an evolution here. I like it. I like it! Ahahaha! Okay. How does this work on— This is a wayfinder, right? Oh, that's the same thing. This is a wayfinder. The wayfinder skill is a really fantastic skill from that whole box, which helps you really just like find your way based on your plan. The last one we're running is a way tighter setting here. So let's first go through discovering everything. Now what I don't like is in this case, it just kind of like went worse. No good. Shit. Let's go look at which is this, EDA 542.

You can see that it's now like in, in review, so it's like already running. Okay, so do not install Copilot.

So if you're wondering what grep pal is, grep pal is— grep pal actually like runs, runs screen reviews and actually reviews your code for you. But in many cases it'll actually run screen recording interactions with your tool. So if you tell it like recreate this bug, it'll actually recreate the bug and then and it'll go and like find, fix them up.

You can see it gave it a score of 3 out of 5.

It's totally normal for the first run, but once I get this to a place I want it to learn, then I can tell it, hey, cycle through grep tile until you get a 5 out of 5. That's what it's called, a grep loop, because that's how it loops. But let's see what happens. Okay, so let's look for your name reliability, which we did in the earlier example. Is we're going to take this box, we're going to go back to Marcus. Hey Marcus, I'll make it for you. So I believe it's 532, right? 532. My instinct tells me that we should do all 20 and not dumb it down to the 9. I don't understand why we wouldn't require all 20.

As for the test harness, I prefer more testing than less.

It's always nice to have that.

I don't understand the first question at all.

I also said, found it interesting, I said my catalog currently designates zero predicted keys. The known intentional behavior is all predictions get rejected. I don't know why this happens at all. So now it's a problem for the Next. It's kind of cool.

I'm going to remove this for 2 seconds. I want to read a Slack message.

All right, bring it back up. Okay, this is odd. Why? What issue is that?

All right, well, we are at 10 o'clock and I don't have any more comments. So if anybody here wants to comment and have a conversation or have a discussion about this, I would love to hear from you. If I don't get a comment, then I'm going to jam out. And I just want to make sure— it's always easier to work when I know I don't have any like API keys to deal with or anything So it's really cool to work with you guys and to have you guys here join us.

And yeah, do the whole like, subscribe, comment, share with friends.

Appreciate being here.

We love to just like put it in the open public.