Backend Python • Linux-first • Docker • APIs • PostgreSQL
╭──────────────────────────────────────────────────────────────────────────╮
│ mirco@linux ~ $ whoami │
│ marcos_vinicius_thibes_kemer │
│ │
│ mirco@linux ~ $ uname -a │
│ Linux • Ubuntu • Bash • Containers • Automation │
│ │
│ mirco@linux ~ $ echo "$PHILOSOPHY" │
│ Build systems that are predictable, scriptable and observable │
╰──────────────────────────────────────────────────────────────────────────╯
Backend development with a Linux mindset — terminal-driven, reproducible and pragmatic.
mirco@linux:~$ cat linux.md
- Terminal-driven workflow (bash, cli tooling, automation)
- Reproducible dev environments (Docker, .env, scripts, Make targets)
- Strong fundamentals (filesystems, permissions, processes, networking)
- Productivity stack: Ubuntu + Neovim + Git
Why Linux matters in my work
- ⚙️ I design tooling and automation like a sysadmin would: predictable, scriptable, repeatable
- 🧠 I focus on fundamentals: processes, logs, permissions, networking, services
- 🐳 I ship environments, not “it works on my machine”: containers + configuration + docs
mirco@linux:~$ backend --capabilities
- REST APIs and service-oriented design
- Data modeling with SQL (PostgreSQL / SQLite)
- Background jobs, schedulers and automation scripts
- Containerized environments (Docker, Compose)
- Logging-first mindset and operational awareness
I care not only if the code works, but how it runs, how it fails, and how it can be debugged
mirco@linux:~$ man development_style
- Clarity over cleverness
- Simple architectures before abstractions
- Automation instead of repetition
- Readable code for future maintainers
- Small tools that do one thing well
Inspired by the Unix philosophy and real-world constraints.
mirco@linux:~$ echo "fun_fact"
Great software comes from a mix of logic, curiosity and coffee