Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

scrottie (4167)


My email address is Spam me harder! *moan*

Journal of scrottie (4167)

Monday April 02, 2007
07:56 PM

Technical imparatives and one more heated resignation

[ #32885 ]

One more, in the middle of a heated meeting about fundamentally a technical problem, announsed his resignation and then was told to skip his two weeks. This is two people out, as far as I can tell, because of the broken, business serving, but engineering effort draining and fire causing release process. Rather than arguing with engineers, bully them, throwing your weight aroung -- *listen* to what they're saying. They're trying to help you. We're generally cold and impassionate people. If we ask for something, it's only to get you what you asked for from us. When we're stuck in the situation where we're paid money by you, and you've asked us to do something, and we can't, or it's being made extremely difficult for artificial reasons -- then there's no resolution for us to stop accepting your money and making implicit promises that we can help.



The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.

  • Programmers have principles -- technical principles. You do not ask a programmer to ignore his principles. A good programmer knows nothing good comes of this. The gains are short lived and thoroughly not worth the long term cost. Repeated experience with this solidifies the principle. A good programmer would no more deploy kludgery or pretend that a broken system works than he would rob a bank. Yet management is insisting, and taking arms when their demands aren't met. Ultimately their demands are fo