Available for contract work San Diego, CA

Independent developer. Building useful software.

DevOfCodes is my one-person software company. This is where I share the products, tools and experiments I'm working on, and where you can hire me for focused contract development.

Discuss a project → Explore my work ↓

One person, an LLC, and work you can inspect. The background is live WebGPU, built with the open-source shaders library.

Who
Max WahlgrenSenior software engineer, seven years in enterprise internal tools. DevOfCodes is the work I do on my own account, alongside that job.
What I build with
.NET and TypeScriptASP.NET Core, NestJS, React, PostgreSQL, Docker. Python when the data wants it.
How I work
Written scope, shipped in unitsAcceptance criteria up front, a status record kept as I go, docs with the code.
Selected projects

Each one has a purpose, a state it's actually in, and something you can look at.

No client logos yet. Credibility here comes from the work itself. Statuses are kept honest; roadmap items are marked as such.

In daily useIn developmentResearch planPrototype
Live render · voxel model
01In developmentPrivate repository · 120+ merged PRs

Block-Based Build Instructions

Describe a structure in plain language. Get a locked design, a deterministic voxel model, a bill of materials, and step-by-step instructions you can follow in the browser.

BBI is an AI-assisted design and construction tool for block-based games, with Minecraft first. The language model runs the design workshop and never emits geometry: a procedural generator builds the canonical voxel model from the locked specification, and everything downstream (validation, materials, instruction book) derives from that model.

Works today
  • Design workshop → specification and palette → design lock
  • Procedural generation with a 3D viewer and validation findings
  • Bill of materials, build statistics, block catalog
  • Instruction book: chapters, steps, camera hints, quality checks, change marking
Roadmap
  • Revision engine: change requests with model diffs (phase 5, in progress)
  • Identity provider and first shared deployment
  • Exports and renders for sharing a build
Stack
.NET 10 modular monolith, EF Core, PostgreSQL, Redis, S3-compatible storage · React 19, TypeScript, Vite, Tailwind, Three.js
Process
Five-phase roadmap, one issue per deliverable, architecture decision records, a feature guide page for every shipped feature.
Ask for a walkthrough → Not deployed publicly yet. I'll demo it live.
DFS Command Center's Lineup Studio screen: a five-step workflow, a constrained lineup generator with an infeasible run explained constraint by constraint, and a candidates table with validation states.
Real screenshot · synthetic data
02In daily usePersonal tool · private repository

DFS Command Center

A research and portfolio workbench for daily fantasy sports on DraftKings and FanDuel. It consolidates provider exports, public sports data, projections, lineup construction, contest evaluation and results into one audited record.

I built it for myself, which means it gets used every slate. It imports the platforms' real export files (parsers verified against the actual downloads), ingests schedules, rosters, game logs and injury reports from public sources behind a licensing gate, generates lineups under constraints, and reconciles what was actually entered against what the plan said.

What it refuses to do: it never enters a contest or moves money, nothing in it says "profitable", and a feature that isn't ready shows an explicit unavailable state instead of a placeholder that looks real.

Under the hood
  • Constraint solving with OR-Tools CP-SAT, portfolio optimization with HiGHS
  • Monte Carlo contest evaluation with uncertainty reported apart
  • Bitemporal rosters, append-only game logs, a reviewed identity queue
  • Fourteen export gates, every input fingerprinted and re-checked
Stack
Python 3.12, FastAPI, SQLAlchemy, Celery, Polars, SciPy · React 19, TanStack Query, Tailwind 4 · Docker Compose, Prometheus
Ask for a personal trial → Personal data stays personal, so there's no public instance. A trial is a private workspace of your own.
Live render · gradient as text
03Research planWritten October 2026 · not started

Open Editor Platform

A plan for a fully open-source editor SDK that gives software developers and book authors equal standing: one integration surface, two editing profiles, a shared platform for comments, versions, search and optional AI.

