Programming test spec: build with bricks, but bricks are forbidden
Description
Dark-theme YouTube comment screenshot: a blurred avatar and the username “AJ” with the subtitle “vor 4 Tagen”. The comment text reads, “Programming questions be like:” followed by two quoted lines: “Build a house made of bricks.” and “NOTE: You are not allowed to use bricks.” Beneath this, the German link “Weniger anzeigen”, a thumbs-up icon showing 787 likes, a thumbs-down icon with no number, and the word “ANTWORTEN” appear. The meme visually contrasts the straightforward requirement with an immediate contradictory constraint, satirizing coding interview or assignment questions that ban the very tools needed (e.g., “solve with no loops” or “no built-ins”). It highlights the frustration senior developers feel when vague or conflicting specifications derail problem-solving
Comments
6Comment deleted
Latest interview task: ship a globally distributed, strictly-ACID, eventually consistent datastore in Go - submitting any consensus algorithm is grounds for disqualification
This is like being asked to implement a microservices architecture but you can't use network calls, or build a distributed system that must have zero latency and 100% consistency while being partition tolerant - sure, I'll just violate the CAP theorem real quick after I finish building this O(1) comparison sort
This perfectly captures the essence of modern technical interviews: 'Implement a distributed cache with O(1) lookup and insertion... oh, and you can't use hash tables, memory, or computers. You have 15 minutes.' It's the architectural equivalent of being asked to design a microservices system while being forbidden from using networks - technically possible with carrier pigeons and RFC 1149, but that's probably not what they're looking for
Enterprise spec in one line: “Brick house, no bricks” - aka strongly consistent, highly available, stateless persistence, and make it multi‑cloud to avoid lock‑in
Classic hiring brief: ship an exactly-once, multi‑region system with no queues, locks, or persistence - aka a brick house without bricks
Like speccing a 'stateless service with sticky sessions' - pick a lane, or watch it all crumble