[gonzalohm]

Except you do this in a corporate setting and they will stop you the second it works. And then you are stuck maintaining a barely working version forever.

I learned this the bad way, but now I just lie and say it doesn't work until it's good enough for me

[dbvn]

^^^ THIS ... If what you're building is useful, showing someone a prototype too early can cause the whole company to rush you to deploy.

[olliepro]

Everyone's threshold is different. I aspire to "move fast and break things", but more often than not, I obsess over the rough edges.

[josephg]

This is what it looks like when trust has broken down at a company. Management don't trust engineers when they say "this needs more time". And engineers don't trust management with the truth (it kinda works - we really could ship it now if we wanted to).

Remarkably common, but not inevitable. Thankfully there's plenty of workplaces which don't look like this.

And yeah, lying is certainly one way to get work done in a bad organisation. I'd much rather - if at all possible - to find and fix the actual problem.

[gonzalohm]

I think the problem is that in the current system, the blame is always on the engineer. If you ship something early and it didn't work, then it's your fault because you didn't QA it enough.

If you don't ship it in time it's also your fault

This is bound to happen with any company that needs to deliver to clients. Sales are incentivized to sell at all cost, even if the product is not there yet.

[tripledry]

Another fun one is when sales has already sold the thing to the customer without there being a product to sell. At that point it stops being about trust it's just "get it out there".

I hate this, but seems to be fairly normal practice.