Brad Hobbs Dacula, GA

Work

Things I’ve built.

Client work, employer work, personal projects, concepts, and portfolio samples, each labeled for what it is. Client and employer work is shared with written permission; screenshots use fake data and leave out private details.

  • Client work built for a client, shared with permission
  • Employer work built as an employee, shared with permission
  • Concept designed to show an approach, for a fictional business
  • Sample a working example with fictional data or no data
  • Personal project something I built and use
Employer work · shared with permission
meeting-room app · session view
Meeting-room desktop app showing a session with its moderator and presenters, each with a Start button

Desktop + Web · Distributed systems

Event presentation platform: cloud, venue, and every room

Problem
At a large conference, hundreds of presentations have to reach the right room on time, often over hotel internet that drops out. Technicians need to watch and control every room at once, and speakers need an easy way to hand over very large files.
Approach
A cloud platform plus a small Kubernetes server at each venue that holds its own copy of the event and keeps running offline. RabbitMQ keeps the two databases in step, files are mirrored to on-site storage, and every meeting room runs a locked-down desktop app built from the same React code as the web apps.
What I built
I designed the architecture and led the team that built it, and I wrote major parts myself, including the meeting-room desktop app, the shared-views monorepo, and a developer tool that runs the whole stack locally. The platform includes a speaker upload app, an admin app, a kiosk-mode room app that runs PowerPoint, Keynote, PDF, and video, a live ops dashboard, .NET, Node, and Go services, and a virus-scanning file pipeline.

Built as an employee and shared with written permission. The code is private. The product name and logo are changed, screenshots use generated fake data from a local test environment, and the diagrams are redrawn.

Event presentation platform: cloud, venue, and every room

1 / 10
Meeting-room desktop app asking for the event PIN on a numeric keypad

Event PIN sign-in

Room PCs are shared, so technicians unlock them with the event’s PIN instead of a personal login.

  1. Connect to the on-site server, reach it remotely, or go straight to the cloud.
  2. The server checks the PIN and starts a session for that event only.
Client work · shared with permission
configurator · window wall in 3D
Configurator dimensions step for a custom window wall, with a 3D preview of four glass panels, a door, and a transom

Desktop · Electron + AWS

Storefront door configurator with 3D preview

Problem
Quoting a commercial aluminum door means turning an opening size into a frame, door leaves, glass, and hardware, then pricing all of it from a price list. Doing that by hand is slow, easy to get wrong, and the shop still has to work out the cut sizes again.
Approach
One desktop app built around shared pricing and manufacturing packages, so the estimator, the PDF, and the server all work from the same numbers. A step-by-step wizard, live 2D drawings and a 3D preview, and a small AWS backend for quotes, sign-in, and the price book, with a local cache so saves aren’t lost when the network drops.
What I built
I designed and built it on my own: the Electron app, the Fastify API, the MySQL database, and the AWS infrastructure in CDK. It covers 36 stock products (28 doors, 7 windows, and a custom window wall), dimensions from rough opening, frame, or door size, finishes, glass, and hardware, a 3D preview, porch layouts, customer and shop PDFs, emailed quotes with a customer approval link, a six-step order lifecycle, a price matrix, and an admin price book with an audit trail. Custom (non-stock) pricing is only partly mapped: some glass options still fall back to catalog prices, and only quote saves work offline.

Built for a client and shared with written permission. The code is private. The product name, logo, prices, and data are changed, the screenshots use fake data from a local test setup, and the diagrams are redrawn.

Storefront door configurator with 3D preview

1 / 10
Full-screen 3D preview of a dark bronze double storefront door with a panic bar and a mail slot, seen at an angle

3D preview

Any configuration can be opened full screen and turned around in 3D. The model is built from the same dimensions the drawings use.

  1. Options show up on the model. This is the panic bar added on the Add-Ons step.
  2. The mail slot sits on the active leaf, in the bottom third, where it was placed.
  3. Switch between the dimensioned 2D drawing and the 3D model. The 3D view is built with Three.js through React Three Fiber.
Client work · shared with permission
Sentinel · local synthetic preview
Sentinel chart workspace with a synthetic SPY candlestick chart, level dock, and watchlist

Desktop · Charting and supervised trading

Sentinel: a Windows trading workstation

