<img src="https://media.daily.dev/image/upload/s--nFdWjnOX--/f_auto/v1767591337/ugc/content_1b78df4c-0f7b-4d7b-a9be-365d0c76d4de?_a=BAMAK+ZW0" alt="image-2004456597049815040">
We’ve all said it:
“Let’s just ship it, we’ll clean it up later.”
Later: me, staring at my own code like it was written by a stranger. 😅
you wondering why past-you made these choices 😅

Prince Kumar

A humorous take on the common developer experience of shipping code quickly with the intention of refactoring later, only to return and find the code confusing or poorly written. The post highlights the universal struggle with technical debt and the consequences of prioritizing speed over code quality.

Ship now. Regret later.

You cannot win in this game.
You are required now to ship it and they dont want it done properly and then later when problems arise you are a shitty engineer because you did not do it properly 😂

ship now, rip off the customer later - it works for me. (since 2023)

How many projects started as a PoC and management said “It’s good enough, ship it. We’ll re-write for maintainability, scalability, and sanity later.”?
10 years later…

I always wondered how many projects were “validated” fast and ditched not because the idea was wrong but the mvp sucked beyond repair…

For personal projects and Startups it’s going to be increased 😆