c'mon it's not subjective. it's clear as daylight. | [reply] |
Production ready for my business (publishing) is different than production ready for real-time derivatives trading. Production ready for my brother's business (software testing) is different from production ready for a non-profit. Production ready for a web development firm is different from production ready for an ISP. Production ready for a biology lab is different from production ready for an industrial automation shop. Production ready for a sporting good store is different from production ready for a university.
Within those industries, production ready also depends on availability and skill level of developers, maintainers, managers, and consultants, as well as their taste for risk, the amount of ancillary tools and materials, and considerations for existing code and systems.
None of these are binary, off-or-on, simple, single right answer for everyone everywhere questions.
| [reply] |
Is it as much production ready as much as Perl 5 is for all/any business that currently Perl 5 is used for?
| [reply] |
I work in a shop where a majority of the code is not what I would call production ready. Yet it's in production and has been for years; failing on edge cases regularly and failing on normal things mysteriously now and then. The variance of quality of code and systems that are in production in the various shops of the world is astounding and in almost every freelance gig I've had I've seen code that I would never personally allow into production. "Production ready" is a subjective concept which I've seen to mean "hobbled and dangerous" as often, or more often than "solid and safe."
| [reply] |
