Full-Stack Developer
I build software, APIs, automation systems, and developer tools.
Most of the work is in Node.js, TypeScript, and JavaScript — APIs and backend services, browser automation, developer tooling, and technical research. Go, React, and Next.js when the system needs them.
Index
Backend services, browser automation, developer tools, and systems work \u2014 the kind of software I actually build.
A Node.js API for routing, authentication, and JSON request handling. Small surface area: Express, straightforward middleware, and a local database instead of a heavy framework stack.
Node.js · Express · REST · SQLite
A Puppeteer-based runner for repeatable browser tasks: session handling, request automation, and data extraction. Built for workflows that are too brittle for a one-off script.
Node.js · Puppeteer · HTTP · Automation
A command-line tool for a repetitive technical workflow — wrapping API calls, local files, and automation steps behind a short set of commands.
Node.js · CLI · API · Automation
A Go HTTP service for storing and serving media payloads. JSON over HTTP, FFmpeg for media processing, and encrypted storage on disk. Built as infrastructure, not a product UI.
Go · HTTP · JSON · FFmpeg
Scripts and helpers around ADB, Fastboot, and local Android environments. Device bring-up, debugging, emulator/VM setup, and the boring parts of keeping a device lab usable.
ADB · Fastboot · Android · Linux
Research notes and tooling around application behavior: HTTP traffic inspection, Android app analysis, and instrumentation experiments. Technical research — not a security product and not client work.
Burp Suite · Frida · HTTP · Android
A small prototype for testing an idea end-to-end before committing to a larger build. Intentionally narrow: one path, one interface, enough to see whether the approach holds.
TypeScript · Node.js · HTTP
Practice
The work I keep coming back to. Not a service menu \u2014 just the layers I actually spend time in: backend, APIs, automation, systems, and technical research.
APIs, services, request handling, authentication, data processing, and backend architecture.
Browser automation, workflow automation, request automation, and developer tooling.
Linux, VPS environments, Android tooling, device debugging, and infrastructure.
Application analysis, HTTP traffic analysis, reverse engineering, and technical experimentation.
Note
I'm SirGate (SirgateDev on GitHub), a full-stack developer who likes building things end-to-end. Most of my work revolves around Node.js, TypeScript, and JavaScript — APIs, automation, backend systems, and developer tools.
I would rather understand how a request moves through a stack than treat a framework as a black box — from the client, through auth and routing, into storage, and back. The interesting part is usually the system, not the template. Go when the service calls for it; React and Next.js when a frontend is part of the same system.
Outside of product UI I spend time on browser automation, Android device tooling, Linux environments, and technical research: application analysis, traffic inspection, and reverse-engineering experiments. Same instinct in each case: figure out how something works, then build around it.
If you have a project, an idea, or just want to talk, get in touch.
Path
Broad stages, not a resume. Dates are omitted because they are not the point.
Started building software and experimenting with web technologies — HTML, CSS, JavaScript, and the first Node.js scripts that actually did something useful.
Moved deeper into Node.js, APIs, HTTP, and server-side systems. Most of the work became request handling, data, and services rather than pages.
Started building automation systems and developer tools — browser workflows, request pipelines, and CLIs for tasks that did not deserve to stay manual.
Explored Android tooling, Linux, VPS environments, and device debugging. More time on the machine, the process, and the network around the code.
Began exploring application behavior, traffic analysis, and reverse-engineering experiments. The same instinct: understand the system, then build against what is actually there.
Stack
Grouped by how I actually use them. Backend and tooling sit above frontend libraries on purpose.
Contact
Have a project, idea, or just want to talk?