Sabitlenmiş Tweet
minum susu milo pas pagi, 2 chocolatos pas siang, 2 bengbeng pas malem, repeat selama 3 hari, pas hari ke 4 minum suprot nya @BatmanSlipi bisa kenyang dari sahur sampe jam 3 aja
Catholic 𐕣@myshawti
Ayo cerita
Indonesia
yazid
1.6K posts
yazid retweetledi
As a Junior DevOps / SRE trying to move towards Mid-level, I'll tell you bluntly:
Knowing how to use Docker, Kubernetes, and CI/CD is not enough.
At Junior level, you're expected to follow existing docs and keep things running.
At Mid level, you're expected to understand why the system is built that way, choose the right tools, and reduce future operational pain.
If you can already deploy stuff and write basic pipelines but still feel stuck at Junior, spend the next 3–6 months building these Mid-level DevOps muscles.
Environment & Infra Foundations
↬ Linux basics (permissions, processes, networking)
↬ Shell scripting you're not scared to edit later
↬ Understanding VPCs, subnets, security groups
↬ Basic DNS, TLS, certificates
↬ SSH, bastion hosts, jump boxes
↬ Packaging apps: Docker images, image hygiene
↬ Container runtime basics (cgroups, namespaces)
↬ IaC fundamentals (Terraform/CloudFormation)
↬ Understanding cloud pricing basics
↬ Reading infra diagrams and drawing your own
↬ Knowing what is "state" and where it lives
↬ Secrets management basics (KMS, Vault, SSM)
CI/CD & Release Engineering
↬ Building reliable pipelines (GitHub Actions, GitLab CI, Argo, Jenkins)
↬ Build cache, artifacts, and image registries
↬ Branching strategies and release channels
↬ Rollbacks vs rollforwards
↬ Blue/green and canary basics
↬ Promotion across envs (dev/stage/prod)
↬ Test stages: unit, integration, e2e
↬ Handling flaky tests
↬ Environment parity and drift
↬ Deploying DB changes safely (migrations)
↬ Approval flows and change management
↬ Pipeline observability (logs, metrics)
Kubernetes & Orchestration
↬ Pods, Deployments, Services, Ingress
↬ Requests/limits and basic capacity planning
↬ ConfigMaps, Secrets, and env separation
↬ Liveness/readiness probes
↬ HPA basics (what metric, what threshold)
↬ Rolling updates and rollout strategies
↬ Debugging with logs, exec, port-forward
↬ Basic network policies
↬ When not to use Kubernetes
↬ Helm/Kustomize fundamentals
↬ Understanding cluster responsibility boundaries
Observability & Reliability
↬ Metrics, logs, traces: what each is for
↬ SLI/SLO basics, not just alerts
↬ Alert fatigue vs useful alerts
↬ Dashboards that answer "what broke?" quickly
↬ On-call handoff and escalation paths
↬ Incident communication in Slack/Zoom
↬ Writing and following runbooks
↬ Postmortem basics (timeline, impact, action items)
↬ Health checks and readiness checks
↬ Using tools: Prometheus/Grafana, Loki/ELK, Jaeger/Tempo
↬ Understanding dependency failure chains
Tooling & Automation Mindset
↬ Knowing your core stack well (AWS/Azure/GCP)
↬ Picking one main IaC tool and getting good at it
↬ Picking one main CI tool and mastering it
↬ Using CLIs efficiently (kubectl, aws, gcloud, az)
↬ Small scripts to remove repetitive work
↬ Writing reusable pipeline templates
↬ Standardising logging/metrics across services
↬ Adding safety rails: guardrails in pipelines, policies
↬ Keeping docs close to the code (READMEs, runbooks)
↬ Cleaning up unused infra and cruft
The Junior to Mid jump is not just "I can follow the docs and restart pods"
It is:
"I understand the system, the tools, and the tradeoffs well enough to make changes safely and reduce future ops pain for my team"
That is the mindset shift.
Puneet Patwari@system_monarch
As a Principal Backend Engineer with over 12 years of experience, I can tell you quite certainly that if you're still getting rejections in system design interviews after good efforts, I think your fundamentals are not strong... Dedicate 2-3 months to mastering these design fundamentals, then practice designing a few systems(and do plenty of mock interviews). Scaling & Architecture ↬ CDN ↬ Caching ↬ Sharding ↬ Queueing ↬ Replication ↬ Partitioning ↬ API Gateway ↬ Rate Limiting ↬ CAP Theorem ↬ Microservices ↬ Load Balancing ↬ Fault Tolerance ↬ Database Scaling ↬ Service Discovery ↬ Consistency Models ↬ Eventual Consistency ↬ Distributed Transactions ↬ Monolith vs Microservices ↬ Leader Election Databases & Storage ↬ Leader-Follower Replication ↬ WAL (Write Ahead Log) ↬ Asynchronous Processing ↬ Transaction Isolation ↬ Read/Write Patterns ↬ Consistent Hashing ↬ Redis/Memcached ↬ Backup & Restore ↬ Hot/Cold Storage ↬ Data Partitioning ↬ Object Storage ↬ SQL vs NoSQL ↬ Data Retention ↬ Data Modeling ↬ OLAP vs OLTP ↬ ACID & BASE ↬ Bloom Filters ↬ File Systems ↬ S3 Basics ↬ B+ Trees ↬ Indexing Communication & APIs ↬ JWT ↬ CORS ↬ OAuth ↬ Throttling ↬ Serialization ↬ API Security ↬ Long Polling ↬ WebSockets ↬ API Gateway ↬ Idempotency ↬ Service Mesh ↬ Retry Patterns ↬ REST vs gRPC ↬ API Versioning ↬ Circuit Breaker ↬ API Rate Limits ↬ Fan-out/Fan-in ↬ Protocol Buffers ↬ Message Queues ↬ Dead Letter Queue Reliability & Observability ↬ Metrics ↬ Alerting ↬ Failover ↬ Logging ↬ Rollbacks ↬ Monitoring ↬ Heartbeats ↬ Retry Logic ↬ Autoscaling ↬ SLO/SLI/SLA ↬ Load Testing ↬ Error Budgets ↬ Health Checks ↬ Circuit Breaker ↬ Incident Response ↬ Chaos Engineering ↬ Distributed Tracing ↬ Canary Deployments ↬ Graceful Degradation ↬ Blue-Green Deployment
English
yazid retweetledi
@unknownfhaal BARU AKU TINGGAL PRAKTIKUM UDA DI KATAIN LAGI TU TUMBLER
Indonesia
yazid retweetledi
local AI katanya lebih aman
karena datanya ga kemana-mana
tinggal di laptop sendiri
ternyata tidak selalu 👀
"Bleeding Llama" — CVE-2026-7482, CVSS 9.1
celah kritis di Ollama yang bisa bocorkan semua yang lo pikir aman
thread buat yang pake Ollama, Claude Code, atau coding agent 👇
The Hacker News@TheHackersNews
🚨 CVE-2026-7482 in Ollama could let remote attackers leak process memory from more than 300,000 exposed servers using crafted GGUF files. Separate unpatched Windows flaws enable persistent code execution through Ollama’s update mechanism. Full details and mitigations: thehackernews.com/2026/05/ollama…
Indonesia
