[kubernetes][helm][argocd][fluxcd][prometheus][grafana][opentelemetry][jaeger][tempo][loki][envoy][istio][linkerd][cert-manager][external-dns][karpenter][crossplane][backstage.io][terraform][pulumi][vault][etcd][kyverno][opa][tekton][spinnaker][cilium][falco][kustomize][velero][fluentd][thanos][cortex][keda][knative][contour][traefik][rook][ceph][minio][redis][postgresql][kafka][rabbitmq][elasticsearch][opensearch][mongodb][cockroachdb][neo4j][clickhouse]
tty/0 · gdantas.io ·
·
gd@platform:~$

/ platform engineer
6+ years building developer platforms. I'm part of QuintoAndar Group's Platform Engineering team, focused on our IDP (Backstage.io) and building tooling that improves developer experience and productivity.
"So others may live." — U.S. Coast Guard Rescue Swimmer
UPTIME
STATUS
Platform Engineer · DevEx & Productivity
BASE
São Paulo, BR
gd@platform:~$ _
01

kubectl get topology

// the platform as a graph
CLUSTER · sa-east-1
● synced
$ kubectl get pods --watch · 112 pods · 4 namespacesp95 latency 38ms
02

cat ~/.stack

// what's running right now
orchestration
Kubernetes
cloud
AWS
iac
Terraform · OpenTofu
gitops
ArgoCD · Atlantis
portal
Backstage.io
languages
Go · Python · TS
ai
Cursor SDK · Claude Code API · LangGraph · MCPs
observability
LGTM Stack · Prometheus · Thanos · OTel
data
Vector DBs · Postgres
03

cat ~/.doctrine

// "So Others May Live"
MANIFESTO.md

Platform engineering is backstage work. Usually, the less we're noticed and the more productive teams are, the better we're doing.

The first platform team I worked with had this motto: "So Others May Live" — we do the complex stuff so others don't have to, we go where others wouldn't, to do what they wouldn't — without anyone noticing we exist.

That's exactly what platform is — and it ties straight back to DevOps culture. At the end of the day, what I love most is helping other engineers solve problems :)

TL;DR: if we can make the best path the easiest path, with the best tools, for everyone — our platform mission is accomplished.

— gdlast edited: today
ROLE 01DevOps
DevOps to me is culture, not tooling or a job title. It's a daily habit: shortening the feedback loop between who builds and who runs, until both sides stop existing as sides. When dev and ops share the same pager, the code comes out different.
ROLE 02SRE
SRE is the engineer who treats operations as software: SLO before code, toil measured in hours, incident turning into postmortem and postmortem into real change. On-call is an excellent way to learn how systems actually work, find improvement opportunities and observability gaps.
ROLE 03Platform Engineer
That's when all of this turns into product: self-service, paved roads, abstractions that protect the dev without locking them in. Favorite metric: time others gained without noticing. The more invisible, the better.
04

ls ~/talks

// recent · slides + video
gd@platform:~/talks$ ls --all ↗ all talks
05

ping --help

// think I could help you crack a problem?
CHALLENGES.txt

Platform is teamwork. If you want to swap notes, bring a talk to your team, or you've got a project that needs an extra brain — the inbox is open.

$ ping gd ↗

gd@platform:~$ echo $SIGN
gd
Osasco / São Paulo · BR