The recommendation is to reuse what already works (CodeMirror 6 for code, Tiptap's open-source packages on ProseMirror for manuscripts, Yjs for collaboration) and to own the contracts around them: a book model with stable chapter IDs, portable schemas, conversion fidelity for DOCX and EPUB, and release gates that are published rather than promised.

Honest note: the plan is sized for a team of eight to ten. I'm working out what a one-person first slice looks like, and whether to start it in the open.

In the plan
  • Survey of CodeMirror, Monaco, Ace, ProseMirror, Lexical, Slate and friends
  • Three-layer product: surfaces, capability packages, workspaces
  • Architecture contracts for documents, collaboration and AI proposals
  • Release gates, benchmarks and a twelve-month delivery plan
Proposed stack
TypeScript, CodeMirror 6, Tiptap OSS / ProseMirror, Yjs, Hocuspocus, Web Workers first; Apache-2.0 for new code
Read the plan → About 3,000 words with sources.
Live render · lattice
04PrototypeRuns locally · no customers

The DevOfCodes platform, and Falcon

A multi-tenant SaaS foundation I built to learn what a security-first platform costs to get right, with Falcon, a project and task manager for engineering teams, as the first service on top of it.

Seven deployable services from one compose file: Identity (OpenID Connect, MFA, step-up auth), a Control Plane for plans, entitlements and a service registry, a Gateway that validates tokens and enforces policy and rate limits at the edge, an append-only Audit store, and Falcon itself with PostgreSQL row-level security per tenant.

Falcon works end to end on my machine. It has no users, and I'm not selling it. The platform underneath is what I keep: it's the foundation for the next product, and a game experiment (GridForge) already reused it by treating each world as a tenant.

Stack
.NET 10 with OpenIddict · NestJS 11 on Fastify · PostgreSQL with RLS · Redis · RabbitMQ · BullMQ · React 19 · Prometheus and Grafana
Status
Working prototype. Not deployed. Kept as the base for future products rather than marketed as one.
Need something like this? →
Work with me

Three kinds of project I can deliver with confidence.

Each one is something I've already done for myself, which is the only kind of promise I'm comfortable making on a page like this.

Build a small web application, end to end

Spec, data model, API, UI, auth, and a Docker deployment you can run anywhere. Typically .NET or Node on the back, React on the front, PostgreSQL underneath.

Evidence: BBI, the platform

Turn a messy data workflow into a reliable pipeline

Imports from awkward files, validation that opens issues instead of silently fixing things, provenance on every row, scheduled jobs, and reports people can trust.

Evidence: DFS Command Center

Finish or harden something you already have

Authentication, multi-tenancy, background jobs, observability, tests and documentation for a codebase that works but isn't yet something you'd hand to a stranger.

Evidence: the platform, BBI's cross-cutting track
About

Hi, I'm Max.

I'm a software engineer in San Diego. I've spent seven years building internal tools and systems across enterprise operations, going from analyst to senior engineer, and I've watched the same problems repeat on every team: context that lived in a chat thread nobody could find, decisions that couldn't be traced, software that worked until someone else had to maintain it.

DevOfCodes LLC is the work I do on my own account, alongside my full-time engineering job. I build things I want to exist, I document them as if a stranger will take them over tomorrow, and I take on a small number of contract projects where that way of working is worth paying for. Because it runs alongside a day job, I only take work I can scope honestly and deliver on the schedule I quote.

If you've read this far, you probably have something in mind. Send it over. I read every message myself and reply, usually within a day.

Max Wahlgren
Founder and engineer, DevOfCodes LLC
San Diego, California

Discuss a project

Tell me what you're trying to get built, roughly when, and anything that already exists.

Or email directlyhello@devofcodes.com

Delivered straight to my inbox by a small function in my own AWS account. No third-party form service, no newsletter, no automation.

Got it.

Thanks. I'll read it and reply personally, usually within a day.