Dictation, structure, and human revision represented as a visual metaphor.

The rough version is often the only version I can get out at first.

I know the problem. I know several things about it that matter. I probably have an opinion about what caused it, another opinion about the last tool that annoyed me, and a detail that won’t turn up until halfway through explaining something else.

That is not necessarily the order a customer needs to read it in.

For a long time, getting from that pile of knowledge to a useful message was its own job. The technical work might already be understood, but it still needed sentences. Then the sentences needed rearranging. Then I had to check that I had answered the actual question instead of explaining everything adjacent to it.

With ADHD, fatigue, and migraines in the mix, that extra job can use a surprising amount of the capacity I had available for the original one.

Now a lot of my work starts with talking into my phone using Wispr. I explain the thing while I have it. I can interrupt myself, add the detail, come back to the point. Dictation gets words out where I can work with them. AI can help organize them into research, a draft, a set of steps, or documentation I might actually find useful later.

I don’t have to finish the document in my head before I begin.

That change is big enough that I’ve described the feeling as barely doing anything. It’s a strange thing to say after years of doing work the harder way. A task that used to include a lot of friction can suddenly feel suspiciously easy. Surely there’s another part where I’m supposed to struggle with it for a while.

Then I remember how much I brought to the conversation before the tool produced a paragraph.

I know the context. I know what matters to the person involved. I know which detail changes the diagnosis of a technical problem and which impressive-looking suggestion would make it worse. I have to recognize when a tool has answered a different question or turned uncertainty into confidence it hasn’t earned.

There’s plenty left for me to do.

The original “Still Building” article is a useful example. I had a history: illness, old websites, repair work, family, curiosity. AI helped arrange it into something readable. That didn’t give it permission to manufacture an exact childhood scene, decide how an outing ended, or turn every hard experience into a lesson with a tidy payoff.

And when I asked for ideas for more stories, the next useful step was a set of separate briefs. Each one had an angle. Each also needed limits on what it could honestly claim. The tool helped get the ideas into a form that another writing pass could develop. The history still had to remain mine.

That’s a lot like the work I do with customer messages and research. Organizing words is useful. Keeping the words attached to what actually happened is essential. A sentence can become smoother and less accurate at the same time. I would prefer a slightly awkward truth over a beautifully formatted guess.

The mistakes are part of using these tools. Dictation can give me the wrong word. AI can misunderstand the target, miss a qualification, or produce an answer that sounds finished before the result has been checked. I still need the source. I still need to read the draft. If something was supposed to work, I need evidence that it worked.

This is also why I care about where the result ends up. An answer disappearing into a conversation I can’t find later is only temporarily helpful. I want the useful information saved in a form I can return to. The next version of me who needs it should not have to reconstruct today’s whole train of thought.

There’s something quietly generous about making a tool do the part that costs you the most unnecessary effort. It leaves more room for the part you wanted to do: understand the problem, make something useful, get the message across.

It also leaves room to stop. Every saved minute doesn’t need another assignment. Sometimes making work easier means there’s a little more of the day left for life.

I’m still responsible for what I make. I still have to decide whether it’s right.

But I can begin with the rough version now.

For somebody with no shortage of ideas and a fairly unreliable supply of energy, that is a hell of a useful place to start.

Source and edition note

Based on Still Building, chapters 9, 12, 16, and the referenced conversation’s actual request for eight article briefs. The memoir/brief workflow is the concrete example. General mistake patterns are described without inventing a specific client incident or product guarantee.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

A fictional civic streetscape. The map is conceptual and shows no actual utility route or exact facility.

A perfectly ordinary building can ruin my ability to mind my own business.

It doesn’t need to be especially attractive. Sometimes a lack of windows helps. A cabinet, an unusual bit of equipment, something about the way a site fits into the street. There’s clearly a reason for it to exist, and now I would like to know what that reason is.

Living in Pueblo has supplied plenty of material.

I’m interested in phone systems, fiber, radio, utilities, and the practical machinery that lets a city keep doing ordinary things. Once you start looking at that stuff, the background gets busy. A bridge can carry more than traffic. A plain building can be part of a much larger story. An electrical site can have a history that reaches farther back than the equipment currently standing there.

The difficult part is keeping the interesting possibility separate from the answer.

One of my research threads followed a telecom-looking roadside compound around Medal of Honor Boulevard. That appearance was enough to start asking questions. It was not enough to identify what the place did. The research brought up records for a lift-station project in the corridor, but matching the exact place I was asking about to the documented facility remained unresolved.

