Case file  ·  001 Updated 2026-11-15

My only machine died. I need a working one to keep shipping.

My only machine died in November 2026. I ship everything from a phone, and that ceiling is now the bottleneck on four active repos.

Open — hardware requested

01 What broke

Machine
Dell Latitude E5440
Built
2014
Status
Dead — board failure
Detail
4th-gen Core i5, DDR3, spinning disk. Motherboard is gone. Nothing recoverable.

Not a damaged keyboard or a dead cell. The machine itself is gone, and it was already a decade past the point where a current toolchain would run on it comfortably.

02 What I do with a machine

I am 16. Solo maintainer: I write Linux-on-Android tooling, Rust clients, ESP32 firmware and Python packaging. Everything is public, and every release is built by CI I wrote. 30 public repositories of my own, all readable, none of them private. The six below are the ones a machine actually unblocks.

How this is being built right now

Nothing above was built on a laptop. The desktop comes from Linux-For-Android, a full Linux environment running on Android with no root. When something needs a real GUI session, it runs inside a GitHub Actions runner provisioned by Free-Github-Actions-RDP. Both are my own projects, so the workaround is part of the portfolio rather than an excuse.

Figures pulled from the public GitHub API on 2026-11-15. Verify them independently: https://github.com/pdev-labs

03 What would actually fix it

Minimum

  • x86-64, 4 cores or better
  • 16 GB RAM (8 GB is workable, 16 GB removes the ceiling)
  • NVMe SSD, 256 GB or larger
  • Runs Linux with no out-of-tree driver fights

Helpful

  • 32 GB RAM (local Android emulator + Rust release builds at the same time)
  • USB-C with DisplayPort alt mode
  • User-replaceable battery and SSD

Not asking for the newest or the fastest. Refurbished, previous-generation, or review-unit hardware all do the job.

04 What I give back

  1. Named credit in the repositories. Whoever provides the machine is credited by name in the README of every repository it unblocks, and at the top of the build log. Not a temporary banner that quietly disappears — it stays there.
  2. A public build log. What shipped each week, what broke, and how long each build took — on the actual hardware.
  3. A written Linux compatibility report. What worked out of the box, what needed a quirk, and what I would tell the next person who buys it. Published in full, with attribution, and nobody gets to edit it first.
  4. Upstream fixes. Every driver quirk, packaging bug and kernel problem I hit turns into a patch or a bug report rather than a tweet.
  5. It stays in circulation. If the machine is replaced later, it goes to another maintainer, not into a drawer.

05 How to reach me

This page is the entire ask. It is not a mailing list and there is no form behind it. If someone sent you this link, it was one message, sent once, to one address.