Why I Built GUSPowerFit: Where Discipline in the Gym Meets Discipline in Code

I squatted 465 pounds on a random Tuesday in my home gym. No spotter, no hype man, no crowd. Just me, the barbell, and a squat rack I bought secondhand off Facebook Marketplace.

That lift didn’t happen because of talent. I’m not genetically gifted for powerlifting. I’m 5’9” with average leverages and a lower back that complains if I look at a deadlift wrong. That 465 happened because I showed up, followed the program, and did the boring work for months before that one exciting rep.

And that, weirdly enough, is the exact same reason I can build software.

The Connection Nobody Talks About

Fitness people don’t usually talk about code. Developers don’t usually talk about squat maxes. But the crossover between powerlifting and programming is so obvious once you see it that I can’t unsee it.

Both require:

• Progressive overload — You don’t jump from squatting 135 to squatting 465. You add 5 pounds a week, sometimes 2.5. In code, you don’t go from “Hello World” to building a full-stack app. You learn one concept, apply it, then stack the next one on top.

• Consistency over intensity — One incredible workout doesn’t build strength. One all-night coding session doesn’t make you a developer. Showing up 4-5 times a week, every week, for months — that’s what produces results in both domains.

• Failing as a feature — I’ve failed lifts. Gotten pinned under the bar, had to dump weight, missed attempts at meets. Each failure told me exactly where my weakness was. In code, every bug, every crashed build, every deployment failure teaches you something you couldn’t learn from a tutorial.

• Following the program — The best lifters follow structured programming. They don’t walk into the gym and freestyle. The best developers follow structured processes too — version control, testing, code review, deployment checklists. Discipline isn’t sexy, but it’s what separates people who make progress from people who spin their wheels.

This connection is why I built GUSPowerFit.

What Is GUSPowerFit?

GUSPowerFit is my fitness brand and platform. It started as a way to document my own training — lifts, programs, progress — and turned into something bigger when people started asking me how I train and what I’d recommend.

The site covers powerlifting, strength training, and the mindset side of fitness. Not the “believe in yourself” poster-quote version of mindset. The practical version: how to structure training when motivation disappears, how to push through plateaus, how to make fitness sustainable when you also have a full-time job and a business to run.

I built the site myself, obviously. Same way I build client sites — clean code, fast load times, mobile-first design. It’s a real-world showcase of what I do at Gus Digital Solutions, except the client is me.

The Home Gym Setup

I train in my home gym. It’s not a commercial facility with chrome dumbbells and motivational quotes on the wall. It’s a power rack, a barbell, plates, a bench, and a pull-up bar in a space that barely fits all of it.

Here’s why that matters: constraints breed creativity.

I don’t have a leg press, so I learned to program squat variations that hit every angle. I don’t have cable machines, so I got creative with band work and tempo training. I don’t have a training partner, so I learned to be disciplined about safety — proper rack height, bail-out technique, realistic weight selection.

The same principle applies to building software as a solo developer. I don’t have a team of engineers, so I learned to use AI tools effectively. I don’t have a QA department, so I write tests and do my own code review. I don’t have a project manager, so I built my own systems for tracking work and managing client expectations.

Constraints aren’t limitations. They’re design parameters.

Training Philosophy

My approach to training is boring and it works. Here’s the framework:

Compound Movements First

Squat, bench, deadlift, overhead press. These are the lifts that build the most strength per minute invested. Everything else is accessory work — important, but not the priority.

In code, the equivalent is mastering fundamentals first. HTML, CSS, JavaScript. React or whatever framework you pick. Git. The terminal. These “compound movements” of web development make everything else easier.

Progressive Overload, Not Random Intensity

I don’t max out every session. Most training days are at 70-85% of my max, focused on building volume and technique. Heavy singles and PRs happen maybe once every 6-8 weeks during peak phases.

When I’m learning a new technology, I don’t try to build a production app on day one. I start with small projects, build volume and comfort, then push into harder territory once the fundamentals are automatic.

Deload Weeks Are Not Optional

Every 4th week, I cut volume and intensity by 40%. This feels like wasting time. It’s not. Deload weeks are where recovery happens, where accumulated fatigue dissipates, where your body (or brain) actually adapts to the stress you’ve been putting on it.

In work, this looks like taking a day to clean up code, reorganize files, update documentation, and not touch anything new. Developers who never take “deload weeks” burn out. I’ve seen it, I’ve done it, and it’s not productive.