That last sentence is less satisfying than a confident identification. It’s also the sentence that keeps the whole investigation honest.

If I let the appearance decide the answer, I can produce a very convincing story about a thing I haven’t actually identified. Put the story on a nice map and it gets even more convincing. The map does not improve the evidence. It mostly improves the font.

Sometimes the records do give you something wonderfully specific.

Pueblo’s Ordinance 10380 documents an exchange involving Intrepid and city-owned conduit across the 8th Street Bridge. The city made conduit space available in exchange for fiber strands for its use. There it is, in the paperwork: an ordinary piece of the city serving a communications purpose you could easily miss while passing over it.

I like that kind of discovery. The interesting thing doesn’t need to be secret. It can be public and sitting inside a document whose title gives most people an immediate desire to do something else.

A council record turns out to explain a small part of how people and equipment connect. It doesn’t reveal the entire network, and I don’t need to pretend it does. One piece becoming understandable is a perfectly good result.

Another thread led to West Station and the city’s Honor Farm history. The city records an electric substation on part of that property since 1951. The utility’s own project material describes plans for later terminal upgrades. The site has a history, proposed changes, and a role in the place around it. What first looks like equipment behind a fence becomes something you can begin to put in time.

That’s the pleasure for me: the moment an object gets some context.

I’m the same person who likes an old repeater page, a phone system, or a computer whose odd behavior suggests there’s something left to figure out. The city is a bigger version of the question. Who needed this? What problem did it solve? What changed around it? What information would let me stop guessing?

There’s usually another question after that. I recognize that this may be a personality issue.

A lot of the work can happen at a desk. That matters when standing and walking are difficult. Documents, maps, historical records, and imagery let me keep investigating even when a long afternoon on my feet isn’t workable. My physical range can change without making the subject less interesting.

And once I’ve spent time making sense of something, I want to preserve the useful part. A readable explanation. A source link. A note about what remains unknown. Something the next interested person can use without beginning the whole search again.

That might be the most consistent thread in my work: I want the thing I wished I’d found at the beginning to exist by the time I’m done.

There are plenty of unanswered questions left in Pueblo. Some will stay unanswered. Some will turn out to be much more ordinary than the first theory. I can live with that.

Ordinary things are doing a remarkable amount of work around us.

I would still like to know what the hell is in that building.

Source and edition note

Based on Still Building, chapter 15, and the September 4, 2026 Pueblo research dossier. The Medal of Honor compound-to-lift-station match remains an unverified lead. The ordinance, Honor Farm page, and West Station project PDF were independently read for this edition. The PDF describes a planned upgrade, not verified completion. No operating topology or equipment identity is inferred.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

• City of Pueblo Ordinance 10380
• City of Pueblo — Honor Farm history
• Black Hills — West Station upgrade plan

An imagined workbench spanning different stages of the business, not an inventory of Justin’s actual equipment or surroundings.

There’s a post from 2007 where I tell a computer forum that I run a PC repair business and then explain that my own PC has developed a problem I can’t figure out.

That feels like a fairly honest company brochure.

Windows XP was doing the kind of thing that makes a technician start doubting the basic agreement between a button and an action. Programs wouldn’t launch. Parts of the interface stopped responding. The machine was producing plenty of symptoms and being less generous with explanations.

I’d tried things. I was asking what to try next. I wanted to understand the failure instead of simply making it disappear with a reinstall. Nearly twenty years later, that last part sounds familiar enough to be a little embarrassing. Apparently I have been myself for quite a while.

The post is also useful evidence of something less dramatic: by then, I was already doing computer repair as a business. There wasn’t a future entrepreneur in the thread describing his vision. There was a working technician with a troublesome computer and a question.

The earlier trail is scattered across websites and forum discussions. By 2004 and 2005, there were online stores under KCSales, including allgardenfurniture.com and time4neon.com, built around osCommerce. That history contains a lot of practical work behind the tidy phrase “online store.” Product information, images, hosting, catalogs, checkout. All the parts that have to agree before the customer can do the apparently simple thing at the end.

A website can look finished while some essential part is still being an asshole.

I learned the work by getting into the work. The surviving record shows projects and questions accumulating. A business-directory record places KC Computer Services’ start in 2005. That’s one milestone in the trail; it isn’t a reason to pretend every stage happened on one official morning. Making things, trying things, repairing things, and becoming responsible for things can overlap for a long time before hindsight straightens them into a timeline.

