http://www.perlmonks.org?node_id=756093


in reply to Re: Secure Perl Coding Standards
in thread Secure Perl Coding Standards

it's more serious consequences for not knowing how to do your job

That is the heart of the problem, the people who tend to be in charge are the least able to evaluate other peoples skills. I have had one manager who knew how to program. He was up to a** in alligators trying to get his bosses to line up a more stable development environment. So he ended up not being able to do that much.

All the rest of the managers, they did not want to get involved with anything involving processes, they mostly wanted to mediate between departments and individuals. They did not themselves people who involved themselves directly with work and therefore had not ability to evaluate whom was doing what. Why do think so many companies suck at development? They put non-technical people in charge of the technical side of the business and it sucks.

Until you get managers who view themselves as part of the work process it is very hard to implement a standard on how work should be done.

Replies are listed 'Best First'.
Re^3: Secure Perl Coding Standards
by Your Mother (Archbishop) on Apr 07, 2009 at 17:48 UTC

    I totally agree. I tried to work a little about that in but I didn't have a good example. Some of the most awful security holes I've seen were known but persisted because of an unwillingness to pay the development costs required to fix them.