██╗ ██╗██╗██╗ ██╗ ███████╗██╗ ██╗
██║ ██╔╝██║██║ ██║ ╚════██║██║ ██║
█████╔╝ ██║██║ ██║ ██╔╝███████║
██╔═██╗ ██║██║ ██║ ██╔╝ ╚════██║
██║ ██╗██║███████╗███████╗ ██║ ██║
╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝
┌─[guilherme@kill74]─[~]
└──╼ $ cat /etc/profile.d/me.conf
handle → kill74
name → Guilherme
location → Castelo Branco, Portugal 🇵🇹
age → 20
education → Lic. Design Digital e Multimédia
Instituto Politécnico de Castelo Branco
prior → TeSP Desenvolvimento Web e Multimédia [grade: 15 ✓]
stack → C · Assembly · Rust · Go · C# · JS/TS · Python · PHP · Lua · SQLite · Oracle · MongoDB
layers → bare-metal kernels → systems daemons → REST APIs → UIs
philosophy → understand the whole stack, own every layer
status → [ BUILDING ] — always.Most developers live at one end of the stack. I build kernels and ship products — because you can't truly master one without understanding the other.
Production systems, open-source tools, and systems experiments. All shipped.
|
Production-grade event ingestion bridge — Slack, Teams, GitHub, GitLab → one hardened pipeline. Built in Go with HMAC/token webhook verification for 4 providers, OpenTelemetry tracing, structured What this proves: I design for production from the first commit — security, observability, and reliability are not afterthoughts.
|
💬 ChatifyTerminal-first, self-hosted chat server — engineered for correctness in Rust. WebSocket server with SQLite-backed event persistence, multi-channel messaging, DMs, voice, file transfers, reactions, history replay, and time-window search. Optional Discord bridge behind a Cargo feature flag. Ships as cross-platform binaries with automated Windows release packaging and SHA256 checksums via GitHub Actions CI. What this proves: Systems thinking applied to networked, concurrent, production-ready software.
|
|
Full-stack data engineering platform — from raw events to business insight. Built on .NET 8 + PostgreSQL with a clean ETL pipeline modelling real-world e-commerce analytics. Handles ingestion, transformation, and BI-ready output. Designed around the principle that bad data architecture costs more than bad code. What this proves: I design systems end-to-end, not just endpoints.
|
🔗 SPO2SQLEnterprise integration bridge — SharePoint Online → SQL Server. Console tool that syncs SharePoint lists to SQL Server via CSOM, applying data quality routines to catch structural inconsistencies before they corrupt downstream reports. The kind of unglamorous, critical infrastructure that keeps businesses running. What this proves: I build tools that survive contact with production.
|
{
"languages": {
"systems": ["C", "Assembly (x86)", "Rust", "Go"],
"backend": ["C#", "Python", "PHP", "Node.js"],
"frontend": ["JavaScript", "TypeScript"],
"scripting": ["Bash", "Lua"]
},
"frameworks": {
"web": ["React", "Next.js", ".NET 8"],
"data": ["ETL pipelines", "PostgreSQL", "MySQL", "Oracle", "SQL Server"]
},
"systems_knowledge": [
"x86 protected mode", "memory management",
"CPU protection rings", "async runtimes",
"network protocols", "CSOM / SharePoint APIs"
],
"toolchain": ["Linux", "Git", "Vim", "GDB", "Bash", "Docker", "Terraform", "npm", "OpenCV"],
"currently_exploring": ["eBPF", "WASM runtimes", "distributed consensus", "GitOps (ArgoCD / Flux)"]
}[ ACTIVE ] Studying distributed systems & consensus algorithms
[ ACTIVE ] Deepening OS internals — scheduler design, memory models
[ QUEUED ] eBPF-based observability tooling (Rust)
[ QUEUED ] Contributing to open-source systems projects
[ ALWAYS ] Reading. Building. Iterating.
Open to internships, collaborative projects, and interesting problems. If you're building something that requires understanding the full stack — let's talk.
┌─[guilherme@kill74]─[~]
└──╼ $ sudo shutdown -h now
Syncing filesystems...
Saving state...
[ always building → never stopping ]
Connection to kill74 closed.// The present is connected to the past and future. — Lain