By 2009, there’s a client-server troubleshooting discussion. By 2011, I’m asking about using a tablet for client agreements. Different problem, same habit: there’s a process here, it’s awkward, can technology make it work better?

I particularly like that agreements are part of the history. They’re a useful correction to the romantic version of a technology business, where you apparently spend all day making interesting machines do interesting things. Somebody still needs to understand what work is being done. The information needs to be recorded. The practical relationship between the people matters as much as the equipment.

Eventually, a lot of the job becomes responsibility for what happens after the exciting part.

Does it still work? Can the person use it? Is there a way back if it fails? Have I explained the result in words that help? A clever fix that leaves somebody confused has left part of the problem sitting on their desk.

The equipment has expanded over the years. Computers, networks, Wi-Fi, cameras, phone systems, backups, software. There’s more to learn, and there’s always some new variation on an old inconvenience. Running a business means deciding which of those things needs attention now and leaving enough information that the next visit to the problem doesn’t begin from nothing.

I was also sick through these years. The work didn’t happen in a separate, unlimited-energy version of my life. That helped make wasted effort something I cared about reducing. If a better process could remove an unnecessary step, there was a practical reason to build it.

Looking backward, I can see the continuity more easily than a single beginning. Websites became stores. Technical interest became work people relied on. Questions became experience, and experience became responsibility for helping somebody else through the next problem.

The old records are an oddly good way to remember the beginning. They show what needed doing, what I was trying, and where I had to ask for help. They also preserve my public admission that my own computer was currently winning.

Apparently I was starting a business.

I was definitely still troubleshooting.

Source and edition note

Based on Still Building, chapters 5–7, and its historical trail. The 2007 post was read directly on September 10, 2026. The storefront page returned 403; 2004–05 stores, the directory’s 2005 start date, and 2009/2011 milestones retain the memoir’s source status. Directory start and legal formation are not treated as identical.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

• Justin’s 2007 PC-repair forum post
• 2004 storefront discussion
• KC Computer Services directory record
• 2009 client-server discussion
• 2011 tablet agreement discussion

Interpretation of the remembered object at Grandma Ann’s; the exact artwork, furnishings, and scene remain unknown.

I can’t give you the manufacturer. That would make this much easier.

I can tell you it was above the couch at Grandma Ann’s house. She lived in a trailer in Iowa. The picture was huge, at least in the way I remember it. About as long as the couch. An old-fashioned street scene, buildings, a bridge, and little lights.

The little lights actually worked.

That’s the part I keep coming back to when I try to explain it. The windows weren’t only painted to look warm. The streetlamps weren’t just dots of yellow. There was light in the thing. Dim, warm light inside a little world somebody had made and hung on the wall.

I loved it.

It’s a funny thing to carry for years: a fairly strong attachment to an object you can’t reliably name. Memory has kept the features it cared about and discarded the information a search engine would find helpful. Somewhere there may have been a label with a model number. My brain decided we could manage without it.

Excellent archival practice, young Justin.

When I started looking for something like it again, I ran into the difference between recognizing the category and recognizing the thing. An example could have illuminated windows and an old street and still feel wrong. Another could be close enough to bring back some of the feeling while clearly being a different scene.

The search became partly about the picture and partly about figuring out which details had survived. How much was the object? How much was the size it seemed to have when I was a kid? How much was the way the light felt in that particular room?

I don’t have an exact inventory of what was painted in it. I have the couch underneath, the street scene above, and that wonderful fact that somebody had made the lamps light up.

That fact remains enough to interest me.

I’ve spent a lot of my life enjoying things that do something. A radio brings a distant voice into a room. A little arrangement of components changes what becomes possible. A page somebody built connects a person to information they didn’t have. I like seeing the relationship between the pieces and the effect.

The picture had an effect I could understand without taking it apart. A window with light behind it feels different from a window drawn on a surface. It invites you to pay attention. The scene has one small extra layer of reality, even though you know perfectly well it’s a picture.

I don’t need to make myself a childhood engineering prodigy to explain why I liked it. I was looking at a cool thing at my grandma’s house. Plenty of people would have liked it. My particular contribution was apparently to remember it long enough to give myself a research project decades later.

There’s affection in that project that no product match can entirely resolve. If I found the exact model, I would have the model. I wouldn’t have recovered the room, the time, or being the kid who saw it there. A purchase can put an object on a wall. Memory brings the rest on its own terms.

Still, I understand wanting something close.

You can miss the small ordinary things that made a place itself. The things nobody would have thought to document because they were simply there. A couch. A picture. Little lamps that worked. They don’t have to be rare or expensive to take up a permanent bit of space in your history.

