If I do it twice, it becomes code. If it reaches production, it passes a security gate first.
| ⚙️ Automation paved roads instead of tickets: one template, every service |
🏗️ Infrastructure as Code versioned, reviewed and rebuilt on demand |
☁️ Multi-cloud AWS · Azure · GCP · OCI, same principles everywhere |
| 🔐 DevSecOps security gates in every pipeline, secrets never in code |
📈 Site Reliability SLOs, error budgets, observability and chaos on purpose |
🛡️ Cloud Security least privilege, Zero Trust, posture as code |
| 🗡️ Offensive Security thinking like the attacker to build the defense |
🔎 Digital Forensics evidence, integrity and chain of custody |
🧠 Local AI models and agents running on my own hardware |
| Cloud |
|
| Infrastructure as Code |
|
| Containers |
|
| CI/CD |
|
| Security |
|
| Observability |
|
| Code |
|
| AI |
|
+ Automate the second time, document the first
+ Security is part of the pipeline, not a phase after it
+ Fix the root cause, then make sure it can't come back
+ Least privilege by default, exceptions by evidence
- "It works on my machine"
status: Running · Let's play ✨