██████ ██ ██ ██████ ██████ ██████ ██ ██ ██████ ██████ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████ ██ ██ ██
██████ ██ ██ ██████ █████ ██ █████ ██ ██ ██ ██████ █████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████ ██ ██ ██ ██
██ ██ ██████ ██████ ██████ ██████ ██ ██ ██████ ██ ██ ██████
Rubén Martínez Agramunt
🔹 Backend Engineer 🔹 Security-Minded 🔹 Built From Scratch
Tip
Started in a bedroom — Linux installs, broken configs, shell scripts nobody asked for. That obsession with how things actually work never left. It evolved into something disciplined.
focus = [
"backend architecture", # not just REST endpoints
"secure system design", # threat models, not afterthoughts
"infrastructure fundamentals", # what runs beneath the code
"understanding systems under the hood",
]
# No cargo-culting. No copy-paste engineering. No magic I can't explain.$ cat active_learning.txt
┌──────────────────────────────────────────────────────────────────────┐
│ 🧱 Secure REST API Design │
│ Structure, auth patterns, error boundaries │
│ — built right, not bolted on │
├──────────────────────────────────────────────────────────────────────┤
│ 🔐 Security-First Backend Patterns │
│ From the ground up, not retrofitted │
├──────────────────────────────────────────────────────────────────────┤
│ 🐳 Docker & Containerization │
│ Reproducibility by default │
│ — if it doesn't run in a container, it doesn't ship │
├──────────────────────────────────────────────────────────────────────┤
│ 📖 OWASP Top 10 & Real Attack Surfaces │
│ Reading the threat landscape, not the marketing deck │
├──────────────────────────────────────────────────────────────────────┤
│ 🧪 Testable, Readable, Lasting Code │
│ Written for the engineer who inherits it at 2am │
└──────────────────────────────────────────────────────────────────────┘
{
"core_backend": {
"primary_languages": [
"Python",
"JavaScript",
"TypeScript"
],
"secondary_languages": [
"Java",
"C#"
],
"systems_languages": [
"C",
"Rust",
"Go"
],
"scripting": [
"Bash"
],
"frameworks": [
"Django"
],
"data": [
"PostgreSQL"
],
"api_architecture": [
"REST"
],
"architecture": [
"API Design",
"Async Systems",
"Authentication & Authorization"
]
},
"systems_and_networking": {
"fundamentals": [
"HTTP",
"TCP/IP",
"Sockets",
"Concurrency"
]
},
"infrastructure": {
"tools": [
"Docker",
"Git",
"Linux"
],
"principles": [
"Containerized Development",
"Reproducible Environments"
]
},
"security_mindset": {
"focus": [
"Threat Modeling",
"OWASP Top 10",
"Secure System Design",
"Attack Surface Awareness"
]
},
"enterprise_experience": {
"platforms": [
"Microsoft Dynamics 365"
],
"automation": [
"Power Fx",
"Business Process Automation",
"CRM Solutions"
]
} ┌─────────────────────────────────────────────────────────────┐
│ 01 // Understand before you use │
│ If you can't explain why a tool exists, │
│ you don't own the decision to use it. │
├─────────────────────────────────────────────────────────────┤
│ 02 // Security is architecture, not a feature │
│ Threat modeling before line one. │
│ Not a checklist at the end. │
├─────────────────────────────────────────────────────────────┤
│ 03 // Boring is a compliment │
│ Elegant systems are invisible. │
│ The best code is the one nobody has to touch. │
├─────────────────────────────────────────────────────────────┤
│ 04 // Own the whole stack │
│ From TCP handshake to HTTP response. │
│ No layer is someone else's problem. │
└─────────────────────────────────────────────────────────────┘
← still reading? you might be my kind of engineer →