Hacker News new | ask | show | jobs
by rcarmo 1735 days ago
This reads a lot like a lean/MVP manifesto. I would say that there is always a pressure to deliver working code, but that “unfinished” should always be in terms of project scope and not in terms of either functionality or reliability. “Code” is the wrong terminology here.

It’s OK to not have every feature implemented. But it’s not OK to ship half-baked, untested functionality, no matter what the “code” looks like.
2 comments
commandlinefan 1735 days ago
> This reads a lot like a lean/MVP manifesto

It also reads like the Agile manifesto from 20 years ago, which caused a huge splash when it was first published - before it was misinterpreted by everybody who might have been able to actually apply it to obtain results as "do exactly what you've always been doing (especially in terms of fixing a delivery date long before you describe what the software is supposed to do), but use terminology like 'sprints' and 'standups' to do it".

link
yakshaving_jgt 1735 days ago
Conversely, half-assed is ok if you only need half an ass.
link