I have worked with a lot of screens since then. Brighter ones, sharper ones, things capable of displaying almost anything. That doesn’t make the dim little lights less interesting to me. Their limits were part of what they were. One scene, one effect, enough to hold a kid’s attention.

The exact picture is still uncertain. The attachment isn’t.

If I find something close, I’ll know what I’m looking for before I know what to call it.

The streetlamps will actually light up.

Source and edition note

Based on Still Building, chapter 2. Preserves the Iowa trailer, couch, old street scene, bridge, warm lights, and later search. Size is explicitly remembered rather than measured. No product identification or childhood dialogue has been supplied.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

Skill and the need for gentler working conditions can occupy the same room.

I can explain a complicated network problem and still need the screen turned down.

That seems to cause more confusion than it should.

People get to see the answer. They see that I understand the equipment, can follow the failure, and know what to check. That’s real. I’ve spent years learning how to do this work. But the answer doesn’t come with a display showing what it cost me to produce it.

There’s no little status window underneath saying how much pain is present, whether a migraine has already eaten most of the afternoon, or how expensive the next conversation will be.

Apparently I should have included better telemetry.

I run KC Computer Services while living with chronic illness. Those two facts have to fit into the same day. Work brings responsibilities. My body brings conditions that don’t consult those responsibilities before becoming difficult. Being self-employed gives me some room to arrange things, and it gives me plenty of things that still need arranging.

Knowing how to solve a problem is one resource. Having the energy to solve it, explain it, record it, and handle the surrounding work is another. They interact, but they aren’t interchangeable. I can’t withdraw extra energy from the account marked “knows a lot about computers.” I have checked.

This is part of why an ordinary task can be surprisingly expensive. The task itself may be short. Getting into it, shifting attention, handling the interaction, and recovering the thought I was working on can take more. Add pain or fatigue, and the description on paper becomes a poor estimate of the work involved.

I understand why somebody looking from outside might miss that. Much of the cost is invisible. What bothers me is when the visible competence gets used to erase the invisible cost. If I managed something difficult, then apparently I must also be fine for everything else.

The difficult thing may have used what I had.

This is why I care about ways of working that preserve capacity. Remote access can mean solving a problem without spending energy on a trip that adds nothing to the repair. Clear written information means I can check the facts without trying to hold a whole conversation in my head. Good documentation can prevent the next round of confusion.

Those things also help the person who needs the work done. A clear answer is easier to use. A reliable system needs less emergency attention. A useful record means we don’t have to rediscover the same problem next time. There’s value in doing the work in a way that leaves less unnecessary work behind it.

I don’t think choosing that route requires an apology.

The trouble is that efficiency can hide its own reason. Somebody sees me solve something remotely and sees the convenient part. They don’t necessarily see the energy that staying home preserved, or what an avoidable trip would have taken away from the rest of the day.

The rest of the day matters too. I have Shelly and Michael. I have things I want to do because I’m a person, including things with no useful business outcome whatsoever. Being good at work doesn’t give work first claim on every usable part of me.

Sometimes the adjustment is small: send it in writing, reduce the noise, make the next action clear. Sometimes there is no clever adjustment available and I need to stop. A better workflow doesn’t make rest obsolete. I’m interested in tools, but I haven’t found one that turns a person into an unlimited resource.

I’m proud of being capable. I want that part of me in the picture. I also want the picture to include what it takes to keep doing things while sick. Otherwise people are trying to understand the result with half the information missing.

You can trust that I know what I’m talking about and believe me when I say I’m tired. You can value the work without assuming I had an easy time doing it.

And if I ask you to turn down the screen, we don’t have to reopen the entire question of whether I understand the network.

The screen is just too fucking bright.

Source and edition note

Based on Still Building, chapters 1, 7–9, 11–12. No specific customer event, missed obligation, or medical outcome is invented. This is personal experience, not general medical guidance.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

A visual metaphor for better information about oneself, not a depiction of a diagnostic appointment.

In December 2024, at forty, I found out I was autistic and had ADHD.

By then I had already put a fairly substantial amount of wear on the equipment.

I had a business. I had a family. I had years of experience being sick and decades of experience being me. There was a whole life in progress when somebody finally supplied information that would have been useful near the beginning.

I spend a lot of time looking for the missing detail in a technical problem. The setting nobody mentioned. The part of the documentation that changes how you interpret everything else. It was a little strange to discover that I had been doing my own life with significant pages missing.

