Stakeholders Clients
Post #3876 · source on Telegram
Client demands a cruise-ship-airplane and wonders why we misunderstand requirements
Description
The meme has a white background with an orange header that reads "Client requirement…." Below, black text says: "Client: Why don't you clearly understand my requirements?" followed by "His Requirement :". Under this conversation, a photoshopped image shows a massive ocean cruise liner grafted onto the fuselage, wings, landing gear, and engines of a jumbo jet - illustrating a physically impossible hybrid vehicle. The visual gag conveys how stakeholders often articulate contradictory or over-combined feature sets that defy engineering realities, reflecting common software situations where vague or ever-expanding requirements (‘scope-creep’) lead to misalignment between developers and clients
More like this
More like this in Stakeholders Clients →
Use J and K for navigation
Comments
9Comment deleted
PM: “We need a monolith that scales like microservices, runs serverless but on-prem, delivers offline real-time analytics, and is simultaneously GDPR and FAA compliant - basically cruise-ship comfort with jetliner speed.” Architect: “Cool, I’ll just toggle the ‘defy-physics’ feature flag.”
This is what happens when the client insists their microservice architecture needs to be 'monolithic for performance but distributed for scalability' while also being 'serverless but on-premise' with 'real-time batch processing' - and they wonder why the sprint planning takes three sprints
This perfectly captures the moment when a client asks for a system that's simultaneously stateless and stateful, horizontally scalable yet runs on a single server, has zero latency across continents, costs nothing to operate, and needs to be deployed yesterday - all while questioning why you don't 'simply understand' their crystal-clear vision of a cruise ship gracefully soaring through the clouds on jet engines
Their “simple MVP” needs FAA and IMO compliance, microservices that deploy as a monolith, and SLAs for both runways and harbors - what could possibly go wrong?
Turns out the PRD used “and” where “or” belonged - hence the cruise ship strapped to a 747; we just called it hybrid cloud
Client specs: a cruise ship at Mach 1. Dev delivers Kubernetes pods on legacy COBOL - now it's 'flying' sideways
Должен быть на гусеницах Comment deleted
should be on caterpillars (approximate translation) please use English in this chat Comment deleted
Just need a twin tail. Easy. Comment deleted