>> The primary function of a legal department is to provide advice that prevents legally actionable mistakes. This advice does not have to be sane, or efficient, (...)
>Strong disagreement. As a counterport, would you agree to the following: ``the primary function of a programming department is to crank out code. the code doesn't have to run predictably, nor be maintainable nor indeed have any business requirements. KLOC is the king.''?
I don't see where you are getting KLOC; KLOC is rarely a metric that Programmers like. They'd choose readability, or (run-time) efficiency or something.
But yes; That's what you see. In both cases, really; I know last time I went to a lawyer for help with a AUP or privacy policy, I got something ridiculously one-sided that protected me, but would have been an absolute PR disaster to actually hand out as policy.
And yeah, I've seen programmers come up with solutions that were equally good from a purely technical perspective, but equally insane from the perspective of the whole business.
This is why managing a business is so difficult. You can't expect the lawyer to understand PR any more than you can expect your programmer to understand marketing. (I mean, sometimes you get lucky and find someone that is pretty good at both... those people are quite valuable, if you can find them.)
Actually, that's another discussion entirely. When you see the company you are working for (as a narrow specialist) doing something that is bad outside of your specialty, how hard do you try to change that? I mean, certainly, you should say "This isn't my specialty, but I think doing X is wrong, I think you should do Y" - the question then, is how hard do you fight for it. I mean, it is the person managing the company's job to choose specialists who are competent. At what point do you step out and say "Hey, you screwed it up" outside of your specialty?
>Strong disagreement. As a counterport, would you agree to the following: ``the primary function of a programming department is to crank out code. the code doesn't have to run predictably, nor be maintainable nor indeed have any business requirements. KLOC is the king.''?
I don't see where you are getting KLOC; KLOC is rarely a metric that Programmers like. They'd choose readability, or (run-time) efficiency or something.
But yes; That's what you see. In both cases, really; I know last time I went to a lawyer for help with a AUP or privacy policy, I got something ridiculously one-sided that protected me, but would have been an absolute PR disaster to actually hand out as policy.
And yeah, I've seen programmers come up with solutions that were equally good from a purely technical perspective, but equally insane from the perspective of the whole business.
This is why managing a business is so difficult. You can't expect the lawyer to understand PR any more than you can expect your programmer to understand marketing. (I mean, sometimes you get lucky and find someone that is pretty good at both... those people are quite valuable, if you can find them.)
Actually, that's another discussion entirely. When you see the company you are working for (as a narrow specialist) doing something that is bad outside of your specialty, how hard do you try to change that? I mean, certainly, you should say "This isn't my specialty, but I think doing X is wrong, I think you should do Y" - the question then, is how hard do you fight for it. I mean, it is the person managing the company's job to choose specialists who are competent. At what point do you step out and say "Hey, you screwed it up" outside of your specialty?