Thursday 11 March 2004 — This is over 20 years old. Be careful.
Some thought-provoking software engineering reading:
¶ Frameworks, Good Code and the Opposite of YAGNI
Thursday 11 March 2004 — This is over 20 years old. Be careful.
Some thought-provoking software engineering reading:
¶ Frameworks, Good Code and the Opposite of YAGNI
Comments
Puzzled.
Ben points out the potential conflict of interest in the thread: that I advertise Teamstudio and also work for them, under the guise of Teamstudio actually being of benefit to this cause and these issues or not, when, in fact, I may have my own interests to worry about-- like getting as much revenue as possible, since I should gain financially if you give Teamstudio your money. He's right, I would benefit directly, because my work is aligned with the "corporate motivation" of increasing revenue, not necessarily increased code quality, which is much harder to quantify.
Such is the nature of business... take a look at any given company, and you only have a relatively small number of people working on the Intrinsic Value of the product/service (eg developers), when in fact it takes a lot more people besides just them to make it all happen and be successful (sales, marketing, accountants, etc). It's very interesting... I don't have to contribute to the Intrinsic Value of our products, yet my employer finds it very easy to find "corporate motivation" for my role and responsibilities (largley by aligning it with their own).
Add a comment: