Stories
Slash Boxes
Comments
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 ]

Beatnik (493)

Beatnik
  (email not shown publicly)
http://www.ldl48.org/

A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.

Project Daddy of Spine [sf.net], a mod_perl based CMS.

In his superhero time (8.30 AM to 5.30 PM), he works on world peace.

Journal of Beatnik (493)

Friday September 28, 2007
06:13 AM

Never enough inodes..

[ #34559 ]
Out of the box consultants never have a clue when they set foot in our department. They fuck up at least one thing that causes us to wanting to grab a stick and chase him around the office. Yesterday, we had someone in for a 2 day job on testing pens. He ran an analysis script on our servers and apparently it was decided to use the smallest possible partition to store a gazillion analysis reports on. The smallest partition in this case was the home folder NFS share for the remote users. Byte-wise, the partition was far from full, inode-wise, it was an ex-partition. *SIGH*
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Don't you ever come across any new consultants who don't screw up all the time?

    What behaviour and strategies do they use to not annoy the hell out of you? Do they nag you with never ending questions instead, or can they cope with it some other way?
    • I was impressed with an Oracle consultant I worked with [dbperfman.com]. We needed serious help dealing with some performance issues and he was very, very good. Part of what helped is that he did serious interviewing of the entire development team to find out what we needed and many of our recommendations made it into his final report. He also turned out to be really good at database normalization (even to the point of recognizing when normalization would be a bottleneck).

      • With a name like that (dbperfman), you'd wonder whether the dude's gonna show up wearing a superhero cape.

        But then I looked at the site [dbperfman.com], and he is obviously a ninja (and ninjas don't wear capes).
  • One company I worked at paid over $100,000 to consulting firm to come in and tell us what one of our systems did. This might not seem surprising as it can be difficult to answer this for legacy code, but this was a system that was currently in development! Only one developer was on the system and they arranged a meeting with him -- on the last day they were there and right before he was quitting the company. Not surprisingly, their description of the system was useless.