The assessment didn’t make the phone quieter. It didn’t make a vague instruction clear. It didn’t arrange all my interests into an orderly queue or give me the ability to begin every task as soon as I decided it mattered.

What it changed was the investigation.

Take communication. I prefer text. With text, the words stay where I can look at them. I can reread the question, check the detail, and answer the thing the person actually needs. A phone call asks me to process the information, the sound, the timing, and the interaction together. Those are different demands, even when the topic is identical.

Knowing that lets me ask for a different method. It gives the preference a practical purpose I can explain. The person still gets an answer. I have a better chance of giving a useful one without spending everything I have on the delivery mechanism.

Or take starting something. I can be deeply interested in a complicated technical question and still have trouble beginning an ordinary task. That looks ridiculous if the only scale you use runs from easy to difficult. It starts looking more understandable when you ask about clarity, interest, interruption, energy, and what the first action actually is.

I have a lot of ideas. An idea becoming a task does not automatically make its entrance obvious.

These are things I can work with. Make the next step concrete. Put the information somewhere I can retrieve it. Reduce unnecessary noise. Allow a thought enough room to become useful. Notice when the remaining problem is that I’m exhausted.

I wish I had been asking those questions sooner.

That wish comes with some anger. Forty is a long time to spend without a useful explanation for parts of your own experience. By the time I had one, I had already made decisions, struggled through things, and developed ways of coping without that information. I can be glad to have it and pissed off about when it arrived.

I also have to leave the alternate life alone. I don’t know who I would have been with an earlier diagnosis. I can imagine that some things might have been easier, but imagining it doesn’t turn it into a history I can verify. I’ve got enough work understanding the life that actually happened.

And there are plenty of things in that life that still require their own explanation. I have Crohn’s. I have migraines. I have ordinary responsibilities. Every difficult day isn’t a single diagnosis announcing itself in a different costume. Sometimes several things are happening together. Sometimes I don’t know which one is doing what.

The useful change is that uncertainty can lead to a question instead of another demand to try harder.

I’m still capable of making a bad plan. I still have to take responsibility for what I do. Better information gives me a better chance of making a plan that survives contact with me. That seems like a reasonable place to start.

There’s no untouched version of adulthood waiting for me to begin correctly. This is the one I’m in, with people I love and work I care about already attached.

So I’m making notes in the manual as I go. This helps. That costs more than I thought. Put the instruction in writing. Leave room for rest. Try the clearer question.

Some of the pages arrived late.

I’m still going to use them.

Source and edition note

Based on Still Building, chapters 3, 8–10. December 2024 assessment timing and diagnoses are drawn from Justin’s shared history as preserved in the memoir, not a new medical-record review. No alternate childhood or clinical causation is asserted.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

A symbolic planning scene. The landscape is imagined, not the actual Colorado State Fair grounds; it does not depict a completed outing.

The Ferris wheel was the simple part.

I wanted to go on it with Michael at the Colorado State Fair. I’m his dad. There was a thing we could do together. That was the entire original project description.

Then I had to work out how to get myself around the fair.

How much walking would it take? How much standing? Could a scooter make it workable? Was one available? Would it fit in the trunk? Could Shelly and I handle moving it? Would it work on the ground we actually had to cross?

At some point, wanting to spend time with my son had developed a transportation department.

I understand equipment research. It’s a large part of what I do. Give me requirements and I’ll start looking at what fits them. But this was a reminder that being good at figuring things out doesn’t make it pleasant to have to figure out everything. Sometimes I would like an ordinary activity to retain its ordinary size.

A scooter that looks useful on a product page still has to be available. One purchase option sold out. Local availability became another problem. The question kept moving. First it was what would help. Then it was what I could actually get. Then whether the thing I could get would create a different problem before we reached the fair.

All of that was work, even though none of it was the outing.

I can stand. I can walk. Those statements tell you remarkably little about whether I can comfortably spend hours moving around an event. They don’t tell you how I’ll feel halfway through, what the walk back will cost, or how much useful energy I’ll have left for being with my family.

The equipment question starts making more sense when you include the whole day.

I wasn’t researching a scooter because I had lost interest in moving. I was researching one because I wanted to go somewhere. There’s a fairly direct relationship between those two things. A tool that reduces the cost of getting around can leave more of me available for the reason I left the house.

Michael is that reason in this story.

I don’t need to turn him into an inspirational child in an article about his dad. I wanted to do something with my son. He gets to be a kid who goes to the fair, with his own thoughts about it. He doesn’t need an assigned role in a lesson about my health.

