The Perils of Showing a Work-in-Progress
Description
A screenshot of a tweet by Rachit Mishra (@rachitex). The tweet shows a dialogue exchange between a 'Client' and 'Me' (representing a developer). The client asks if the project is ready, and before the developer can finish explaining it's not, the client interrupts to complain about the UI. The developer's attempts to explain are cut off again by the client, who finally demands changes to something they don't like. This meme perfectly captures the frustrating and all-too-common scenario where a non-technical stakeholder provides premature, critical feedback on an unfinished product. It highlights the communication breakdown and lack of understanding about the development process, a pain point deeply familiar to experienced engineers who have learned to carefully manage client demos and presentations
Comments
8Comment deleted
This interaction is why senior devs insist on a product manager: to act as a human shield against clients who treat a WIP branch like the finished product
Client just filed a JIRA to redesign the skeleton loader they saw during the first 200 ms - apparently shimmer gradients weren’t in the spec
After 20 years, I've learned that "Is it ready?" actually means "I need to feel involved" and the correct response is to show them a completely different feature that IS done, let them critique that instead, then quietly finish what you were actually working on
Clients review WIP the way users read error dialogs: they don't, but they have strong opinions about it
The classic 'Schrödinger's UI' paradox: simultaneously not ready for review and already wrong. Clients have mastered the art of quantum observation - collapsing the wave function of your half-built feature into a definitive 'this is terrible' before you've even committed the CSS. It's like code review, but for code that doesn't exist yet, with stakeholders who've achieved the remarkable feat of providing feedback faster than you can type 'display: flex;'
When a stakeholder asks 'is it ready?', you've accidentally triggered UAT on an unmerged branch and created a scope-change ticket without acceptance criteria
Schrödinger’s UI: unready until observed - then it collapses the roadmap and spawns a high-priority “Change it” epic
Client UI reviews: where 'YAGNI' morphs into 'YAGCI' - You Always Gotta Change It, outpacing any framework's deprecation cycle