Programming From Prison

A software engineer serving time in prison landed a full-time job at Turso after building a track record of open-source contributions—culminating in work on Project Limbo, a Rust rewrite of SQLite’s storage layer. The central takeaway is less about a feel-good comeback and more about a concrete pipeline: limited access to a computer, sustained daily output, and visible engineering work that eventually made outside recruiters look past incarceration.

The story traces how incarceration became an unlikely launchpad. After years of drug-related charges and a long sentence, he entered a prison college program that provided access to a computer with limited internet. That access reignited his programming drive, and he quickly outgrew the curriculum—spending roughly 15+ hours a day on projects and open-source contributions. He also credits prison-based remote work opportunities through the Department of Corrections, which allowed him to pursue legitimate employment if he met requirements and avoided disciplinary issues.

With that structure, he moved from self-directed learning to professional engineering. He landed a software engineering job at Unlocked Labs, building education solutions for incarcerated learners while continuing to contribute to open source. After about a year, he was leading their development team. From there, he found Turso’s Project Limbo—Turso’s effort to rewrite SQLite from scratch. Although he hadn’t worked deeply on relational databases before, he used his prior storage-engine interest (from cache work) to dive into the codebase, academic database internals, and Andy Pavlo’s CMU lectures. His early contributions were driven by the practical reality of prison time: programming consumed much of his life, with reports of around 90 hours a week spent on coding and infrastructure.

A key turning point came when Globber (Turso’s CTO) noticed his work. A Discord introduction led to a meeting, and Globber’s later public attention—reading his blog post on a stream—brought broader visibility. Over time, he began receiving messages from developers and students, including people trying to restart after addiction or similar circumstances, asking how to contribute to open source and build a learning path.

The narrative also argues for “luck plus hard work” as a workable model. Opportunity, he says, arrives unpredictably, but it tends to reward the person who has already been grinding in the same direction for a long time. He describes how remote career chances and hiring decisions became possible only after sustained preparation.

Finally, the account turns to policy and second chances. He praises “fair chance” hiring and suggests that prison systems can produce measurable rehabilitation signals—course completion, program participation, and reductions in sentence—information employers can use to evaluate candidates. He also notes that his return date has shifted due to court outcomes, but frames the remaining time as an opportunity to keep building skills. The broader message: incarceration can be a dead end, but with access, discipline, and organizations willing to look beyond a criminal record, it can also become a starting line.