Problem
Traders need to read charts, market levels, account state, and order checks together before making a decision. Those pieces are easy to lose when they live in separate tools and data feeds.
Approach
I built a Tauri desktop shell with React workspaces, a TypeScript gateway that normalizes market data, and a Go service that owns trading state and risk checks. Native access and broker credentials stay outside the web view.
What I built
I designed and built Sentinel solo. The code includes configurable chart layouts, studies and drawings, a level dock and watchlist, dashboard panels, an options chain and portfolio view, and an order ticket that leads to a separate review. The Go engine checks fresh broker evidence and coded limits before review and again before submission. Native market and broker features require their configured services; these captures use synthetic or illustrative development data.

The code is private and this client work is shared with written permission. Chart images use Sentinel's deterministic browser data; options images use its development-only illustrative fixtures and a fake masked account. No live broker order was placed.

Sentinel: a Windows trading workstation

1 / 7
One synthetic candlestick chart with a level table below and a watchlist beside it

Chart and level dock

The browser preview runs on deterministic synthetic bars and levels. The dock and watchlist keep related market context beside the chart.

  1. The browser capture is explicitly marked synthetic. These prices and levels are generated locally.
  2. The level dock lists status, price, distance from spot, volume, and source details.
  3. The watchlist stays available next to the active chart.
Concept · fictional business
oakstreetplumbing.example
Concept homepage for a fictional plumber with a call button, towns served, and a quote form
The same concept on a phone, with a sticky Call now button

Website refresh

Oak Street Plumbing concept

Problem
Many older small-business sites open with a generic welcome, never say which towns they serve, and hide the phone number in the footer as plain text that can’t be tapped.
Approach
Start with what a customer is trying to do on a phone, which is to find out whether you serve their area and then call. Put the services, towns served, and a one-tap call button on the first screen, and keep the quote form to three fields.
What I built
A responsive homepage concept with a sticky call bar on phones, clear hours, a list of towns served, and a short quote form. The business, phone number, and details are all fictional.

Oak Street Plumbing concept

1 / 2
Concept homepage for a fictional plumber with a call button, towns served, and a quote form

On a computer

A website-refresh concept for a fictional local plumber, with tap-to-call, the service area on the first screen, and a short quote form.

Sample · fictional data
community-resource-directory
Resource directory with a search box, category and city filters, and four result cards
The directory on a phone with stacked filters

Web · Accessibility

Community resource directory

Problem
People looking for local help need to filter quickly by need and city, and see right away how many options match.
Approach
Keep the public side small and clear, with one search box, two filters, a visible result count, and proper labels and focus states.
What I built
A React and TypeScript directory with automated tests. The records are fictional, and it hasn’t had a formal accessibility audit.

Community resource directory

1 / 2
Resource directory with a search box, category and city filters, and four result cards

On a computer

Searchable listings with category and city filters, a visible result count, and accessible form labels.

● Personal project · private beta
pickem · live game view
Pickem live game view showing Alabama at Georgia in the third quarter, with a live-updates status bar
Pickem on a phone with Georgia picked against the spread for 50 points

Mobile + Web · AWS

Pickem: live college football picks on every platform

Problem
A pick’em league needs picks, point totals, lock times, and live scores in one place, on whatever phone or computer each player uses, and the rules have to hold up on game day.
Approach
One Expo React Native codebase for all three platforms, on a serverless AWS backend. Lock rules are enforced on the server, and live scores flow from a sports-data provider to every open screen without a refresh.
What I built
Players pick games against the spread and wager points from a weekly budget. Game cards go live on their own: a scheduled AWS Lambda pulls scores every minute, and the app checks for changes every 15 seconds during games. Also: a standings table, graded history, a commissioner slate builder, Google and Apple sign-in, and biometric unlock on phones.

The production code is private. The linked repo is a small, rewritten sample of the shared-codebase pattern, with no backend, accounts, or live data.

Pickem: live college football picks on every platform

1 / 9
Pickem live game view with the score, quarter and clock, possession, and a live-updates status bar

Live game view

Scores, the game clock, and possession update on their own while you watch. No refresh, no reload.

  1. While a game is in progress the app checks for new data every 15 seconds (every 60 seconds in the hours before kickoff), and only re-renders the games that changed.
  2. These screenshots use the app’s built-in test scenarios, so this banner marks the data as simulated. Real games use the same screen.
  3. Score, quarter, and clock come from a sports-data provider. A scheduled AWS Lambda pulls them every minute and stores them in the database.
  4. Possession and down-and-distance come from the same live feed.
