Things I’m building, and what they cost me●

Fewer, harder projects. Each one lists the decision I had to get right and the one I got wrong first.

PROJECT 01 · ACTIVE · PRIVATE REPO

Xylodesk

An all-in-one career platform. Recruiting orgs get an ATS shaped around their real hiring workflow with role-based access; job seekers get one account, a real public profile, a resume builder, and fit-based matching instead of applying into a void. Built solo, from schema to UI.

For job seekers

Covers the basics you would expect: apply to postings, message recruiters directly. What sets it apart:

  • ›Application tracker: a kanban pipeline and list view, every application and its stage in one place.
  • ›In-app communication with the hiring team: one unified inbox for application threads and direct messages, not a portal per employer.
  • ›Structured, evidence-based job matching: six weighted requirement categories against your actual resume, not keyword overlap.
  • ›AI Career Coach: interview practice with per-turn feedback, market-backed salary negotiation guidance, and skills assessments you can choose to share with employers.Roadmap
For Orgs & hiring teams

Covers what any serious HRIS has to get right: strict multi-tenant data isolation, GDPR-correct compliance, scoped compensation visibility, enterprise SSO/MFA. What sets it apart:

  • ›End-to-end ATS: job posting with approval workflow, kanban pipeline, scorecards, and bulk actions.
  • ›Internal Mobility Portal: a personalized dashboard of internal openings, automatic eligibility guidance, and a career path visualizer mapping skill gaps to target roles.Roadmap
  • ›Org-wide skills graph: a live map of who has which skills, with gap analysis against upcoming needs.Roadmap
  • ›AI-driven career coach for internal mobility: reminders, learning nudges, and progress milestones as an employee works toward an internal move.Roadmap
  • ›A genuine feedback loop: peer-to-peer and manager feedback with sentiment analysis, so it stays constructive and visible instead of buried in a form nobody reads.Roadmap
Decisions worth defending
Fail-closed tenancy

acts_as_tenant configured so a query missing its tenant raises instead of silently returning every organization’s data. Deliberate cross-tenant paths carry an explicit record-level authorization check.

Two models, not one

Public candidate profile and internal HR record split early, so compensation data can never leak into a public page through a shared field.

Compliance by design

GDPR erasure that also respects employer retention duties: a 30-day window anonymizes retained records in place instead of deleting rows other data still references.

AI behind one gate

Every AI feature, resume suggestions, match scoring, reply drafting; checks the same explicit consent flag before it runs, rather than assuming consent from account creation or a prior feature.

Ruby / Rails 8GraphQLMySQLReactNext.jsTypeScriptSolidQueueGeminiTailwind CSSClaude CodeRepo private while in development — happy to walk through the code.
PROJECT 02 · IN USE DAILY

A review pipeline that gates my own pull requests

Working solo means nobody catches what you miss. So I built four specialized Claude Code subagents that review my work before it ships — AI as a second set of eyes, not a faster typist. Nothing non-trivial gets pushed until a hunt → fix → re-hunt loop comes back clean.

Architect

Reviews a design or open issue before any code exists: what's missing, what conflicts with the architecture, what's underspecified.

Bug-hunter

Line-level review of every diff for real defects — tenant-isolation leaks, authorization gaps, data-integrity and compliance risks.

PR-reviewer

Merge-readiness pass: does the change do what it claims, does it break something that worked, can each user see exactly what they should.

Flow-verifier

The dynamic check — actually runs the system against real flows like sign-in, applying, and data erasure to catch what static review can't.

PROJECT 03 · SHIPPED

This site

Built with Next.js and Tailwind CSS on a customized base template. The exercise was less the scaffolding and more everything on top of it: real content instead of placeholder copy, a deliberate pass on type scale and spacing, and a hosting setup that keeps the source (and the résumé it ships) out of a public repo while the built site stays public at the same URL.

Next.js (static export)TypeScriptTailwind CSSGitHub ActionsGitHub PagesCloudflare
How it’s hosted

No backend to speak of as it’s a static export, so “hosting” is really a build-and-publish pipeline. Source lives in a private repo; CI builds it and pushes the compiled output into a second, public repo’s gh-pages branch, which GitHub Pages serves. Cloudflare sits in front for DNS, the apex-to-www redirect, and TLS.

personal-siteprivate repo — Next.js sourceGitHub Actionsnpm ci · build · static exportBtaluW/BtaluW — gh-pagespublic repo, build output onlyGitHub Pagesserves the static filesCloudflareDNS · apex redirect · TLSwww.btalu.cavisitorpush to maincross-repo push (scoped PAT)servesproxiedHTTPS
Decisions worth defending
Private source, public site

Source, comments, and git history are private, only the compiled output is published. CI publishes only the compiled output; the source and its history never leave the private repo.

Static export, no server

No forms, no database, no server-rendered pages, so there's nothing for a server to do at request time. Static export means every page is just files, which is also what makes GitHub Pages hosting possible at all.

Redirect at the edge, not in DNS

The apex domain (btalu.ca) isn’t pointed at GitHub, it’s a Cloudflare-proxiedArecord with a Redirect Rule sending it towww. One less place (GitHub’s own apex-redirect mechanism) that has to agree with DNS.