Frontend First, Functionality... Eventually
Description
An aerial photograph of a construction site shows several multi-story building facades, complete with brickwork and window openings, standing upright. However, there is nothing behind these facades; they are just empty shells propped up on a dirt lot, resembling a movie set. The meme text, in large white capital letters, is overlaid at the bottom: "WHEN FRONTEND IS READY BEFORE BACKEND". This image serves as a powerful and widely understood metaphor in software development. The visually complete but hollow building fronts represent the user interface (frontend), which can be built to look finished using mock data. The missing structure behind them represents the server, database, and business logic (backend) which is not yet complete, rendering the beautiful UI non-functional. It humorously captures the project management challenge of teams working at different paces and the awkward state of a project where the outside looks done but the inside is nonexistent. Two watermarks are visible: 'vk.com/humor' and 't.me/dev_meme'
Comments
7Comment deleted
Our frontend is feature-complete. Now if you'll excuse me, I need to go see if the backend team has finished inventing the database yet
Demo day: the React façade renders at 60 fps - then the user hits “Save” and free-falls into a 500 because the backend is still a Confluence page marked “TODO”
Just like these buildings, our frontend looks production-ready until someone tries to actually live in it - then they discover it's all useState with hardcoded demo data, axios calls returning Promise.resolve({todo: 'implement later'}), and a backend team still debating whether to use REST, GraphQL, or just rewrite everything in Rust
The classic scenario: your React components are pixel-perfect, TypeScript interfaces are immaculate, and the design system is chef's kiss - but the backend team is still debating whether to use REST or GraphQL while the database schema exists only in a Slack thread. Sure, you've got a beautiful facade with mock data, but try deploying that to production when your 'foundation' is still a TODO in the sprint backlog. At least the stakeholders think you're 80% done because they can click buttons that don't actually do anything yet
Definition of done: 100% Lighthouse, 0% endpoints - congrats, we shipped the Facade pattern literally
Frontend ships the facade; backend's still debating if we need elevators or just a service mesh
Pixel-perfect React on MSW mocks, OpenAPI still TODO - don’t worry, we’re calling it the Façade pattern