// life timeline
A 286 with an amber monitor
Tech support as a kid
Mexico City to Monterrey for systems engineering
2000s: remote ColdFusion developer
CMMI certification makes him a project manager
Bank systems that control ATMs
2025Quits Windows over taskbar ads, installs Omarchy
2026OpenCode Go, his blog in 2 or 3 sittings
2026His own Android app: Rails plus native Kotlin
2026sonic.apex Omarchy plugin
// 00
The rundown
David is a type 1 diabetic in Monterrey, Mexico, and the app that came with his glucose sensor was not giving him enough. So he built his own. An Android app with a Rails backend and a fully native Kotlin frontend. His words on Kotlin: "I don't know anything about Kotlin." He shipped it anyway, with AI agents, on Omarchy.
That is the whole story of this moment in one man. A technical project manager who started in tech support as a kid, wrote ColdFusion in the 2000s and ran projects on bank ATM systems, now builds the exact software his life needs. He is builder #7, and he brings omarchy.builders to 6 countries: the US, Britain, Singapore, Canada, Pakistan and Mexico.
“I built the whole backend in Rails and the frontend, all native Kotlin in Android. I don't know anything about Kotlin.”David · L84
// 01
The app the sensor never gave him
"I'm a type 1 diabetic, so control of my disease, you know, is one of the things, one of the main things." The app that ships with the sensors is good for the sensor. "But it doesn't give you too much information."
So he opened an agent and started small. "I'm just going to log my insulin intake." Just that. It worked, and it was "again, amazing". Rails on the backend. Native Kotlin on Android. A language he had never touched.
He is clear about what it is and is not. "It's not to save my life. Not that dramatic." It is about control. Big widgets with exactly what he wants to see. "So in a glance, I see what I want to see, and none of the other apps were giving me that."
Next: make it a hub that pulls from his other apps and from any sensor brand, polish it, then open it up so it helps everyone else living with the same thing. Nix asked to be told the day it goes public. David's answer: "You are going to be my first notification."
Lesson for every builder: start with one field. The one number the official app hides from you. Let the agent write the language you don't know.
// 02
A 286 and an amber monitor
His first computer was a 286 with an amber monitor and 2 floppy drives. He cannot even remember the brand. He played games on it, a karate game among them, and then found Gorillas, the game that shipped with its own source. "I think that was the first, like, I came near programming."
Born in Mexico City, he did tech support "when I was really young", then moved to Monterrey for college to study systems engineering.
// 03
ColdFusion, CMMI and ATMs
His first gig as a programmer was remote, in the 2000s, writing Macromedia ColdFusion. Tech lesson: ColdFusion let you put server logic right inside HTML style tags, years before that was cool again.
Then a company he worked for went through a CMMI certification, the process maturity model big shops use to prove they ship software in a repeatable way. "And they chose me to be a project manager." He has been a technical PM ever since. Mostly software development, plus a bank with "all sorts of crazy things going on", like "the system that controls the ATMs".
// 04
Ads in the taskbar? Goodbye, Windows
David has "always been a linux fan". His personal PC was just for games, until Windows pushed one step too far. "This cannot be happening. I cannot have ads in my taskbar. What is this?" He wiped it and installed Omarchy. The games kept running.
He found Omarchy on X, following DHH after about 10 years of Rails. Today his work PC is still Windows, and every day he hits the Super key by accident. Going back feels like going back "maybe 50 years".
// 05
OpenCode Go and a blog in 3 sittings
He started the year copy pasting from ChatGPT into his Rails controllers. Then he saw DHH using OpenCode. He signed up for OpenCode Go, the cheap starting tier that opens up many different models.
His blog, the one he had been planning, was done in 2 or 3 sittings. He went hunting for errors. "Going through the code. I couldn't find anything." His reaction: "And I just couldn't believe it, you know?" Then came another project, and another. Today that blog lives at davidzu.com.
How does he keep up with AI? "I don't keep up." He stays in his lane and builds.
// 06
The architect and the coder
David runs agents like the PM he is. He talks to one model. That model calls DeepSeek as the architect, which writes a technical specification. Grok Build is the coder, and it reads the spec.
The rule: "I don't let the coder change the, uh, specification." To change it, the coder has to convince the architect. That kills the error loops where an agent hits a wall, invents another path and breaks everything. Fewer mistakes, fewer hallucinations. That is CMMI thinking applied to agents.
// 07
My data, my database
After the insulin app, the biggest win was owning the data. "I know where, you know, like, what each table does." His records live "in a database store, but it's mine."
Privacy matters. So does resilience. No company can get bought, kill the service or charge more for the same thing. Switch sensor brands, keep your history. Next on his list are about 5 subscriptions to replace, starting with a meditation timer he has used for 10 years that grew courses and guided sessions he never asked for. He just wants his timer and his data.
// 08
sonic.apex, meal-planner and more
David builds for Omarchy too. sonic.apex is his Omarchy plugin for the SteelSeries Apex 7 TKL keyboard: RGB, the OLED screen and the scroll wheel, from Python. He wants a wider monitor just to fit more plugins on screen.
meal-planner is a household meal planner built as a Rails 8.1 multi agent pipeline. Everything he described on the call was made on Omarchy. "It was Omarchy, the enable enabler of having all, uh, of these projects coming together."
// 09
Everybody is having fun
His read on why everything is accelerating: "Instead of creating a new SaaS or a new big business, what everybody is doing is having fun." Modding games. Personalizing everything. "Like, myself, I just built an app for me."
And the feeling? "I'm personally as excited as when I was starting college, you know?" That moment "when you feel like everything is possible". He feels it again.
// 10
In his words
"I don't know anything about Kotlin."
"So in a glance, I see what I want to see, and none of the other apps were giving me that."
"I cannot have ads in my taskbar."
"Instead of creating a new SaaS or a new big business, what everybody is doing is having fun."
"I'm personally as excited as when I was starting college, you know?"
"I don't let the coder change the, uh, specification."
"I don't keep up."
// their setup
Setup
hardware
Lenovo LOQ (Ryzen 7, RTX 4060) on Omarchydaily · laptop
Windows work PCwork · workstation
SteelSeries Apex 7 TKLkeyboard · keyboard
tools & models
opencodeopencode-gogrok-builddeepseekchatgptrailskotlinandroidomarchy-pluginshyprlandgithubdeepseekgrokchatgptrubykotlinpythoncoldfusionagent workflow
Orchestrator pattern: DeepSeek as architect writes the spec→Grok Build codes it→and the coder may not change the spec
// learn from David
Learn from David
Split your agents into architect and coder intermediateDavid's orchestrator pattern cuts error loops and hallucinations.
Build the app your vendor won't beginnerStart with one field, keep it in your own database, grow from there.
// full transcript (cleaned)
Show the cleaned transcript (269 lines) · open full page
L1Nix: Okay. One, two, three. Okay, cool.
L2Nix: Um, I think we're ready. Uh, awesome.
L3Nix: Can you say something to make sure I can still hear you?
L4Nix: Ugh, I can't hear you again. Can you hear me?
L5David: Problem.
L6Nix: There you are.
L7David: Yeah.
L8Nix: There you are.
L9David: Oh my God. Look, whenever I got the microphone working, I lost hearing on the.
L10Nix: I gotcha.
L11David: So I'm just going to leave it at that. The speaker. There.
L12Nix: All right. How you doing, man? How you doing, man?
L13David: I'm doing fine. Thank you. Lots of work, but everything's going fine.
L14Nix: What's your, uh, what's your X handle? Because I don't know your David to your X handle.
L15David: David Cue. David Cue.
L16Nix: K-U? T-U?
L17David: C like in my last name, just the first two letters of my last name.
L18Nix: Oh, Z-U.
L19David: Z-U.
L20Nix: There you go. All right, I gotcha. All right, I just want to be—I like to have it pulled up whenever I chat with folks.
L21Nix: All right. Sorry about all the trouble getting this thing rolling.
L22Nix: Good to see you. Where in the world are you?
L23[redacted: echo: repeats Nix's line 21 to 22 inside David's audio]
L24David: I live in Monterrey, Mexico.
L25Nix: Okay. Very cool. I love it.
L26Nix: Um, we've had—I talked to people from India, Pakistan.
L27[redacted: echo: repeats Nix's lines 25 to 26]
L28Nix: I think there's an echo, but I can deal with it. Um, Singapore, all over the place.
L29David: Nice.
L30Nix: Well, tell me your background. What, what, what do you concentrate on, and how did you find Omarchy?
L31David: Background. I started working as a developer, you know, like. Well, I started working doing support when I was really young.
L32David: I was doing tech support, and then I—I was born in Mexico City. Then I moved here to Monterrey to start college, and I started, uh, studying systems engineering and working as a programmer.
L33David: Remote programmer back then in the 2000s. I was doing some call fusion.
L34David: I don't know if you remember that one. Macromedia call fusion.
L35Nix: Yeah, yeah. The fusion? Confusion?
L36David: Called fusion.
L37Nix: Cold fusion.
L38David: Yeah. I was studying a language.
L39Nix: Yeah, cold fusion. I gotcha.
L40David: Cold fusion, yes. To put it all inside of the HTML tags.
L41Nix: Yes.
L42David: That was my first gig as a programmer. And, you know, I worked for several different companies back then. And then when I was working at, uh, another company, they were doing, uh, a certification.
L43Nix: Uh-huh.
L44David: CMMI certification.
L45Nix: Uh-huh.
L46David: And they chose me to be a project manager. And since then, I've been working as a technical project manager.
L47Nix: I gotcha. I gotcha. Like, what kind of projects?
L48David: All kinds of projects. I mean, I've done mostly software development, but also I work at a bank, and we had all sorts of crazy things going on.
L49Nix: That's cool.
L50David: Like the system that controls the ATMs and things like that.
L51Nix: Yeah. Um, I was looking at your tweets where you said, "Everything is moving so fast." How do you keep up?
L52David: I don't.
L53David: I don't keep up.
L54Nix: This is very true.
L55David: I'm just staying, like, in my lane, man. You know, like, uh, you know, I started—I think I started this year, uh, with ChatGPT, and I already had Omarchy installed because I always been a Linux fan. So I saw this new, uh, distro coming out, and I was—I, I had a—I have a personal computer, and I was using it just for games.
L56David: Just for gaming. I was just, like, on my work PC all day, and I just used my personal for gaming.
L57David: And I got sick of—sick of Windows at some point. I don't know.
L58David: It was so mad or something that I was like, "This cannot be happening. I cannot have ads in my taskbar.
L59David: What is this?" So I said, "Let's get rid of this.
L60David: I'll install Omarchy." And, you know, I started playing some games there.
L61David: I was just cool. Then I started, uh, playing with ChatGPT.
L62David: And I always, like, try to keep the technical side, so I'm doing my personal projects, uh, uh, doing Goblin Rails. Always been a fan of Goblin Rails.
L63David: Started working on my blog and things like that. You know, copy-pasting things from ChatGPT into my controller.
L64Nix: Yes.
L65David: And.
L66Nix: Early, early days, it's all integrated.
L67David: I think it was. Yeah, yeah, yeah. But it was just, like, half a year ago or something like that.
L68Nix: Yeah. Very quick.
L69David: Yeah. So anyway, uh, I think it was on Twitter that I saw this agent use, and I saw DHH using OpenCode.
L70David: And, you know, I created my account and started looking at it. And, and OpenCode has this really cheap, uh, starting point.
L71David: I think, uh, OpenCode Go is the one, and it gives you access to a lot of more different models.
L72Nix: Yes.
L73David: So I started with that. And I don't know, Nix.
L74David: I think I ended the blog that I was planning to do in, like, two seats, you know? I don't know how many hours was that.
L75David: Two, three hours, a couple of seats, and I had it all done working with these agents. And I just couldn't believe it, you know?
L76David: I was going through the website and trying to find errors and.
L77Nix: Sure.
L78David: Going through the code. I couldn't find anything. And I was like, "This is amazing.
L79David: This is the whole thing, right?" So then I started creating another project and another project, and, you know, I, I, I just, uh, created.
L80David: I'm, I'm a type 1 diabetic, so control of my disease, you know, is one of the things, one of the main things. And I didn't like, you know, I used the app that comes with the sensors.
L81David: And so the app is good for the sensor, but it doesn't give you too much information. So I created, uh, an Android app.
L82David: I, it started as, "I'm just going to log my insulin intake." Just that.
L83David: I just want to put how much insulin I'm getting in each day. And I did, and it was, again, amazing.
L84David: Like, I built the whole backend in Rails and the frontend, all native Kotlin in Android. I don't know anything about Kotlin.
L85Nix: Right. Do you have a GitHub account?
L86David: Yes, sure. It's the same handle, David and.
L87Nix: Okay. Same handle.
L88Nix: On X and on GitHub. Do you—let me pull it up real fast and see what you got out there.
L89David: All the—all the projects are up there, and it's so locked in. I haven't put private anything.
L90Nix: Uh, people.
L91Nix: Uh, I'm trying to find—there's a lot of David Zu's. Um, can you put in the chat a link to your profile?
L92Nix: Because there's a bunch of David Zu's.
L93Nix: Um, while you're doing that, have you seen the summaries that I do after these chats for folks?
L94David: The, the things you are typing after these interviews you have?
L95Nix: Yeah. So let me—let me put in the chat, "Look at this site."
L96David: Oh, this site.
L97Nix: Yeah, "Look at that site."
L98Nix: And.
L99David: Oh, no.
L100Nix: Okay. So, um, that site is for all my interviews. I put summaries and talk, um, and make people, you know, boost them up and feature people about what they do with computers.
L101Nix: And I wanted to get your permission to do—to put your, uh, profile up there and feature you and make you look like a rock star. Is that okay?
L102David: Sure. Sure. Go ahead.
L103Nix: Okay. I just always ask first before I get started. Um.
L104David: For sure. For sure.
L105Nix: Um, so tell me your background. When did you start using computers, and what was your first computer? And, like, just tell me the whole story.
L106David: Ooh, man. I, I had an Edge 86, uh, Amber, Amber monitor, you know?
L107Nix: Yeah.
L108David: That was my first computer.
L109Nix: Okay.
L110David: I don't even remember the brand, like, that crazy brand.
L111Nix: Did you use Commodore 64 or, or mainly X86?
L112David: X86. It was an X86, my, my first computer.
L113Nix: Like 286, 386?
L114David: Like a 286.
L115Nix: Wow. Going back. Back when the RAM was in megs.
L116David: Yeah.
L117Nix: Not gigabytes. Megs.
L118David: Sure. I, I, I remember that the, you know, like, the, uh, bottom floppies, like, the two floppies, and you had to put.
L119Nix: And.
L120David: And two floppies you were using.
L121Nix: And clipping it and turning it over?
L122David: Yeah.
L123David: Yeah. From that time, you know, I was just doing playing games and, uh, playing karate there.
L124David: And I actually did. I think I tried to do the Gorilla game again, which basically had the whole instructions to go build your game piece by piece.
L125Nix: Uh-huh.
L126David: I think that was the first, like, I came near programming and, and really doing real computer stuff.
L127Nix: Let me look at your, uh, you got a lot of repositories. What's your favorite repository that you're working on?
L128David: Oh, right now, you can check out, uh, it's called A1C. It should be there. A1C.
L129Nix: Um, searching.
L130David: That is my, uh.
L131Nix: Is it called something else?
L132David: Dia- diabetes login application.
L133David: No, it should be there.
L134Nix: Yeah. It might be private. Do you have it private?
L135David: No, no, no. No. Oh, yeah.
L136David: This one is private. Oh, okay.
L137Nix: That's okay. Um, tell me—tell me how you, like, what made you make it, and, and how helpful has it been to, like, help you with your disease? Has it, like, changed the way you work with your blood, blood type?
L138Nix: And, like, tell me all about that.
L139David: Oh, yeah. For sure. Like, it changed all my life, this thing.
L140[redacted: private health detail, lines 140 to 149]
L150Nix: Wow. That's a lot.
L151[redacted: private family and health detail, lines 151 to 159]
L160David: And I started, you know, living like this, uh, measuring all the time. Using glucometer sucks, really.
L161David: So when I got my first glucose monitor, it was also a game changer, complete game changer. Now, having, uh, all your glucose at the moment in your cell phone.
L162Nix: Right.
L163David: That was also amazing.
L164Nix: How do you so does the app warn you when it's about to get bad and you're able to stop it from getting worse?
L165David: Yes. Yes. Yes.
L166David: Yes.
L167Nix: So it's preventative a little bit.
L168David: It prevents yeah. Yeah. I mean, yeah.
L169David: If, if you are unaware. I'm mostly unaware of when I'm going up, because it doesn't feel too much.
L170David: But when I'm going down, I feel it in all my body. So it's usually I know I'm going down, right?
L171David: But the alarms help, especially at night, because sometimes you're just fully asleep and your glucose is going really down.
L172Nix: And do you have alerts that say, "Hey, David, you need to do something"?
L173David: Yeah. They in the phone and my watch.
L174Nix: Okay.
L175David: The same. The alert comes in my phone, goes to my watch, and, and those are the things. But I also want to start building, you know, like, little displays with just my glucose monitor, and so I can, you know, put the little I'm, I'm exercising in, in the yard.
L176David: I can put it there and see how, how low am I getting. That's also one of my projects, but I have a lot on my plate right now.
L177Nix: Oh.
L178David: All the things.
L179Nix: Um, so that's really cool that, that you made your own app to, to save your life. Would you say that's true?
L180David: It's not to save my life. Not that dramatic, because I have all the other apps that do that. But it gave me a lot of control that I couldn't find.
L181David: And also, it's like, you know, I see the information that I want, and I want it.
L182Nix: Right.
L183David: You know, that level of personalization that I just, like, I put big, uh, big widgets with. This is my glucose. This is the last, uh, intake I took.
L184David: This is how much units you took. So in a glance, I see what I want to see, and none of the other apps were giving me that.
L185David: And, and one of the things that I want to do, progressing with this app, is use it as, as a hub for all the other apps, you know, because once I got my insulin there and I know how much insulin I'm putting e-every day.
L186Nix: Right.
L187David: Now, the next metric is, I need to know how many calories and how many grams of carbs correspond to these doses of insulin.
L188Nix: So do you correlate all the information together to help you know what to eat, how much insulin to take? And it really wraps all the information together to give you a better.
L189David: I need that stage right now. But I'm connecting to the other apps that I have. So my, my watch, you know, gets my all the moving information and exercise that I do.
L190David: And I can also in that app log food. So I'm using that app to log my food because it has, like, uh, an AI layer that you can take a picture, snap a picture of your plate, and it will calculate how much carbs you're eating.
L191Nix: Right.
L192David: It's all so, but for me, it's a great start because I don't have to log everything by hand.
L193Nix: Right. Right. And that's the goal.
L194David: I'm pulling the what? Sorry.
L195Nix: Go ahead.
L196David: I lost you there for a second.
L197Nix: Are you there?
L198David: You're back. Yeah.
L199Nix: Okay.
L200David: You're back.
L201Nix: Hey, I'm going to turn your video off because I think your video is making us lag.
L202David: Sure. For sure.
L203Nix: Okay. I know what you look like. All right.
L204Nix: So, um, how did you find Omarchy?
L205David: How did I find what?
L206Nix: Omarchy.
L207David: Oh, I think it was Twitter. I think it's it was Twitter.
L208Nix: Okay.
L209David: Because I've been following Jake because I'm, I'm a fan of his work because I've been working with Royal Rail for, like, 10 years.
L210Nix: Right. You mean DHH? I got you.
L211David: DHH, right.
L212Nix: Right. Um, what and how do you use Omarchy today?
L213David: Well, everything I've been telling you is done on Omarchy. All the apps, all the designs.
L214Nix: Oh, wow.
L215David: And it was Omarchy, the enable enabler of having all, uh, of these projects coming together, really. You know, it's the it's the I and C set up in this operating system that allows me to, to do this. I have my work computer with Windows, and I use Claude in my home computer.
L216David: And it's like, uh, 200 years before what I do with Omarchy.
L217Nix: Right.
L218David: It's like it's from the '80s, the computer. It's because, you know, Windows, and it doesn't have agents running, and it's not in, in, in open code. I, I build, like, an orchestrator pattern.
L219David: So I spoke with one model, and then this model calls, uh, DeepSeek, and then DeepSeek is the architect. So the architect writes a specification, a technical specification.
L220David: And I use Grok build to as a coder. So Grok reads the specification created by DeepSeek.
L221David: And that way, I managed to, like, layer out the work of the agents. And it's been reducing a lot of mistakes and, and hallucinations and everything because I don't I don't let the coder change the, uh, specification.
L222Nix: Right.
L223David: It has to speak to the architect to convince and convince the architect to change the specification.
L224Nix: Right.
L225David: So that way, I think you avoid error loops when the agent cannot go that way and finds another way of implementing and maybe breaks everything.
L226Nix: Right. And how does it feel when you go back to your work machine on Windows? Do you end up, like, accidentally pressing the super key?
L227David: Oh, yeah. Yeah, yeah. All the time.
L228David: All the time.
L229Nix: That's funny. And you said it feels like going back 200 years. Is that what you said?
L230David: Yeah. Yeah, yeah, yeah. It feels like going back, I don't know, maybe 50 years.
L231Nix: Have you, um, have you customized Omarchy for yourself a lot? Like, do you do themes or.
L232David: Oh, yeah. Sure. Sure, sure.
L233David: Yes. I was I was, uh, uh, posting on Twitter the other day that I want to buy a wider monitor just so I can host more, uh, plugins in that file, you know?
L234Nix: Yes. Yeah. Get a white line.
L235David: Like I.
L236Nix: Line them up.
L237David: Yeah. I, I see all these things that are being done by everybody. And I think that's why I think that everything is accelerating fast because, you know, I, I, I feel that with this, uh, coming of AI and all the agents and, and, and operating system like Omarchy, instead of creating a new SaaS or a new big business, what everybody is doing is having fun.
L238David: You know, like, modding games and, uh, personalizing items. And, like, myself, I just built an app for me.
L239David: And I think that's, like, the first step of this age where everybody's just having fun.
L240Nix: Yeah. And it's interesting because, like you mentioned, uh, uh, software as a service, you know, I even a couple of months ago, I think I don't remember, I had, like, a couple of maybe 10 services that I subscribed to. And I think I've got it down to just the, the agent subscriptions.
L241Nix: And I don't even you know, if I've if I find that I used an application that I had to purchase, I just make it myself now.
L242David: Right. Right. And that that's I think that's what we are all doing because it's so easy, and you don't have to get all the blood of the application.
L243Nix: And have you found that when you make a new one to replace a subscription, yours is better than the subscription?
L244David: Not right now, but I have, like, five on a store to do that. For example, I, I've been using a timer for meditation for many years.
L245Nix: Right.
L246David: Many, many years. Like, 10 years. And it used to be just a timer.
L247David: And now, it has all this stuff there, like, guided meditations and courses, and it gives you phrases before you start your meditation. And I'm tired of it.
L248David: I'm like, I just want my timer, like, before my timer, and, you know, keeping my data. Because that's one of the things that I saw it was the most impactful for me after I built my, uh, app for logging insulin, that now I have all that information in my own database.
L249Nix: Right.
L250David: I with that database, I know where, you know, like, what each table does. And that's what I, I I'm going to be doing for the next years. Just keep all my disease information in, in, you know, in a database store, but it's mine.
L251David: Nobody's going to tell me, uh, you need to move it from here or now to host this. You need to pay more.
L252David: I have my information there. And, you know, that that's the kind of things that I want to be doing, like, keeping my information for myself.
L253Nix: So is it a matter of having more customizations, or is it a matter of privacy, or is it both?
L254David: Well, privacy. Privacy is one of the points. And resilience, you know, so to speak.
L255David: Uh, resilience in a sense that now you are not at the mercy of a company that, you know, can get bought by another company and remove the service that you were using, or, like I said, like, charge you a lot more for the same.
L256Nix: Right.
L257David: And, uh, for, for example, with the glucose monitors, I've been using several different brands of glucose monitors. And I'm planning on, on keep doing it because, you know, they keep coming out, new ones. And every time you switch to a different brand, then your past information is gone.
L258Nix: Right. Right. So now, you can change your monitor and keep your data.
L259David: Exactly. Exactly.
L260Nix: Um, have you found some monitors are more open where you get more data off of them?
L261David: Well, I, I just grabbed the one that I use. It's a Chinese one. And I'm, I'm getting the info from that one.
L262[redacted: private, unannounced, lines 262 to 266]
L267Nix: Sure.
L268David: And if I'm going to try them all, I'm going to make my app read all of those monitors so I can ingest the data. And I think that's my plan for the future for this app. My plan is to give everyone the ability to have, like, a hub from all of your other apps while dealing with diabetes.
L269Nix: That's amazing. So what is your plan? That you're getting your application while it's private to get it nailed down and get it perfect, and then you're going to share it for the world so that you can help other diabetics?
L270David: Exactly. Yeah. Exactly.
L271Nix: That's amazing, David. I mean, if you think about the power of a computer, and then if you add Omarchy to it, which it gives you all these abilities, and then you have a problem that you fix that other people have, I mean, you can draw a straight line across all those things to where none of this was possible without AI. Maybe, maybe possible without Omarchy, but, like, Omarchy certainly helps to accelerate it, doesn't it?
L272David: Exactly. Exactly my feeling.
L273Nix: Wow, man. That's amazing.
L274Nix: Wow. I'm still trying to wow.
L275Nix: That's amazing. Well, um, what else do you want to tell me about that, that you want the world to know?
L276David: I don't know. I don't know, Nix. I think we're, we're living in other exciting times.
L277David: Uh, I'm personally as excited as when I was starting college, you know? That, that moment when I when you feel like everything is possible and you haven't faced the terrors of, of working for a big company.
L278David: I, I feel like that again, you know? And, and it's an amazing feeling.
L279Nix: Right. And I'll tell you what, David.
L280David: Right.
L281Nix: The thing that the excitement that you talk about, um, I've interviewed about 7 people now, and there's about another 25 that are in that are scheduled. And every single person has mentioned the word excitement and how they feel like, you know, they're enabled again, and they they're able to control their own software. They're able to control their own computer.
L282[redacted: third party health (another interviewee's condition)]
L283David: Right. Right. Right.
L284Nix: Well, man, I really appreciate it. Um, again, I want to I want to appreciate I want to tell you thank you for meeting with me and telling me your story. And I'm going to go off and write up your, uh, your profile, and I'll copy you, and I'll tag you.
L285[redacted: private, lines 285 to 287]
L288Nix: And I and I I wish you well, and I want to keep in touch with you, okay?
L289David: Oh, yeah. Please. Please do so, Nix.
L290David: Just the same to you. And you are going to be my first whenever I, I finish this and I put it public.
L291David: You are going to be my, my first notification, Nix.
L292Nix: Oh, man. Thank you so much. I really appreciate it, David.
L293Nix: You're very kind, and I appreciate you taking time to speak with little me. And when I put your story out, I'm going to make you a rock star, okay?
L294Nix: So look for it in the next 20 minutes, okay?
L295David: Thank you very much.
L296Nix: Thank you so much, David. It's great to talk to you from Mexico, man. It's so cool.
L297David: Bye.
L298Nix: All right. Bye-bye. Thank you, sir.
L299Nix: That's the.