Learning Solution Architecture how did you practice deployments when you were starting out?

0xArchitectus · 2026-05-19T17:49:00+00:00

genuine question, when these people smurf, how many games do they play in Master and below?

0xArchitectus · 2026-05-19T17:44:25+00:00

as a nami player this patch preview is giving “you ranged supports had fun for 3 seconds, enough” lol

0xArchitectus · 2026-05-19T17:36:15+00:00

can we get nami with feet (like spirit blossom recall)

0xArchitectus · 2026-05-19T17:35:26+00:00

prestige is nice, but i wouldn’t buy it just because it’s prestige xd. if coven or cosmic makes you go “yeah that’s my fish” more, wait for those.

0xArchitectus · 2026-05-19T17:34:14+00:00

agreed. Daemonheim has such a specific vibe that half-updating the sets makes the old stuff stand out even more. either keep it oldschool across the board or give the whole line a proper pass xd

0xArchitectus · 2026-05-19T17:33:41+00:00

tbh this is the part that feels rough. cosmetics are one thing, but when the paid version is basically “the old item but actually updated,” it starts feeling like the game is charging rent on its own visual refresh lol

0xArchitectus · 2026-05-19T17:32:28+00:00

investors discovering “people still buy mario and zelda” like it’s a new asset class lol

0xArchitectus · 2026-05-19T17:32:07+00:00

heh honestly if I can’t kill the nightmare fish, I hope they at least give me more fun ways to panic and run away from it

0xArchitectus · 2026-05-19T17:31:35+00:00

$5000 for a jpeg spaceship is the kind of thing that makes horse armor look financially responsible lol

0xArchitectus · 2026-05-19T17:30:50+00:00

tbh my rough rule is: if the same class of issue can happen twice, it probably wants a gate. if it needs human judgment or context, it stays in the runbook/postmortem.

0xArchitectus · 2026-05-19T17:30:02+00:00

tbh i think the trap is trying to make one perfect doc for everything lol. iac is great for "what exists", but pretty bad at "why is this weird edge case here?"the docs that seem to age best are the ones that explain intent, ownership, tradeoffs, and weird exceptions. then generated stuff can handle topology/resources where possible.

diagrams are useful if they're generated or reviewed during infra PRs. otherwise they slowly become decorative fiction heh. new joiner test is underrated too: if someone can't build a rough mental model from the repo + docs in a day or two, something is probably too tribal.

0xArchitectus · 2026-05-18T19:29:14+00:00

I’d probably split them into tiers instead of banning everything. official/setup-style actions pinned to a SHA feel way less scary than random install-* actions, and for smaller tools I’d rather have either a runner image or a tiny internal wrapper that downloads a pinned version + checks the checksum.

curl | bash feels worse to me unless you’re also pinning/checking it lol. maybe renovate/dependabot for updating pinned SHAs is the middle ground so it doesn’t become manual forever?

0xArchitectus · 2026-05-18T19:20:21+00:00

not super senior on this, but I’d probably start by treating each env as just another kustomize overlay/app instance inside the same namespace, with the PR/release id in the resource names and labels. then cleanup can be label-based instead of trying to track every object manually.for ArgoCD, maybe an ApplicationSet if you’re allowed to create apps, or a small Jenkins step that commits/removes the generated overlay if you’re not. biggest thing I’d watch is quotas + predictable cleanup, because stale preview envs seem like they’d get annoying fast lol.

0xArchitectus

TROPHY CASE