3 ms·

I'd like to see that "Bug per 1K LoC" drop down list. There could even be an ISO rating and you could fail coders for not meeting their minimum bug counts. As a

• Justsignedup 13y ago
  Well. Listen, you get what you pay for. However I think BUG count is not the issue. It's code quality. What if I told you: "I need a POS implementation of Foo, it doesn't have to be maintainable but has to work with a taaaaad bit of ability to patch it up. I am trying to prove a concept is viable and show it off to like 50 people. I will rewrite this code if I decide to implement the concept. Also I want this done in ~ 1 week" Should that not drive down the price and time required? That means probably minimal tests, minimal abstractions, lots of copy-pasta, but still within decent coding guidelines and meets the needs