Making Systems Do What I Meant by Jeremias
Jeremias's entry into Varsity Tutor's November 2026 scholarship contest
- Rank: 88
- 0 Votes
Making Systems Do What I Meant by Jeremias - November 2026 Scholarship Essay
I already solve problems for a living, but most of them still live in a building. I work on building automation systems at a NASA facility. Day to day I keep the mechanical side running and I program the controls that tell the building what to do. When something goes wrong, it is rarely a single broken part. More often the system is doing something different from what the people using it think it is doing.
That's the academic skill I want to develop further: problem-solving, especially the kind you do in software and in the way a system is designed.
I'm a first-generation college student. I came up through the trades and community college, and I'm working toward a master's in computer science at Full Sail University. I went back to school because the problems I want to take on now are not only about keeping one facility running. Through my studio, Obsidian Crow Studios, I'm designing and building games. That work asks the same question I already face on the job, just in a different place. What is this system actually doing, and how do I get it to do what I meant?
Out in the field I've learned not to guess. If a space will not hold temperature, I don't start swapping parts at random. I trace how the system was set up and check whether the program is following the sequence we think it is. Then I compare that to what is actually happening in the room. That habit has kept me honest. It has also shown me the gap I still have. I can program building automation, but I want the computer science behind it so I can build more than controls.
That's what the master's program is for. I'm not trying to become a different person. I'm trying to take a skill I already use at work and make it strong enough to carry into software and game design. In class I want to get better at defining a problem before I rush to fix it, and at checking my work against reality instead of against what I hoped would happen.
That kind of problem-solving supports the goals I'm actually chasing. At work, it means I can build and maintain systems that operators can trust. In my studio, it means I can take a game idea and keep working it until the design holds up when someone else plays it, not only when I already know how it is supposed to feel. I'm doing this later than a lot of students, and I have children and a grandchild in mind while I do it. I don't need a degree to look impressive on a wall. I need the skill so the next things I build actually work for the people who use them.
If I can develop that kind of problem-solving in school and carry it back into my job and my studio, the time I'm putting in will have done what I went there for.