Stack Personality Quiz

What does your stack say about you?

Eight questions. One archetype. No signup.

1. How do you pick a database?

Postgres unless there is a very good reason not toWhatever has a serverless option and a generous free tierWhatever is trending on the last three conference keynotesSQLite in production until the post-mortem says otherwise

2. A $50 surprise cloud bill lands in your inbox. You…

Open the billing console, sigh, and start disabling things you forgot existedCalculate how many months of a Hetzner box that would have boughtForward it to finance — that is what budgets are forBlame egress, add a CDN, and call it architecture

3. It is launch day. What are you actually doing?

Running the deploy script and refreshing the pageFollowing a runbook with one eye on the pager and one on the dashboardDrafting a launch thread about your "cloud-native, event-driven platform"Verifying latency from twelve global PoPs before anyone clicks

4. How many providers are in your current stack?

One. It is a VPS. There is also maybe Cloudflare DNS.One cloud, but twelve services inside itBest-of-breed: each tool from whoever does it best, invoice be damnedOne platform I trust, three services I understand

5. Describe your dream infrastructure setup.

Bare metal in a datacenter I can drive to, full root access, no surprisesZero ops: everything managed, autoscaling, and someone else's problemCompute in 300 cities, data close to users, config as the only deploy artifactA monolith on a PaaS, managed Postgres, and a good night's sleep

6. How do you handle scaling worries?

Add Kubernetes now so you are ready when you hit 10 usersWait until the metrics say so, then vertical scale firstAutoscaling everything — if it scales to zero, it scales to heroOpen a priority support ticket and let the vendor figure it out

7. What does "DevOps" mean to you?

There is no DevOps team. There is you, SSH, and a systemd unit file.YAML, pipelines, and a culture of blaming the last person who mergedA platform team with an internal developer portal and golden pathsNo servers to ops — just functions, bindings, and deploy hooks

8. A hot new JavaScript framework drops. Your reaction?

Start a rewrite immediately — first movers get the GitHub starsIgnore it and ship the feature users asked for three sprints agoCheck if it runs on Workers at the edge before reading the docsBookmark it, wait for v2, stick with what works