DBSoftware, maps & interaction
Menu

Drew Baker / personal portfolio

Software · maps · interactive experiences

I turn data and complex ideas into usable software.

My work brings together software, maps and interactive experiences. I set the direction, make product decisions and work with Codex to develop and refine the result.

Selected projects.

Cooperative game / Handshake

Wildfire Response

A cooperative browser game about protecting a community with limited resources. I shaped the product direction and used my first playtest to refine the map, controls and consequences.

Playable prototype · evolving

Explore Wildfire Response
Historical Wildfire Response planning screen with a terrain map, community sites and resource controls.
Historical v0.27 synthetic development fixture · gameplay disabled · AI-assisted terrain art.

Data + sound / NCAA challenge exploration

After the Tip

I redirected a score catalogue into a shared-clock comparison of Purdue’s games and a screened NCAA season, refining the question and sound direction.

Exploratory challenge prototype · not submitted

Explore After the Tip
Purdue's games30 games · both sides
Above: PurdueBelow: Opponent
The screened season6,002 games · both sides
Above: Home teamBelow: Away team

Mean positive lead contribution · points per game · regulation only. Descriptive means, not confidence intervals. Purdue’s games are included in the season; the above/below orientations differ, not a team-strength comparison.

Environmental GIS / ASM540 term project

Heat exposure across
West Hawaiʻi reefs.

I framed an environmental question and worked through GIS choices to compare satellite heat exposure over historical reef habitat. The saved comparison challenged my starting hypothesis.

Regional comparison mapped · research in progress

Explore West Hawaiʻi heat exposure
20152015 saved coastal grid: assessed habitat cells share the highest annual peak heat-stress class; unavailable cells are hatched.
20192019 saved coastal grid: the same historical habitat has a mix of annual peak heat-stress classes; unavailable cells are hatched.
Saved data-only redraws · annual peak satellite heat exposure over historical habitat—not observed reef condition. Read the full maps and NOAA source credits in the case study.

Satellite data / editable ArcGIS atlas

Nepal Satellite Atlas

I defined an ArcGIS atlas I could open, compare and export, then guided its maps and browser presentation.

Exploratory GIS · local atlas and maps

Explore Nepal Satellite Atlas
Full paired radar atlas for 16 and 28 August 2026, with a shared display scale, dates, partial coverage and source credits.
Unregistered visual experiment—not a mapped landslide result.
ASF DAAC HyP3 2026. Contains modified Copernicus Sentinel data 2026, processed by ESA.

Flagship 01 / experimental research portfolio

BurnLens

Making a research release readable.

I set the audience and public story for an experimental computer-vision and geospatial project, then owned the publication decisions.

Public v0.56.0 research portfolio release

Release details

BurnLens reached a public, complete Phase Six portfolio release: v0.56.0-baseline-first-portfolio-release at commit e2e0b778; the later evidence snapshot is a741111d, four commits after the release.

My role
Drew set the portfolio thesis, target audience, use boundaries, owner stop conditions, and publication direction, and owned the human decisions; Codex was assigned technical, product, and reliability direction within that owner-defined envelope.
Result
BurnLens reached a public, complete Phase Six portfolio release: v0.56.0-baseline-first-portfolio-release at commit e2e0b778; the later evidence snapshot is a741111d, four commits after the release.
Limit
BurnLens is experimental portfolio evidence, not official wildfire information, emergency guidance, or operational decision support.
Read BurnLens case study
Release intentVerified releaseLater snapshot
Release
v0.56.0 / exact public checkpoint
Snapshot
Four commits after the release
Boundary
Experimental / non-operational
A field-atlas reading: the release, later evidence snapshot, and use boundary stay distinct on the same sheet.

Flagship 02 / synthetic software testbed

Runbook Sentinel

Making incident response easier to inspect.

I developed a synthetic incident-response testbed that separates diagnosis, proposals and permission to act, and owned its release.

Released synthetic testbed · no real systems connected

Release details

Verified synthetic testbed with a public v0.0.20 release and zero real systems connected.

My role
Repository author and release owner for the pinned public checkpoint.
Result
The pinned v0.0.20 synthetic release passed its exact deterministic gate and excluded the weaker local-model candidate.
Limit
A released synthetic testbed with explicit infrastructure, identity, trace, security, and evaluation limits.
Read Runbook Sentinel case study
  1. 01Read evidence
  2. 02Diagnose
  3. 03Propose only
Reasoning stops hereAuthority is separate
  1. AApprove once
  2. BCheck policy
  3. CMutate synthetic state
Two rails meet at an explicit authority break; model output never becomes permission.

Swipe or scroll to explore. Each project opens into its full story. Browse all work

On my workbench

Follow the work.

A selected, dated view of five projects: what is recorded, what is taking shape and what is still open. Checklist counts describe listed tasks, not effort or whole-project completion.

Open project dashboard

How I work

I shape the question, decide what the result needs to do and refine it through use. Codex assists with research, implementation and testing; my contribution is direction, product decisions and review.

Direction + development
Drew / Direction and decisions
Choose the problem, set the audience, critique the experience and own decisions about what to share.
Codex / Development assistance
Help research, build and test the work within the direction I set. The case studies describe that collaboration rather than imply sole manual implementation.