Track Everything

Every workout goes in a log. Sets, reps, weight, RPE (rate of perceived exertion), notes on how it felt. This data is what drives programming decisions. If my squat has been stalling for three weeks, the log tells me whether it’s a volume issue, a recovery issue, or a technique issue.

I track my development work the same way. Hours spent, tasks completed, blockers encountered, lessons learned. You can’t improve what you don’t measure — in the gym or in code.

The 465 Squat: What It Actually Took

People see the number and assume I’m naturally strong. Let me break down what 465 actually required:

• 3 years of consistent training before I ever touched 400 pounds
• ~700 squat sessions at submaximal weights, building the pattern
• 2 lower back tweaks that forced me to learn proper bracing and belt technique
• Nutrition tracking — eating 3,200+ calories daily during strength phases, which is its own kind of discipline
• Sleep — 7-8 hours minimum, non-negotiable, even when I have client deadlines

The lift itself took about 4 seconds. The preparation took 3 years. That ratio — massive preparation for a brief moment of execution — is identical to software launches. A client’s website goes live in 5 minutes. The design, development, testing, and optimization took weeks.

Why Fitness People Should Build Websites

Hear me out on this one.

If you already have the discipline to follow a training program for months, you have the discipline to learn web development. The skill transfer is real:

• You understand periodization. Learning in phases (fundamentals → intermediate → advanced) is literally how programming curricula are structured.
• You’re comfortable with failure. Missed a lift? Try again next week. Code not working? Debug and try again. Same emotional regulation.
• You know that progress is non-linear. Some weeks your squat goes up 10 pounds. Some weeks it goes down 5. Code learning works the same way — breakthroughs followed by plateaus.

If you’re a fitness professional or gym owner and you need a website, check out what I build at Gus Digital Solutions. I understand your world because I live in it.

Why Tech People Should Start Lifting

And the reverse is also true. If you spend 8-10 hours a day at a desk writing code, your body is paying a price. Rounded shoulders, tight hip flexors, weak glutes, chronic lower back tension — this is the developer starter pack.

Strength training fixes all of that. Not yoga (though that helps too), not walking (though you should walk), but putting heavy things on your back and standing up with them. Squats fix posture. Deadlifts strengthen your posterior chain. Overhead presses open up your shoulders.

Beyond the physical benefits, lifting gives you a domain where progress is objective and measurable. In code, “good” is subjective. Did the client like it? Is the architecture clean enough? Is this the best approach? In the gym, you either lifted the weight or you didn’t. That clarity is refreshing when your day job lives in ambiguity.

The Crossover in Practice

Here’s what a typical week looks like for me:

Monday: Morning squat session (heavy day). Afternoon client work — usually the most technical tasks because my energy and focus are highest post-workout.

Tuesday: Upper body accessory work. Client meetings and project planning.

Wednesday: Rest day from lifting. Deep coding work — this is when I build features, tackle complex bugs, or work on Hollowborne (my game development project).

Thursday: Deadlift day. Content creation — blog posts, YouTube scripts, social media.

Friday: Light full-body session. Client reviews and wrap-up for the week.

Weekends: One session Saturday, full rest Sunday. Weekend work only if deadlines demand it.

The structure matters. Training at consistent times creates a rhythm that makes everything else easier to schedule around. I don’t decide whether to train — that decision was made when I wrote the program. I just execute.

Same with work. I don’t decide whether to write code today — the project timeline already decided that. I just open the editor and start.

What’s Next for GUSPowerFit

GUSPowerFit is growing. I’m working on training content — not cookie-cutter “12-week transformation” programs, but actual strength programming for people who want to get seriously strong while having a life outside the gym.

The site itself is a living project. I use it as a testing ground for new web development techniques before I apply them to client work. New Astro features, performance optimizations, SEO experiments — GUSPowerFit gets them first.

If you’re into powerlifting, strength training, or just curious about how gym discipline translates to business discipline, check out guspowerfit.com. And if you’re a fitness professional who needs a website that actually represents what you do, you know where to find me.

The barbell and the keyboard have more in common than you’d think. Both reward consistency, both punish shortcuts, and both require you to show up on the days when you really don’t feel like it.

465 pounds didn’t happen overnight. Neither did this business. And I’m not done with either one.