01
Build the irritating thing
Most projects here began with a specific friction I could point at: a clumsy channel guide, an unsafe territory edit, a repeated CRM lookup, or an Arizona car that should pre-cool itself before a scheduled drive.
About the person leaving tools everywhere
Hey, I’m Jack. You can call me JBigs.
I build, break, and optimize things for work and for fun—software products, games, automation, AI tools, cloud systems, and the occasional custom object that did not need a personality until I gave it one.
Origin story, minus the cape
Curiosity survived contact with production.
I started pulling websites and code apart as a kid, mostly to understand why they worked and whether I could make them do something else. That instinct never left. It grew into enterprise software, sales automation, product engineering, game development, AI experiments, media systems, and hardware work.
By day, I work in technology and software management. Outside that lane, JBigs is the workshop where I can follow a problem—or an unusually durable joke—all the way into a functioning thing. Sometimes that becomes a maintained product. Sometimes it becomes a prototype, a postmortem, or a lesson I reuse somewhere better.
Workshop rules
How I tend to build.
02
Make the system real
I like the parts after the demo: retries, billing, releases, permissions, data boundaries, update paths, and the recovery screen somebody eventually has to use.
03
Keep the weirdness
Useful software can still have a point of view. That is how an immortal snail became a horror-game pursuer, Google Earth gained shared skies, and a physical clock learned to scream insults.
04
Label the ending
Released, building, prototype, closed, and discontinued mean different things. The archive keeps failed and retired projects visible because the lessons are part of the work.
What is actually in here
A portfolio with more than one species.
Flagship systems
6 deep case studies
Released products, production-shaped systems, a personal reef dashboard, and a long-running psychological horror game.
Workbench
12 focused builds
CRM utilities, media experiments, tiny interfaces, and concepts built far enough to answer the original question.
Archive yard
7 visible endings
Completed, retired, and low-maintenance work, preserved without inflating its current state or erasing what it taught me.
Field notes
The posts survive too
Original JBigs articles remain the running notebook behind many projects, experiments, and decisions.
Two doors, one builder
JBigs is the playground. Bigbee Solutions is the business office.
This site is personal: it is allowed to be playful, unfinished, highly technical, and honest about dead ends. Bigbee Solutions is where consulting, CRM applications, AI systems, and commercial engagements get the quieter meeting room they deserve.
Client-derived work stays out of this portfolio unless publication rights and every artifact are explicitly approved.
Want the evidence instead of the biography?
The Project Index is the direct route. Every public build has a status, story, technical scope, and a stable page.