systems engineer • tower climber • eepy infrastructure pup
status: online 🟢
mood: a little sleepy, still deploying anyway
location: rooftop → datacenter → VR → repeatHeyo, i’m Mira!
I build systems that survive bad conditions, weird configs, and my own experiments
I came from electromagnetic spectrum + comms stuff so now everything I touch ends up being:
- resilient
- slightly overengineered
- and very hard to kill
also I will absolutely break something just to understand it better
things_i_touch:
- backend systems (C#, APIs, auth)
- networks (vlans, routing, "why is this tagged twice")
- reverse proxies + ingress
- self-hosted everything
approach:
- make it work
- make it stable
- make it recoverable
- then make it pretty (optional)region: ATL
name: DSONET
state:
- running: yes
- stable: mostly
- documented: …sometimes
features:
- tiny cloud that thinks it's bigger than it is
- services talking to each other (usually)
- random ports open that i definitely remember (I don't)- making services behave behind proxies
- low latency anything (especially for VR)
- building systems that don’t panic when links get weird
- convincing things to work over networks they absolutely shouldn’t
- living inside VRChat
- tweaking my avi instead of being productive
- climbing towers and immediately regretting it halfway up
- laying in bed like “I should automate that” and then not moving
version: mira v_current
traits:
+ curious to a fault
+ will fix it eventually
+ soft but stubborn
+ thrives in controlled chaos
known_issues:
- turns small ideas into full infrastructure
- refuses to leave things "good enough"if it only works when everything is perfect → it's not done
if it breaks and i can't see why → i failed
if it comes back on its own → now we're talkingMatrix: @mira:sentinelsec.studio
Discord: itsmira02Just me, my projects, and whatever i'm hyperfixated on this week!