I Was Betrayed. What’s Next?
The pieces were finally talking to each other, and the idea that had been living in my head was suddenly doing stuff on a screen. Then the arrangement changed.
I spent the better half of this year building an app.
At some point around two in the morning, I started treating the glow from my laptop like sunlight. I was sitting on the couch, hunched over a computer, drinking something from a can that promised energy and mostly delivered heartburn, convincing myself that this was what momentum felt like.
Everybody else had been asleep for hours. I had a blanket half on me and half on the floor, and a charger stretched across the room in a way that was eventually going to kill one of us. I should have gone to bed, but the thing was working.
It was not finished, because it was never finished. People who build things know that “finished” is mostly a word you use when somebody asks why you are still awake. But it worked. The pieces were finally talking to each other, and the idea that had been living in my head was suddenly doing stuff on a screen.
I built it, and I really thought that was going to change me.
I thought there would be a clear before and after. Before, I was the person who had a lot of ideas. After, I would be the person who proved they could pull one all the way out of their brain and make it real. I would be more confident, more legitimate, and less desperate for somebody else to tell me I belonged in the room.
Instead, I woke up tired, opened the laptop, and kept working.
There is a particular kind of delusion that comes with building something ambitious. You start believing the next solved problem will finally let you relax. Then you solve it and immediately discover three smaller problems wearing a trench coat, so you keep going.
You skip the movie. You answer “in a minute” when somebody you love asks if you are coming to bed. You carry the problem into dinner and the five minutes when your kid is trying to show you something that should be more important to you too. You tell yourself it is temporary and that it will all make sense once the thing is done. I have written about that pacing problem before, back when I still thought it was a scheduling issue.
The embarrassing part is that I did finish it, or I got close enough that the difference stopped mattering. It existed. It worked. It was real enough for other people to touch, use, discuss, and make decisions about.
Then the arrangement changed.
That is the clean version. The real version is that I was building this for a company, not just tinkering with a personal idea in my living room. There were expectations, deadlines, conversations about where I fit when it all got real, and a whole lot of work that became easy to take for granted once it was visible.
Once the thing became valuable, my place beside it became negotiable. Conversations got strange. Things I thought were understood suddenly required proof. The work was still there, but the story of how it got there started being edited in real time. I went from helping build the thing to feeling like I was standing outside of something I had spent an unreasonable amount of my life making.
I am not turning this into a public autopsy or laying out screenshots like a person with a corkboard and twelve feet of red string. I do not want to live there, and the details are not actually the point.
The point is that I had attached so much of myself to the outcome that when the outcome got taken out of my hands, I did not know what to do with the person left behind. I had built the thing, so why did I still feel like I had something to prove?
For a while, I thought the answer was obvious: because I got screwed. And, to be clear, I did.
That anger is real, and I am not going to sand it down into some clean little lesson about gratitude. Sometimes a company benefits from your work and becomes very creative about why it does not owe you what it happily promised while it still needed you.
That sucks. There. Very profound.
Still, being angry did not fully explain the emptiness. It explained why I wanted to throw my phone into a lake, but it did not explain why the accomplishment itself suddenly felt so far away.
That is a lot to ask from an app.
I think I expected the finished product to reach backward through time and validate every version of me that had ever been underestimated.
It was supposed to prove I was not scattered or just another creative person who gets excited and moves on. Mostly, it was supposed to settle an argument I had been having with myself.
The problem is that you can build something impressive and still carry the same old voice into the launch. That voice does not look at all the impossible shit you figured out and say, “Wow, good work.” It asks why it took so long. It asks why somebody else has more users, more money, a cleaner announcement, or a nicer chair. That voice is not new. I named three of its favorite fears a while back, and it has not retired a single one.
Mine asked why I had not protected myself better, and that question hurt because it was not completely wrong.
Turns out, you should inspect that shit.
I was so focused on proving I could build the thing that I did not spend enough time making sure I could keep my place in it. I treated trust like infrastructure and assumed it would hold because everybody was standing on it. I have written about what trust is supposed to look like. It turns out I am better at describing it than inspecting it.
I know more about boundaries now. I know enthusiasm is not an agreement, and being useful can make you feel secure right up until your usefulness has been packaged into something that no longer needs you in the room. It was a brutal way to learn that, but the lesson is still mine.
So is everything else.
I know how to take a half-formed idea and give it structure, learn the part I do not know yet, and stay with a problem after the fun part is over. I know how to keep moving when the whole thing feels held together with caffeine and spite.
Nobody gets to retroactively remove that from me. They can minimize the work, rearrange the credits, or pretend the thing arrived fully formed. I still know what I built, and more importantly, I know who built it.
Maybe that is why I do not feel different. I kept waiting for the finished thing to hand me a new identity, when the work had been changing me quietly the entire time. There was no progress bar that reached one hundred percent and announced that I was now confident, legitimate, and immune to bullshit.
I just became somebody who could do it. Then I became somebody who could survive what happened after.
I wish that second part had not been included in the curriculum. I would have happily skipped that module. But here we are.
The laptop is still here, and so am I.
These days, I am trying to be more careful about what I sacrifice for the work. I do not want to confuse obsession with commitment or exhaustion with evidence that it matters. The people in the room with me are not interruptions from my life. They are my life.
I am still building things, but I am trying to do it for a better reason. The next one will not finally make me enough or win the imaginary trial in my head. I am building because it is what I do, and because turning a blank screen into something real still feels a little like magic, even after I have seen what people can do once the trick works.
I built the thing. It did not transform me on command, protect me, or make everything fair. But it left proof, and this time I know the proof belongs to me.