DIGITAL IDENTITY

DIGITAL IDENTITY — FILE 001

COBALT

@localrccHe / HimCroatiaConnecting…

Backends, bots, tooling and the infrastructure they run on. Mostly self-taught, built by breaking things first.

SCROLL
01

Identity

LIVE · DISCORD GATEWAY
02

About

PERSONAL FILE

I'm Cobalt — a 20 year old hobbyist developer who spends most of his time building and maintaining software that has to keep running when nobody is watching.

Usually that means backends, bots, small tools and the infrastructure underneath them. I like working across the whole stack: servers, networking and DNS, reverse proxies, and the interface people actually end up touching.

Almost all of it is self-taught. I learned by building things, breaking them, and figuring out how to put them back together — which is still, by some distance, the fastest way I know to understand a system.

03

Arsenal

BEST → STILL LEARNING
04

Domains

WHAT I WORK WITH
01

Networking

Routing, ports, firewalls and VPNs — plus working out why one machine refuses to see another.

02

Backend

APIs, databases, bots and services that are expected to stay online without supervision.

03

Frontend

Interfaces that load fast and stay out of the way. Motion only where it earns its place.

04

Domains & DNS

Domain setups, records, SSL, reverse proxies and the mail configuration nobody enjoys.

05

Self-Hosted Servers

Built and run my own servers for games that never shipped with support for it.

06

Hardware

Builds, upgrades, troubleshooting, and assembling servers from loose parts upward.

07

Systems

Windows and Linux, deployment pipelines and the monitoring that tells you it broke.

08

Reverse Engineering

Non-professional

Taking software apart purely to understand how somebody else decided it should work.

05

Record

2016 — PRESENT
  1. 2016ENTRY
    Roblox Studio

    First line of Lua

    Opened a game engine to change one number and stayed for the scripting. Everything after this is downstream of that afternoon.

    • Lua
    • Roblox Studio
  2. 2018SCRIPT
    Outside the engine

    Picked up Python

    The first language that wasn't tied to somebody else's game. Scripts that ran on my own machine and did whatever I told them to.

    • Python
    • Automation
  3. 2019NETWORK
    requests

    Found out how the web actually talks

    HTTP methods, headers, status codes, auth. Once requests clicked, every service on the internet turned into something I could script against.

    • HTTP
    • APIs
    • requests
  4. 2020WEB
    Node.js

    Started building the web, not just calling it

    Moved from consuming APIs to serving them. Node backends first, then the frontend on top — which is where the interface side of this finally started to matter.

    • Node.js
    • Frontend
    • JavaScript
  5. 2022TEARDOWN
    Non-professional

    Took things apart to see inside

    A stretch of reverse engineering, purely out of curiosity. Never professionally — but nothing taught me more about how software is actually put together.

    • Reverse engineering
    • Protocols
  6. 2023BACKEND
    C# / .NET

    Backends in C#

    Swapped scripting habits for a typed language and a real compiler. Services built to stay up on their own rather than to run once and exit.

    • C#
    • .NET
    • Services
  7. 2024TOOLING
    Console → interface

    From console tools to real tools

    Started with command-line utilities for my own problems, then gave them interfaces, installers and error handling — the unglamorous part that makes something usable by someone else.

    • CLI
    • Desktop
    • UX
  8. 2026NOW
    Currently

    Elixir and Rust

    Two languages that disagree with my habits on purpose — one about concurrency and failure, the other about ownership. Both are still very much in progress.

    • Elixir
    • Rust
    • Ongoing