Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We agree, essentially. At the risk of really labouring the point though;

It'd be most efficient for time/cost reasons if we only ship to production code which is actually used in that build.

However, intermediate steps, or additional debug/test/migration/whatever code is required to get to the final state. You probably don't want to ship debug stuff into production.

Therefore, of the total quantity of code written, somewhat less than 100% is useful in production.

Therefore, you don't want to ship 100% of all code written to production.

> "how can we make it so that 100.0% of the code I type is shipped in the final product?"

This isn't necessarily desirable; but phrased slightly differently perhaps reflects more about production efficiency:

"how can we make it so that 100% of the production code is the only code I typed?"



Well, I don't disagree with what you typed there but I think we're off in the weeds a bit.

    "how can we make it so that 100% of the production 
    code is the only code I typed?" 
We certainly want to eliminate as many unnecessary steps as possible.

But much of that intermediate work iteration is inseparable from the discovery and refinement process.

To answer your question literally, "how can we make it so that 100% of the production code is the only code I typed?" would only be possible if you moved all of that discovery and iteration and refinement out of the coding loop or whatever.


Another approach would be to ship that first iteration, no matter how broken! Though I wouldn't recommend it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: