Jesus Armstrong

Why this persona fits the audience

He is a graduate student who also builds portfolio pages, hackathon demos, and small sites for friends. He prefers free resources, often comparing templates in browser tabs while hand-editing HTML and avoiding paid design subscriptions.

• Age: 24
• Location: Philadelphia, Pennsylvania, US
• Occupation: Graduate student and side-project builder
• Income: $24k stipend + side-project income
• Education: Master's student in information systems
• Company size: N/A (academic setting, individual projects)
• Years in role: 2 years (as grad student), 4 years (side projects)

“There's always a free way to build something cool if you're willing to dig for it.”

Jesus Armstrong, 24, is a Master's student in Information Systems at a university in Philadelphia, Pennsylvania. His academic journey is supplemented by a deep-seated passion for building things on the web, a pursuit that began in earnest during his undergraduate years. He’s always been drawn to understanding how things work, which naturally led him to dissecting websites and experimenting with HTML and CSS. His current income consists of a modest $24,000 graduate stipend, supplemented by small payments for side projects, which he reinvests back into his setup – think better cables or a slightly faster SSD, never subscriptions. He lives in a shared house, a common arrangement for graduate students in the city, where utility bills are split and communal spaces often double as impromptu tech meetups. His approach to building is heavily influenced by his value of resourcefulness; he views the constraint of using free tools not as a limitation, but as a challenge to be overcome with ingenuity. Recently, he spent a significant chunk of time hand-editing the HTML and CSS for a friend's small bakery website, meticulously tweaking spacing and font sizes after finding that most free templates were either too bloated or didn't quite capture the 'artisanal' feel the friend wanted. He also just participated in a weekend-long hackathon, where his team built a functional prototype for a local community event app using only open-source libraries and free-tier cloud services. This experience reinforced his belief in the power of rapid prototyping and the efficiency of well-chosen, free frameworks. He’s constantly comparing different free HTML templates in browser tabs, meticulously hand-editing code rather than paying for design software or premium templates, a habit born from both budget consciousness and a genuine enjoyment of the low-level control it affords him. His academic work often intersects with his personal projects, allowing him to explore new concepts learned in class through practical application.

Background & daily life

A day in their life

Jesus's weekday typically begins around 8 AM after a slightly later wake-up than most. He grabs a quick breakfast of cereal or toast while checking emails and scanning Hacker News. His morning is usually dedicated to classes, lectures, or lab work on campus. Lunch is often a packed sandwich or something cheap from the university cafeteria, eaten while reviewing lecture notes. The afternoon might involve a study group session or library work. Evenings are his prime coding time. He'll head back to his shared house, make a simple dinner, and then settle into his corner workspace. He'll code for 3-4 hours, working on his Master's project, a personal website, or helping a friend debug their site, often fueled by coffee and a podcast. He tries to wind down by 11 PM, but sometimes gets lost in a coding rabbit hole, staying up until the early hours.

Lifestyle

Jesus lives a frugal but intellectually rich life in West Philly. His days are a blend of academic rigor and hands-on coding. He shares a house with other students, splitting utility costs and sharing communal spaces, which often become impromptu brainstorming sessions. His diet leans towards ramen and bulk pasta, with occasional splurges on cheap pizza. He walks or takes public transport to campus, using the commute to listen to podcasts or plan his next coding sprint. Weekends are a mix of intense hackathon prep, working on personal projects, and catching up on sleep. He prioritizes experiences and learning over material possessions, viewing his current financial situation as a temporary phase before his career takes off.

Work life

As a Master's student in Information Systems, Jesus's 'work' is primarily academic, involving coursework, research, and TA duties. However, his passion lies in building. He dedicates significant evening and weekend hours to crafting portfolio sites for himself and peers, developing quick demos for hackathons, and building small, functional websites for friends who need a web presence. He thrives on the problem-solving aspect of coding and the satisfaction of creating something tangible from scratch. His workspace is a corner of his shared living room, cluttered with multiple monitors, a mechanical keyboard, and a tangle of charging cables. Coworkers are mostly his fellow grad students, with whom he collaborates on group projects and exchanges coding tips. The pressure comes from looming deadlines for both academic assignments and personal projects, and the constant internal drive to learn new technologies.

Relationships

Jesus's closest relationships are with his fellow graduate students, with whom he shares academic struggles and celebrates small coding victories. They often act as informal peer reviewers for each other's projects. His family, back in his hometown, is supportive but doesn't fully grasp the technical intricacies of his work, though they encourage his pursuit of education. He has a few long-distance friends from undergraduate days who share similar tech interests, and they occasionally collaborate remotely on hackathon ideas.

How they decide

Jesus is a pragmatic researcher. When faced with a need, he'll first exhaust free and readily available options. He'll spend considerable time comparing different free templates or libraries, often opening dozens of browser tabs to evaluate features and aesthetics. He relies heavily on community recommendations, Stack Overflow, and open-source documentation. If a free solution is too cumbersome or doesn't meet a critical need, he'll consider a low-cost option, but only after extensive comparison and validation from peers or online reviews.

How they sound

Speaks with a moderate pace, often pausing to find the right technical term. Uses a fair amount of internet slang and developer jargon ('it's kinda janky,' 'that's a solid boilerplate,' 'just gotta refactor this bit'). Avoids overly formal language unless presenting in an academic setting. Can be enthusiastic when discussing a new coding technique or a clever solution, but generally maintains a calm, analytical tone. He's not afraid to admit when he doesn't know something, often following up with 'but I can look that up.'