The Senior Architect's Universal Answer
Description
A black and white meme featuring a photograph of an elderly, seemingly wise man with white hair, sitting back in a chair and smoking a pipe. He has a pensive and experienced look. The top text, in a bold white font, reads 'ME ANSWERING EVERY SINGLE ARCHITECTURE QUESTION:'. The bottom text, in a larger, more definitive font, simply says 'DEPENDS.'. This meme perfectly captures the quintessential response of any experienced software architect or senior engineer. Complex system design questions rarely have a single correct answer; the optimal solution is always contingent on specific constraints, requirements, scale, and trade-offs. The phrase 'it depends' has become a humorous trope signifying that the person asking the question has overlooked the necessary context, and the architect is about to embark on a lengthy discussion about those very dependencies
Comments
9Comment deleted
A junior dev will give you an answer. A senior dev will ask for more context. An architect will say 'it depends' and then bill you for a three-hour discovery session
If "it depends" were a microservice, its SLA would be "consult ADR first" and its latency would scale with every follow-up question
After 20 years in tech, I've learned that 'it depends' is actually the most honest architecture answer - it's just shorthand for a 3-hour whiteboard session explaining CAP theorem, Conway's Law, your team's velocity, budget constraints, and why your CEO's nephew's blockchain idea won't solve your scaling problems
The architect's Schrödinger's answer: simultaneously the most frustrating and most accurate response to any technical question. After 20 years, you realize 'it depends' isn't evasion - it's the hard-won wisdom that context, constraints, team capabilities, timeline, budget, existing tech debt, organizational politics, and that one legacy system nobody wants to touch all matter more than the theoretical purity of any pattern. The junior dev wants a definitive answer; the senior architect knows that anyone who gives one without asking follow-up questions is either selling something or hasn't been burned enough times yet
After 20 years, “it depends” is shorthand for: what’s the workload shape, latency budget, consistency model, failure domains - and who’s paying the cloud bill?
'It depends' - the only design pattern that survives every tech stack pivot without refactoring
It depends - on your consistency model, P95 latency, team topology, RPO/RTO, and the CFO’s egress-fee allergy
Be like George Costanza, fake being an architect Comment deleted
"Technically yes, but ..." Comment deleted