Software that keeps working when the internet doesn't.

I'm lordofsunshine. I build developer tools, browser editors and Windows utilities. Most of them run on your machine and keep your work there.

Selected work Talk to me
Based in
Remote
On GitHub since
2021
Public repositories
53
Open to
Freelance & collaboration
Scroll to work

01 / Selected work

Five projects that show how I work. The rest are on GitHub.

01 sunConstructor A visual website builder that runs in the browser. Projects sit in IndexedDB and leave as a static ZIP, so there is no account and no copy on a server. React · TypeScript · Zustand · IndexedDB 02 MonoForge Project pages, README rendering, file uploads and discussions for people who publish code. Next.js on the front, Prisma and Docker behind it. Next.js · TypeScript · Prisma · Docker 03 Code Editor with Console Monaco in the browser with shared editing sessions, project chat, live preview and server-side execution. Fastify and Socket.IO hold the real-time side together. JavaScript · Monaco · Fastify · Socket.IO 04 sun-trace Records what an installer changes on a Windows machine: files, services, startup entries. The log makes updates and removals easier to reverse. C# · .NET · Windows · SQLite 05 sunCleaner 158 cleanup, privacy and repair tasks in a PowerShell TUI. Risky actions stay visible, with WhatIf, restore points and undo within reach. PowerShell · Windows · TUI

53 public repositories, from Discord bots to encrypted pastebins.

Browse the GitHub profile

02 / Approach

I care about what happens after the first successful run.

01

It should open without an account.

If a piece of software can work on one computer, I try to let it. Local files, local storage, and an export button that actually exports something useful.

02

The boring parts are the product.

Empty states, error messages, backups and a way to undo. A feature is not finished when the happy path works.

03

The screen should explain itself.

Labels in plain language, spacing that shows what belongs together, and a layout that survives 360px.

04

Choose the stack after the problem.

React when the interface needs it. PowerShell when the job is Windows. A static file when nothing else is required.

03 / Stack

Tools I reach for most. The list changes with the project.

Frontend

  • TypeScript
  • JavaScript
  • React
  • Next.js
  • Vite
  • Tailwind CSS
  • HTML / CSS

Backend

  • Node.js
  • Fastify
  • Express
  • Python
  • FastAPI
  • Socket.IO

Data & infrastructure

  • PostgreSQL
  • MongoDB
  • Prisma
  • Docker
  • Vercel
  • Git

Desktop & scripts

  • C# / .NET
  • PowerShell
  • Python
  • Windows APIs
  • IndexedDB

04 / About

A developer who still likes the visual side of the job.

I started with front-end layouts and followed the work into APIs, authentication, databases and deployment. Most of what I build now is full-stack, though I still spend a lot of time on type, spacing and how a page behaves at 360px.

My projects usually begin as a fix for something that annoyed me: an installer that leaves no trace, a builder that wants an account before it will save a rectangle. I keep them going past the demo stage because a second version teaches more than a folder of unfinished prototypes.

Away from the editor I read documentation for fun, collect small utilities and keep a list of interfaces I like. The motto on my profile is not a joke. Everything will be alright.

Currently

Building sun-trace, tightening sunConstructor's export, and improving how my projects handle errors, tests and deployment.

Elsewhere

GitHub
Telegram

Tell me what you're building.

Bug reports, project ideas, or a collaboration that needs a full-stack developer. Telegram is fastest.

Telegram @bobiku228 GitHub @lordofsunshine