3 ms·

Doubtful, but this isn't even a good point. Working software is the important deliverable. An unmaintainable codebase makes it hard to deliver working software

Doubtful, but this isn't even a good point. Working software is the important deliverable. An unmaintainable codebase makes it hard to deliver working software in the future.

slantyyz 14y ago
So programming in PHP means that your code base will be unmaintainable?
- argv_empty 14y ago
  You'll have to talk to tych0 about that. I'm just responding to the idea of setting aside maintainability in order to produce working code.
- chc 14y ago
  No, deciding not to hire good programmers means that your codebase will be unmaintainable. Next time, maybe try reading the thread before commenting? Here's the discussion up to this point: OP: "If the event that my new ventures grow and I need to hire on more programmers I do not need the best and brightest to get the job done." tych0: "Sure, but your code will also suck and be hard to maintain." Domenic_S: "Doubtful, but this isn't even a good point. Working software is the important deliverable." argv_empty: "An unmaintainable codebase makes it hard to deliver working software in the future." You: "So programming in PHP means that your code base will be unmaintainable?"
  - slantyyz 14y ago
    I did read the thread, thank you. "An unmaintainable codebase makes it hard to deliver working software in the future." is a truism that I chose to respond with a question, because I am not of the opinion that Domenic_S was even remotely suggesting that anyone write unmaintainable code. Domenic_S's argument of "working software is the most important deliverable" isn't really a bad point, regardless of what language you're using. If you have maintainable code that doesn't address the application's requirements, how much does maintainability matter then? In the real world, there is hierarchy of priorities, and for most, working is at the top of the priority list.
    - deleted 14y ago
      [deleted]

Doubtful, but this isn't even a good point. Working software is the important deliverable. An unmaintainable codebase makes it hard to deliver working software in the future.

slantyyz 14y ago

So programming in PHP means that your code base will be unmaintainable?

argv_empty 14y ago
You'll have to talk to tych0 about that. I'm just responding to the idea of setting aside maintainability in order to produce working code.
chc 14y ago
No, deciding not to hire good programmers means that your codebase will be unmaintainable. Next time, maybe try reading the thread before commenting? Here's the discussion up to this point: OP: "If the event that my new ventures grow and I need to hire on more programmers I do not need the best and brightest to get the job done." tych0: "Sure, but your code will also suck and be hard to maintain." Domenic_S: "Doubtful, but this isn't even a good point. Working software is the important deliverable." argv_empty: "An unmaintainable codebase makes it hard to deliver working software in the future." You: "So programming in PHP means that your code base will be unmaintainable?"
- slantyyz 14y ago
  I did read the thread, thank you. "An unmaintainable codebase makes it hard to deliver working software in the future." is a truism that I chose to respond with a question, because I am not of the opinion that Domenic_S was even remotely suggesting that anyone write unmaintainable code. Domenic_S's argument of "working software is the most important deliverable" isn't really a bad point, regardless of what language you're using. If you have maintainable code that doesn't address the application's requirements, how much does maintainability matter then? In the real world, there is hierarchy of priorities, and for most, working is at the top of the priority list.
  - deleted 14y ago
    [deleted]