Print Story A Day in the Life
Working life
By ReallyEvilCanine (Mon May 08, 2006 at 03:30:13 AM EST) A Day in the Life, cubicle, fucktards, open source, LOL What, WTF, pie (all tags)
Secrets

While I'm a fan of Open Source, $OurBigApp is closed source. Despite six years with the company and making a pretty strong case to a buddy who has access the source code, I was denied my request (read: repeated begging) to see a little bit of it to help a customer.

x-posted from da brog

Poll: What to write tomorrow.



Our company is involved with many Open Source projects, but $OurBigApp ain't one of 'em, in part because we have competition, and you'd have a hard time finding bigger champions of closed source than them. Also because $OurBigApp used to be a different company which was bought by a bigger company which is the one involved in Open Source. And also because, well, if we gave away how it all worked, a lot of us would have to look for real jobs.

Seriously, there is value or no one would buy our software. And yet, we may go Open Source within a few years and move from a sales to a service model. Or maybe not. Time will tell. It doesn't really matter to me; I'll have a job either way.

Meanwhile, the secrecy results in some interesting tickets, such as a case I'm still working on. It also makes such tickets frustrating as hell.

Our software has its own file system and we even explain a lot of the inner workings. Unfortunately, someone decided we needed to keep mum on a few bits of it, and one of those bits is the method used to distribute files into subdirectories. Why for the love of all that does not suck does someone actually think that's something we need to keep under wraps? There's nothing terribly innovative about it. More to the point, opening it up completely would work to our benefit, allowing customers to rework the system to best meet their needs.

It seems that whichever jackass made the decision did so thinking, "We need to have secrets and that's one of them. They'll live without the knowledge."

Except we have customers storing hundreds of millions of files. Billions in some cases. And that's where we have the problem, and it's not limited to Windows.

Boring but brief explanation: <^br>Windows can't store more than four billion files in any directory. Once you reach about half that, the system gets really sluggish -- so much so that requests will time out while the system is still looking for the file. It's worse in UNIX for very different reasons, getting very slow as the file count reaches only around four million despite the ability of UNIX to handle many more files overall. The reason is that at 4M, you need yet another inode: searching for a file requires slogging through three multiple indirect blocks.

I got a ticket a few weeks ago asking about some problems with the file system and our utility for setting up subdirectories. I answered quickly, sending the utility, and everything was running smoothly again. Then the guy asked about how the subdirectory distribution system worked.

"Well, I'm sorry to say that it's proprietary. But maybe I can get some additional information anyway. After all, this is an older version of our application and this particular method is no longer even used in our software."

The customer was floored and sent off a gushing note to my manager about people going the extra mile. Yay me.

I actually managed to get to the right person who would be able to tell me about it. Except he couldn't. What he told me I already knew and he couldn't get authorisation to tell me more. I tried again to see the source code just to figure out what the hell the distributor was doing and how it calculated doing it. No dice. And so I have to send the guy an apology that I couldn't do more for him and that he'll be stuck running a few scripts to constantly catalogue and track the files as they're written to the file system.

However, most of the time we get requests for information on the inner workings, it's shit like this:

Hi, we want to reverse engineer $YourBigApp. How do we do it?
Fuckwits.
< First Rule | BBC White season: 'Rivers of Blood' >
A Day in the Life | 7 comments (7 topical, 0 hidden) | Trackback
Nice post by ambrosen (2.00 / 0) #1 Mon May 08, 2006 at 04:52:59 AM EST
Good to see the way it works.

Don't get all uppity by Rogerborg (4.00 / 1) #2 Mon May 08, 2006 at 05:01:32 AM EST
I saw the guy who sweeps up in Burger King fiddling with the frier once.  Once.  The paramedics said they'd seen it before though.

-
Metus amatores matrum compescit, non clementia.
Unlike that guy by ReallyEvilCanine (4.00 / 1) #3 Mon May 08, 2006 at 05:06:44 AM EST
I just want to look at the various bits. I wouldn't actually be touching the wiring or taking a spanner to the gas connection.

the internet: amplifier of stupidity -- discordia

[ Parent ]
I think he peed in the hot fat by Rogerborg (4.00 / 1) #4 Mon May 08, 2006 at 05:11:39 AM EST
Ha, let's see you deny that intention.

-
Metus amatores matrum compescit, non clementia.
[ Parent ]
Bastard. by ambrosen (4.00 / 1) #5 Mon May 08, 2006 at 05:13:01 AM EST
Now I will never be able to get a job in the burger industry ever, due to the temptation to do just that.

[ Parent ]
Really? by Improbus (2.00 / 0) #6 Mon May 08, 2006 at 06:17:00 AM EST
I always thought that hot fat and water didn't get along to well ... did he burn his pecker?



If you immediately know the candlelight is fire, the meal was cooked a long time ago. --- Oma Desala
[ Parent ]
See, we're starting from the joke by Rogerborg (4.00 / 2) #7 Mon May 08, 2006 at 09:23:20 AM EST
and working back to the punchline.  Go back in time a couple of hours and come in again.

-
Metus amatores matrum compescit, non clementia.
[ Parent ]
A Day in the Life | 7 comments (7 topical, 0 hidden) | Trackback