And Shelly doesn’t need to become a piece of equipment in the plan either. Whether we could move a scooter was a real question involving both of us. A plan that quietly hands somebody else an impossible physical task isn’t much of a solution.

That’s what makes accessibility so practical. It lives in weights, distances, surfaces, transport, timing, and the people who have to make those things work together. An available seat matters. So does getting to the seat. So does getting home afterward.

I wish more of that work was visible before somebody decided an outing was simple.

There’s a temptation to finish this story at the top of the wheel, with the city below us and every logistical problem made worthwhile by the view. I haven’t established that ending in the account I’m telling here. I’m not going to add it because an article seems to want one.

The part I can tell is the distance between the wish and the practical possibility. How a father’s ordinary idea can become a search through equipment, availability, and what his body will tolerate. How much determination gets used before anything that looks like participation has even begun.

I still want tools that make those days easier. I still want the planning to lead somewhere beyond more planning.

The goal never became complicated. The route to it did.

I just wanted to ride the fucking Ferris wheel with my kid.

Source and edition note

Based on Still Building, chapter 14, and the original article brief. Whether the Ferris wheel ride occurred remains unconfirmed; the ending deliberately stays with the documented wish and planning.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

An imagined act of practical care; the nurse, laptop, and room are not exact reconstructions.

There is a laptop in the story of how I found out I had Crohn’s disease.

If you know me, that probably sounds inevitable. Of course the computer guy managed to get a computer into the hospital story. But the computer guy was a sick teenager first. Somebody had to bring him the laptop.

A nurse did.

I wrote about it in April 2006, when the experience was much closer than it is now. The account describes getting sick during high school, losing weight, trying to get through school with bathrooms that offered very little privacy, and going through appointments without a useful explanation. Eventually, at Children’s Hospital in Denver, the thing happening to me got a name.

Crohn’s.

A name is useful. It also comes with a whole new category of questions. You have an answer to what is wrong, and suddenly you need answers about how to live with it. You’re still the same kid. You still have the same body. Now there’s a word connecting it to a future you hadn’t planned for.

The laptop gave me somewhere to take those questions.

I could get online. I could learn about the disease. I could find people who were living with it. That last part matters as much as the information. There is a difference between reading that a condition exists and discovering actual people on the other side of the description. People with lives that continued after the diagnosis. People for whom the unfamiliar thing had become something they could talk about.

I don’t remember a specification sheet. I’m not going to improve the memory by inventing the brand, the screen size, or a speech the nurse delivered while setting it down. The detail that survived was the useful one: she got me access.

When you’re a teenager, growing up is already a fairly large assignment. Adding a chronic illness doesn’t cancel the original assignment. You still have to become a person while learning a lot of things you would have preferred never to need.

Having something I could investigate mattered. I couldn’t troubleshoot my way out of being sick. I could follow a question far enough to understand a little more than I had before. I could come back with another question. I could do something besides sit inside the uncertainty.

That’s the part of technology I keep coming back to, even after years of making a living with it. A tool becomes interesting when it gives somebody a useful next move. The next move might be fixing a network. It might be understanding a form. It might be finding another person who knows what the hell you’re talking about.

The nurse didn’t need to solve my whole life for that to count.

I think practical kindness gets underestimated because it doesn’t always announce itself. Sometimes it looks like noticing what a person could use and putting it within reach. There’s no requirement that the object be impressive. It has to help the person in front of you.

Years later, I’m still sick. I’ve built a business and a family life while dealing with that. There wasn’t a moment when the laptop opened and the difficult part ended. I wouldn’t want to tell that version, even if it made a cleaner article.

What happened was smaller, and it has lasted longer than a neat ending would.

Somebody brought a sick kid a way to ask questions, find people, and feel a little less cut off from the world. I became a person who cares a great deal about useful tools and the difference they can make in an ordinary day.

I can’t draw a straight line from one act to an entire life. I can recognize the act when I look back.

Before there were all the networks, projects, and equipment, there was a nurse who brought me a laptop.

I still think about that.

Source and edition note

Based on Still Building, chapter 4, and its account of Justin’s April 2006 post. The original post could not be independently retrieved in this pass (403). No exact onset age, diagnostic interval, nurse identity, or dialogue has been added.

Written with AI assistance in Justin’s requested voice from his shared history and the original Still Building memoir. Reflective prose is a reconstruction, not a verbatim interview. The illustration is an artistic interpretation; people, objects, rooms, and settings are not exact documentary depictions.

• KC’s Story — April 2006 account