3 ms·

Shouldn't the business people in the organization also learn to understand the consequences to the company of poorly managed development processes and technical

• endtime 16y ago
  Yes, and that's what Tyrannosaurs is saying. The article is what's one-sided - it doesn't seem to understand that (unless you work for e.g. 37 Signals) software is in service of the business, and at the end of the day everyone's there to make money for the business.
  • BCGC 16y ago
    "... at the end of the day everyone's there to make money for the business" Really. It seems to me like everyone's there to make money for their departments / business units / lines of business.
    • endtime 16y ago
      Well, my company has only has 4 people full time, so maybe my perspective isn't representative. :) But I've had people who were writing code on a temporary basis get frustrated when things didn't stick to the spec 101% or when there wasn't time for them to follow all the software engineering practices they read about in a book and felt like trying...I understand all that stuff (I've been on both sides of the equation), but what bothers me is when people are inflexible on principle, to the detriment of the business.
• Tyrannosaurs 16y ago
  Absolutely it works both ways. The reason I posted from the position I did is that too often in these discussions there is the assumption that the programmer understand the business well enough to make the call which in my experience is false. The reality is that in these situations you have two people each of whom understand part of the problem. Simple black and white declarations of right or wrong by either party are unlikely to result in an optimal solution to the whole problem.