Jawetzel LLC

About

Hi, I'm Joshua.

Software consultant based in Greater Baton Rouge. Six-plus years writing production code across enterprise teams and solo-shipped products.

Prairieville, LA · remote-proven

I started coding in 2004, scripting video games. When I saw something a game didn't do, I wrote the thing that made it do it, and I never really stopped. By the time I got to Southeastern Louisiana for a Computer Science degree, the hobby had turned into a career path, and school pointed it toward business software.

My first real job was at Lipsey's, a firearms distributor in Baton Rouge. I spent two years there on a full modernization of a large VB codebase onto .NET Core + React, covering both the customer-facing surface and the internal tools, rebuilt incrementally without taking the system offline. That shape of problem is the kind of work I kept going back to: an old system that still earns its keep, with real users on the other end, that needs to move forward without breaking.

Since late 2021 I've been on Fastlane, a compliance platform at Tri-Core. End-to-end feature work across API, web, data model, and rollout, collaborating with a development team and project managers for four-plus years. In the margins, I've shipped four solo products: a recipe site migrated off WordPress with a print-on-demand cookbook (CookJunkie), a pay-as-you-go scheduling SaaS for tutors (TutorTab), an offline-first POS for market vendors on both app stores (Vorbiz), and a gardening content site with AI-assisted drafting (Weekend Plant).

I treat AI as a teammate you give narrow, well-specified tasks to, then review. Most of what I build with agents is the operational plumbing around them (the batching, the dry-run mode, the review step) rather than the model call itself.

Consulting work runs through Jawetzel LLC, my Louisiana company, so contracts and invoices come from there. It's still a one-person shop; the entity is the paperwork, not a bench of subcontractors.

The site you're reading is public on GitHub if you want to see how it's built.

What I do

  • Legacy modernization: VB, classic ASP, and aging .NET surfaces migrated onto Next.js / .NET Core without downtime.
  • Solo-scope SaaS builds, end-to-end: Stripe, auth, calendars, and the integrations in between.
  • AI-native ops tooling: wrapping agents in dry-runnable, reviewable pipelines instead of letting them commit directly.

How I work

The work usually starts with a conversation rather than a spec. Before I write anything, I want a clear picture of what you're trying to do and why you need it now.

The answer isn't always more code. It can mean cutting scope, pushing back on an assumption, or realizing the real fix lives two layers below where we started. Once the shape is right, I build it and ship it.

Want to talk about a project?

I reply to every inquiry personally. Tell me what you're working on, and what's stuck.