Warning
If you came here for the Coding Ranch™ — it has been permanently decommissioned. The unicorns were gracefully drained, the rainbow GIFs rolled back, and all horse-related assets migrated to their rightful owner. This is a horse-free zone now.1
I'm Nico — a full-stack developer who spends the day hopping between backend services, frontend code, and whatever system decided to catch fire that morning. Strong opinions about clean code, weakly held opinions about tabs vs. spaces (I let the formatter fight that war for me).
Tip
Robots should do the boring stuff. If I do something manually twice, the third time is a script.
This diagram renders live from the source — GitHub speaks Mermaid natively:
flowchart LR
A([☕ Coffee]) --> B{Build passing?}
B -- yes --> C[🚀 Ship it]
B -- no --> D[Blame the cache]
D --> E[Clear the cache]
E --> F{Fixed?}
F -- somehow, yes --> C
F -- no --> G[It was DNS]
G --> B
C --> H[[Code review by @TO-KOswald]]
H -- approved ✅ --> I([Merge & pretend it was easy])
H -- "nit: rename this variable" --> B
Still riding shotgun on every pull request: @TO-KOswald —
partner-in-pull-requests, first responder for git push --force incidents, and the
reason half my variable names are actually readable.
These cards switch with your GitHub theme — dark mode gets dark cards, light mode gets light ones. Toggle your theme and watch them flip.
A snake eating my contribution graph, regenerated nightly by a GitHub Action:
⚙️ Automation — because time bookings won't book themselves
Building small tools that remove repetitive work from my day. Current rule of thumb: if a task survives two manual repetitions, it gets automated on the third.
🧠 Patterns & architecture — design patterns, event-driven everything
Digging deeper into design patterns and event-driven architectures. async/await
is easy; knowing when an event bus turns your system into a haunted house is the hard part.
🕵️ Easter egg — you actually clicked it
[!IMPORTANT] You are the kind of person who expands collapsed sections. We need more of you in code reviews. Ctrl+Shift+Respect
Footnotes
-
No horses were harmed during the refactoring of this README. One unicorn filed a complaint with HR; it was closed as
wontfix. ↩