2025-06-24 recall - session #5

Oh, we're on day three and a half. How to do a hat change for good measure. So the goal for this is to wrap up the app and launch it where we left off. We have the the demon running Demon Demon Demon. Now I'm at home and we need to see here. 1 thought I had was actually I'm gonna also maybe record me turning this into content and like the different tools I use around the contact side. I'm not sure how interesting but we'll see. I'll certainly learn a lot through it. At the very least, I'll document what I use 72 6. Anyway, it's always interesting going through this stuff because it highlights areas that and I'm just curious to get better at have a general sense of like is there a faster way to do this stuff? On the flip side, it's, you know, you can see to what extent any. Any stuff is abstracting away some of the nuance building. I think the big thing for me is wanting to know of all the sort of tedious aspects of building stuff how to better leverage AI to do the things that most humans just don't want to do. Certainly around building up test cases I can think through and I often do think through tons of test cases to test. This is me asking it where we left stuff off it add a task to pull from WhatsApp but do it as a deferred integration. Not something we're going to do for launch. Yeah I'm not sure the likelihood of throttling issues but show me an outline for how you would approach the status task and do we already have subtasks and if not let's build out subtasks. Some of the stuff seems silly where you know, I'm. I am and should be defining the scope, not not deferring the scope to it. But it seems to already think that we're building something so I'm curious what it thinks we're maybe it's a good idea. There was one thing I saw at man with the stuff I meant to read which was basically usage examples of Taskmaster man really slowing down like Peter just really annoying was definitely in the GitHub brief. Jeez, man. Subnoxious got some real issues with Screen Studio. This not press. Not to be unappreciative of essentially a free tool but man, actually no, Screen Studio is not free. I'm not even sure I'm using Screen Studio in a way that they're that warrants using Screen Studio. Probably could just do this using QuickTime see what I Can killing me, man. All right. Parse JSON entries for sync sessions. We don't need to pull from the database reads and stuff like that. Let's exclude those because it's just. It's mudding up our logs. But also it's not a meaningful interaction that's worth us even querying from the database. So can we exclude those? How can we even identify. Then we should just be looking at. Well, is there a way to explicitly exclude those things? Reads and seen or whatever it is? It's not a database read. To be clear, I'm referring to the to read types. It's funny. Have some friends who. It's like one friend who runs multiple quad code instances in parallel working on different features. How the hell do you focus on multiple features at the same time? Like I have a hard time imagining that that's even possible because it's not like you can just be hands off and it just does it. Like there's a fair amount of oversight that still needs to happen and unless I'm just doing this wrong, but even then I think there's a certain level of oversight that needs to be done. Pay attention to what you're building. Nope, still saying that. Nope, I see that we're still logging. Check our logs for those unnecessary logs. I already said yeah, it's not even updating the actual. I mean, I can see you didn't make any changes to our code to eliminate message read and contact read. We should be eliminating that from our SQL queries in the first place. No, we don't want to remove it. No, we're not removing. No, we're not removing the logging. What I'm saying we just want to get rid of messages where the message itself is simply a read sent message. It's just a. Jesus Christ. No, we're not removing the logging of messages. What I said is get rid of logging or even any of the database entries when all of the entry is all it represents is a read sent message. What I'm saying is we are excluding read events because those are useless. All we care about is actual text messages sent and received. It dam you see the status. Learn how to do that. Commit the changes it I could have sworn we set this up where it was not nearly as involved to have it auto start read over the readme file I had just installed. Set this up as a demon that would auto when launch on when logging in or like restarting the computer, it would auto start when logging in. The instructions seem a lot more complicated than I recall doing. Please Set this up as a demon that will auto start at login. That was a mouthful it Right. Yeah, that's what I'm seeing. I mean it must be that it just manually did the other yeah, that. That's what we did. Yeah. So what happened here is option two. We just. They did option two but it did it like clot itself implemented it. And last time that's what I just did Auto why does it think it's if you needed to change the launch service file please make any adjustments to the readme markdown. So that is correct. Oh, you just got a message that says invalid command. Use help to see available commands. Why is that? Looks like it made changes. Do those instructions also include the hourly vron Looks like they got rid of the cron. No, it's gone. What's the command to check the status of the demon. Looks like you got rid of it from the read me. It's funny they could I'm sure it'll figure out remake means read me. Just blows my mind. How it accidentally removes. How does it accidentally remove anything? It feel like we're no, looks like there's a bunch of duplicates again happening. Man, this is really frustrating. Stop the command. You're sending duplicated messages that they should not be duplicated. No. Let me see. And we had a test. Oh, our tests are failing. But I don't think it's related to the deduplicate. Check it there. But wiser deduplication logic failing or not working. And is that test actually failing? We were sending. We were. It was not correctly detecting events that had already been logged. Why did that happen? Another thing's we didn't change anything. Since I ran this at my office and it had been working it Tulsa currently running. Bob, how do I stop. Please stop the daemon from running. I just did status and it's running it. How do we stop the daemon from running? It's still sending duplicate events. Stop it. Welcome to software development. There has to be a better way to do that him. Oh man. You gotta be kidding me. I'm dead. Hopefully I just won't auto restart. I mean this screen requires absolutely killing me. Great. Glad you can clearly see. As far as I could tell, it's still doing it. You know where the freaking logs. Dude, it's still running. Stop the Stop all of our node. Stop the script from running. Stop it. Ridiculous. This is why we can't have nice things. Oh really? No. Wow. No, no, buddy man, you gotta be kidding me. Dude, the script is still running. Stop. How do we stop this? It might be related to the fact I think we have auto restart on the launch thing. So maybe you need to remove it from the launch because we think we had auto start set up then that might have stopped. Is there a command I can run to stop the spawning and what's triggering the spawning again? Call stop the emails from sending. It's still sending emails. Just first stop the comment out the code that sends emails. Jesus Christ. What processes would be doing this? What can I look for? Because it said when I do node status it says it's not stopped. Disagree. Please still not be adding here. Please be done restart my freaking computer.