● Personal project · live
The workout tracker’s AI coach turning a request into a 30-minute cardio plan card

Web app · AI · AWS

Workout tracker with an AI coach

Problem
A flexible weekly routine didn’t fit fixed-schedule apps, none of them offered useful recovery guidance, and generic AI chat didn’t know my plan or my gym’s machines.
Approach
A calendar-first log, a rules engine that reads each workout and recommends recovery with its reasons, and an AI coach that gets the plan, this week’s workouts, and the gym’s equipment list with every question.
What I built
A multi-user React app with per-set logging, a recovery coach, a stretch guide matched to the muscles worked, and 8-week progress charts. The AI coach runs through the app’s own AWS Lambda, so API keys never reach the browser. It answers in plain language or returns a complete workout in the app’s own format, ready to add to today. It can use Claude or OpenAI; the live app currently uses OpenAI’s GPT-4o mini. Hosted on Lambda, API Gateway, S3, and CloudFront, defined with AWS CDK.

Workout tracker with an AI coach

1 / 9
AI coach chat answering which machine to use for the lower back and how to set it up

AI coach: gym questions

A real answer from the live app. The coach knows the gym’s actual machines, so it names one instead of giving generic advice.

  1. Each question is sent with the gym’s equipment list, the user’s plan, and this week’s workouts, so answers refer to real machines by model number.
  2. The chat goes through the app’s own AWS Lambda. The AI provider’s API key stays on the server and never reaches the browser.
Sample · fictional data
electron-web-shared-views
Workspace notes app with search, a category filter, and three note cards

Desktop · Electron

Desktop + web shared views

Problem
Teams that ship both a desktop app and a web app often maintain two copies of the same screens, and the two drift apart.
Approach
Keep one view and feature model, and let each platform supply only what’s different, like file access on desktop.
What I built
An Electron + React sample with a searchable notes screen that runs the same code in the desktop app and in the browser.

Desktop + web shared views

1 / 1
Workspace notes app with search, a category filter, and three note cards

Desktop + web shared views

One set of React views shared by an Electron desktop app and its browser version.

Sample · not deployed
Diagram with separate private delivery and moderation paths on AWS

Infrastructure · AWS

Private media pipeline in Terraform

Problem
Uploaded media needs to stay private while a review process runs, and published files need a controlled path to viewers.
Approach
Keep upload and delivery buckets separate; grant CloudFront access to one bucket through OAC and send new uploads through Lambda, Rekognition, and SQS for review.
What I built
A Terraform sample with reusable modules, environment variables, scoped IAM, a Python event handler, and validation tests. It has not been deployed or production tested.

Private media pipeline in Terraform

1 / 1
Diagram with separate private delivery and moderation paths on AWS

Private media pipeline in Terraform

A Terraform reference for private S3 delivery through CloudFront OAC and a separate image moderation event pipeline.

Sample · fictional data
ai-first-react-workspace
Work-item queue with totals, filters, and three fictional items

AI-assisted development

AI-ready React workspace

Problem
AI coding tools move fast, but without shared context and checks their changes are hard to trust and review.
Approach
Give the AI agent and the human the same architecture map, conventions, feature spec, and verification commands, and let CI fail if docs fall out of date.
What I built
A small work-item queue app inside a repo with agent guidance, docs-as-code, an implementation-ready spec, tests, and a documentation check in CI.

AI-ready React workspace

1 / 1
Work-item queue with totals, filters, and three fictional items

AI-ready React workspace

A repository set up so AI-assisted changes arrive with specs, tests, and docs a person can review.

Sample · fake AI provider

AI · Reliability

AI request guardrails

Problem
A single AI request can fail in many ways, like bad input, a duplicate click, a slow response, or output in the wrong shape, and each needs handling before it reaches a customer.
Approach
Wrap every call in the same small set of guardrails and record what happened, so failures are visible and repeat requests don’t cost twice.
What I built
A dependency-light TypeScript library with tests and a demo. It uses a fake provider, so it runs without API keys, costs, or customer data.

More on GitHub, including offline sync, AWS CDK and Terraform infrastructure, and a .NET + PostgreSQL API.

Next step

Want something like this for your business?

Pick whichever is easiest. If there’s a good fit, I’ll send a short written scope. If not, I’ll tell you, and you’ll leave with at least one useful idea.

I reply within one business day.