Full-stack developer in Los Angeles. I build web products and the unglamorous internal tools that keep them running after launch. I like software that is honest about what it does and stays that way once the demo is over.
You probably landed here because this repo shares my name. Convenient. So here is what I have actually been building.
Persistent memory for AI coding agents. Findings, tasks, and patterns live as markdown in a git repo you own, so the next session starts where the last one ended. No database, no lock-in. Plays nice with Claude, Copilot, Cursor, and Codex.
Spreadsheet behavior for any table. Headless React hooks for inline edit, range select, the fill handle, and copy/paste. Drop them on shadcn, Material, Fluent, or a plain old table element. MIT licensed.
Max for Live devices written in Python instead of clicked together in a GUI. Pure standard library, ships to PyPI, and carries the test coverage to prove the .amxd files actually load.
github.com/alaarab/m4l-builder
An MCP bridge for Ableton Live. Around 170 tools for driving sessions, clips, devices, and the mixer straight from an agent.
A pattern is showing up here: I make music in Ableton, I got annoyed at the tooling, and half of these projects are what came out the other side.
A full ITSM platform you run in the browser. On top of the ticket views, Atlas mirrors every ticket to disk as markdown and exposes them to any AI tool through MCP, so the same queue lives in your editor and your agents too. The markdown mirror is loopback-only with a read-only allowlist, with sigstore-signed releases and an SBOM. Private for now — drop me a line if you want a look.
Thirteen years at ADM Associates. I built Intranet, a project-based ERP that grew into the company's primary system and got licensed to clients — the one that replaced Deltek Vision. I also built out the engineering team, set up CI/CD on GitHub Actions, and ran SOC 2-compliant Linux servers and on-prem infrastructure.
These days I'm rebuilding that ERP from scratch as Intrapath — React on Bun this time, with the workflow modeled right from the data layer up.
- Email: alaarab@gmail.com
- LinkedIn: ala-arab
This doubles as my portfolio site: a Bun-native app with React 19 and TypeScript 6. No meta-framework. Bun handles the dev server, bundling, and the production server. Content sits in one typed file, so projects update without anyone touching the layout.
bun install
bun devThen open localhost:3000.
Project content lives in src/data/siteContent.ts and styles sit in src/styles. bun run build bundles the app, builds a server-render bundle, and prerenders one static HTML file per route (scripts/prerender.ts) — each with its own title, description, canonical URL, Open Graph card, and server-rendered body — so crawlers and social unfurlers get real content and metadata, not an empty shell. React hydrates the prerendered markup on the client. Unknown URLs return a real 404. bun run og regenerates the social cards under public/og/. Run bun run typecheck and bun run build before shipping anything; bun start builds and serves the static output.