• (cs)

    Looks like a new version of the Wooden Table.

  • Mark (unregistered)

    Call to common. You discover a better way and it isn't adopted simply because you and not them came up with it.

  • Mark (unregistered)

    All to common. You discover a better way and it isn't adopted simply because you and not them came up with it.

  • UNKLEGWAR (unregistered)

    Glad to see that the US isn't the ONLY goverment that pays unskilled workers too much money to do ridiculously unecessary jobs in the most inefficient way possible.

    Ironic CAPTCHA: Dubya

  • RON (unregistered)

    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

  • spathi (unregistered)

    Sergio?

    From efnet #...games?

  • Southern (unregistered)

    Yup, that pretty much sounds like the Argentinean way.

  • SomeCoder (unregistered)

    I really want to know which company this is. Barring the anonymization, this sounds a LOT like something my company would do back in the late 90s.

    I won't go into details, but they were doing egregious things like "Gustavo" when I arrived. I spent my first year with the company trying to show them better ways to do things like this.

    The real WTF is that I succeeded and don't have a WTF story to tell about it :)

  • Will (unregistered)

    Even easier:

    dir /b *.tif > filelist.txt
  • moe (unregistered)

    Digitize This! [image]

  • (cs) in reply to RON
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

  • (cs) in reply to Erzengel
    Erzengel:
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

    I hate to break this to you, but companies don't exist to keep people employed. They exist to make as much money as they possibly can and spend as little as they can in so doing. Understanding this concept and exploiting it for your own career benefit is not an evil thing to do.

  • Frost Cat (unregistered)

    I can't even imagine wanting a paycheck so badly I'd do something that tedious.

    I guess if I were enterprising and graft-minded, I'd use the shortcut way and then play Solitaire or something.

  • bobbo (unregistered) in reply to mdk
    mdk:
    Looks like a new version of the Wooden Table.

    I haven't been hanging round here very long, WTF is the Wooden Table referring to? (To save me being bothered looking)

    Actually, I probably don't want to know. I'm already sick of "Captcha", "Fist" and "The Real WTF". Oh, and endless point-missing.

    I'll get my coat...

  • (cs)

    This reminds me of my favorite shirt.

  • (cs)

    The Real WTF (tm) is that Windows Explorer still doesn't have a built-in method for printing a file listing. That is, to me, an order of magnitude beyond ludicrous.

  • (cs) in reply to Zylon
    Zylon:
    The Real WTF (tm) is that Windows Explorer still doesn't have a built-in method for printing a file listing. That is, to me, an order of magnitude beyond ludicrous.

    It does. There's just no way to automatically save the contents to a file.

  • ZSB (unregistered) in reply to bobbo
    bobbo:
    mdk:
    Looks like a new version of the Wooden Table.

    I haven't been hanging round here very long, WTF is the Wooden Table referring to? (To save me being bothered looking)

    Not in the category of captcha and first, IMHO.

    It's a reference to an old WTF where IIRC someone needed a flyer for a web page, so they printed it out, took a photo of it (sitting on a wooden table), then scanned in the photo and posted that to the site. http://worsethanfailure.com/Articles/Web_0_0x2e_1.aspx

    mdk is correct in that this does look like a similar issue.

  • Former Jr. Programmer (unregistered) in reply to Mark
    Mark:
    All to common. You discover a better way and it isn't adopted simply because you and not them came up with it.

    That's not the WTF. Gustavo had JOB SECURITY with his slow job. If it's done in an instant with a script, Gustavo has to find another job.

    Captcha: ninjas - as in, script is relatively as fast as.

  • (cs) in reply to moe
    moe:
    Digitize This! [image]
    roflMaOOOOOO
  • Benjamin Smith (unregistered) in reply to RON

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    The solution to this is to become management, or start your own company. Yes, it really IS that simple. Come up with something like that in MY company and I'll give you a nice payraise...

  • (cs)

    I came across a very very very similar situation at a US Govt site.

    Shirley was a typist. She typed up contracts. One day I asked her to add one paragraph to page 2 of a 33 page contract.

    She said that would take her about two days.

    Huh? To add one paragraph?

    Yes, Shirley said. You see, she saved each page in a separate file, so adding a paragraph to page 2 would require spilling text from file 2 to 3, 3 to 40, etc, etc, etc.

    She'd been doing this for over three years.

  • (cs) in reply to dp.design
    dp.design:
    I hate to break this to you, but companies don't exist to keep people employed. They exist to make as much money as they possibly can and spend as little as they can in so doing.
    That is highly debatable, but no matter whether you believe that companies exist to make money or to serve public interest (which WAS originally a major part of the concept of corporations), they obviously should do it in an efficient way.

    The real WTF is that neither Sergio nor Gustavo could imagine that automating this task would lead not to Gustavo getting fired but to him getting moved to a useful task that could NOT be automated as easily.

  • Magnus (unregistered) in reply to dp.design
    dp.design:
    I hate to break this to you, but companies don't exist to keep people employed.

    Correct. That's what government agencies are for.

  • jbinaz (unregistered)

    Two stories.

    First, involving me. My first degree in college (university for our non-American readers) was in Criminology. A friend of my father (gotta' love connections) got me a job at the county sheriff's office in the sexual battery unit (an interesting place, to say the least). My first day, I showed up and the office manager gave me paperwork to file. She showed me how the filing system worked and I got busy. A few hours later (about 11:30), after working diligently, I came back and told her I was done. She looked horrified and told me that was supposed to have lasted until at least after lunchtime, if not mid afternoon. That set the tone for me and the three high school kids I worked with.

    And one of the other college age girls I worked with? Yeah, she had to be "spoken to" about how appearing in a Two Live Crew video (this was in 1989) in a skimpy bikini grinding on every guy was NOT good for the department image. That little incident made it all the way to the top of the entire sheriff's office.

    The second story I heard this weekend. A guy (Joe) was temporarily hired to paint fire hydrants in his city while the full time guy (Steve) was out on medical leave. He was told by his new supervisor to not paint more than 10 per week, as that's all Steve had done each week for years. My friend, Joe, finished all 10 on Monday and spent Tuesday-Friday down at the beach. Your tax dollars at work. Thankfully, Joe is grew up and is a hard-working guy and is embarrassed at his youthful tax-dollar wasting.

  • J (unregistered)

    The real WTF was that they were physically slicing up the maps then taping them together again. My girlfriend is an archivist and she goes to great lengths every day to avoid mutilating physical artifacts.

    Even discounting the value of the maps as physical objects, some people may think that the data is being preserved and that's the true importance of archiving. To them I say, which data would be easier for you to access if it was dropped on your desk this afternoon - a map printed on a piece of paper 300 years ago or a Corel file saved on a Jaz drive 10 years ago?

  • jkndrkn (unregistered) in reply to spathi

    Sergio is a common name.

  • clickpunch (unregistered)

    80% of my job is pretty much this. We get data updates from an outside company, we print them out, I type them in to our proprietary software. I started temping here and tried to explain how they could stream-line it, but they hired me full time instead. I spend a lot of time online, and run some macros a couple times a week to keep up with the workload. Funny thing is, they know it.

    Each department is so protective of its data that they'd rather pay me full time to click "generate report" than let someone else do it.

    I do sometimes get to build new queries though.

  • (cs) in reply to UNKLEGWAR
    UNKLEGWAR:
    Glad to see that the US isn't the ONLY goverment that pays unskilled workers too much money to do ridiculously unecessary jobs in the most inefficient way possible.

    You are missing the point. It's no secret that the US Army subsidizes the Argentine army, as well as most other South American armies. That gives them the ability to use them whenever the democratic goverments get a bit out of hand.

    Latinamerican History 101.

    Addendum (2007-05-22 17:07): In other words, this is most likely a part of your Tax dollars at work.

  • whicker (unregistered) in reply to dp.design
    dp.design:
    Erzengel:
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

    I hate to break this to you, but companies don't exist to keep people employed. They exist to make as much money as they possibly can and spend as little as they can in so doing. Understanding this concept and exploiting it for your own career benefit is not an evil thing to do.

    Actually, it is evil, but it's the rules of the game we are forced to play. Ever stop to think that, just because that's the way it is now (consume and grow, anything less is death), that it's the sustainable way?

    People can find other jobs, yes. Stupid inefficiencies need to be eliminated; but what's the ultimate goal, to make the company owners rich beyond belief? To act as some sort of henchman, kept around until your usefulness to them is exhausted?

    It's all psychological. To say that a company doesn't owe its workers who served it in the past is just a stance. There isn't any reason why or why not, that's just the way people have allowed it to become.

    Make as much money as they possibly can = megalomanical Make a lot of money = intelligent and rational

  • (cs) in reply to J
    J:
    some people may think that the data is being preserved and that's the true importance of archiving. To them I say, which data would be easier for you to access if it was dropped on your desk this afternoon - a map printed on a piece of paper 300 years ago or a Corel file saved on a Jaz drive 10 years ago?
    If the printed map has not been kept in the right conditions (correct temperature and humidity, darkness), it's a mass of faded tatters and completely unusable. Digital archiving requires upkeep as well, and if you copy/convert the data to a current format and medium regularly, there is no problem.

    IMO the recurring scare stories about how digital data will become inaccessible in a few decades are hopelessly outdated. It may seem like that if you look at the proprietary file formats and storage technologies of the past, but these are disappearing in favor of standardized, downward-compatible solutions. In 5 years, your HD-DVD drive will still be able to read CD-ROMS made 20 years ago, and you'll probably still have an import filter for JPEG and PNG in your graphics software 50 or 100 years from now.

  • Kitgerrits (unregistered) in reply to Ancient_Hacker

    Hey!

    I remember being -forced- to work somewhat like that aeons ago. Mind you, that was because the machine only had 256KB of RAM and DOS and WP only left me some 30KB for the actual text...

    These days, I get annoyed at having to split that 4.5GB .ISO in 2GB chunks because the recipient doesn't support UDF...

  • anonymous (unregistered)

    that screenshot ocr thing is a best practice where I work, don't dis it.

  • Theo (unregistered) in reply to jbinaz
    jbinaz:
    And one of the other college age girls I worked with? Yeah, she had to be "spoken to" about how appearing in a Two Live Crew video (this was in 1989) in a skimpy bikini grinding on every guy was NOT good for the department image. That little incident made it all the way to the top of the entire sheriff's office.

    I also need to be "spoken to" about how it would not be good...

    Captcha: yummy. no kidding...

  • (cs) in reply to dp.design
    dp.design:
    Erzengel:
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

    I hate to break this to you, but companies don't exist to keep people employed. They exist to make as much money as they possibly can and spend as little as they can in so doing. Understanding this concept and exploiting it for your own career benefit is not an evil thing to do.

    "exploiting it for your own career benefit" sure sounds evil to me. Exploitation for selfish gain. Exactly what Enron did, or the Oil Barons, or Microsoft during their monopolistic practices time. If exploiting something for selfish gain isn't evil, what is??? How about causing your coworkers to lose jobs for no personal benifit? All I ask is you consider what it is you're replacing. If you give someone doing a tedius task a tool to make it far less tedius and more automated, they still keep their job.

    But if management asks you to automate something, automate it. That's what you were told to do, so do your job. If management hasn't told you to do it, then why are you doing it? It's not your job. Tell the person a better way of doing it (or even give them the commands), but don't out-and-out replace them. It's not good to "go over their head" as it were.

  • Dude (unregistered)

    WTF? Haven't these guys heard of GIS software like ArcGIS or something???!!

  • A. K. Bear (unregistered) in reply to RON
    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.
    I was not congratulated at all.

    When I was young and naive and had some free time at my old programming job, I would take over other peoples' bugs, write extra utilities to make life easier, etc., etc. This was all well and good until I did something bad.

    See, we had RTF templates that would be used to generate PDFs. My manager had written a windows process in C to do this. His solution was:

    1. Insert the RTF into a database queing table.
    2. His process would grab the file from the queue and write it to disk.
    3. Open up the file in MS Word.
    4. Print the file to a PDF using a PDF printer driver.
    5. Update the original database record with the new file.

    The servers that did this processing had to be rebooted once a night or they would crash the next day, because his process leaked memory like crazy. It also generated massive documents - each page was an embedded image in the PDF.

    I found that it was much easier to use some free tools on the command line under Linux. Not only was the process MUCH faster, it retained the actual TEXT instead of creating a massive image, resulting in MUCH smaller files - 15-20k instead of 300k+. We already had Linux servers running things and all the necessary tools were already on the servers, so it should be an easy project to have approved.

    I was excited. My manager would be happy about this, right? So, I told him, "Hey, check this out. This seems like a better solution, what do you think?"

    That was my first lesson in office politics: Egos are very, very easily bruised. If that ego happens to belong to your manager, watch out.

    Captcha: Smile!

  • tamosius (unregistered) in reply to Erzengel
    Erzengel:
    .... But if management asks you to automate something, automate it. That's what you were told to do, so do your job. If management hasn't told you to do it, then why are you doing it? It's not your job. Tell the person a better way of doing it (or even give them the commands), but don't out-and-out replace them. It's not good to "go over their head" as it were.

    How about: some people simply don't like to be monkeys, so they use their brain, and improve processes that are highly inefficient, event if they are not a part of those processes?

    And.. aren't you an union guy or something? because you sure do sound like one ;-)

  • Charles Duffy (unregistered) in reply to Erzengel
    Erzengel:
    If exploiting something for selfish gain isn't evil, what is??? How about causing your coworkers to lose jobs for no personal benifit?
    Needless inefficiency is evil. When someone is being paid to do tedious, unnecessary work, that's wasted resources which could be put towards useful, necessary work -- or staying in customers' pockets, or being returned to shareholders to reinvest, or otherwise doing something other than being wasted on tedium which in no way betters society as a whole.

    If you'd like to discuss this further, feel free to follow up by email. [email protected]

  • (cs) in reply to Erzengel
    Erzengel:
    dp.design:
    Erzengel:
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

    I hate to break this to you, but companies don't exist to keep people employed. They exist to make as much money as they possibly can and spend as little as they can in so doing. Understanding this concept and exploiting it for your own career benefit is not an evil thing to do.

    "exploiting it for your own career benefit" sure sounds evil to me. Exploitation for selfish gain. Exactly what Enron did, or the Oil Barons, or Microsoft during their monopolistic practices time. If exploiting something for selfish gain isn't evil, what is??? How about causing your coworkers to lose jobs for no personal benifit? All I ask is you consider what it is you're replacing. If you give someone doing a tedius task a tool to make it far less tedius and more automated, they still keep their job.

    But if management asks you to automate something, automate it. That's what you were told to do, so do your job. If management hasn't told you to do it, then why are you doing it? It's not your job. Tell the person a better way of doing it (or even give them the commands), but don't out-and-out replace them. It's not good to "go over their head" as it were.

    To add to this thread: I started out as the salesperson for the company I work for. I created an Access database to track my customers and their orders, because there was no system for doing so.

    A year later, I was doing nothing but the database, no sales work. Six years later, I'm in charge of a very complex, very powerful SQL database, other people do the web pages on top of it, and I haven't handled a sales call in so long I don't even remember how to.

    I've automated a huge portion of what used to be manual processes in this company. Because of this, we can handle 100X the volume of orders we could handle when I first arrived, with 20 more people than we had when I first arrived (we're up to 30 staff now). We successfully compete with companies that are more than 20 times our size.

    Thus far, in six years, not a single person has been fired because of all this automation. I've eliminated six positions, but the people in them have moved over to positions that actually require human judgement or communication. Because of this, we don't have to have an automated attendant, we have actual humans answer the phone, which our customers love. We have people doing jobs that have dignity and require creativity, communication skill, judgement, etc., and computers doing almost all the boring, repetitive and mathematical jobs.

    Are there people who might have been hired if I hadn't done this? Sure, if they're looking for boring, repetitive, demeaning jobs at minimum wage that require no skill, intelligence or creativity. We'd probably have 10 or 20 more people. We'd have less happy customers, our order volume would be lower because our capacity would be lower, and employee morale would be just as bad as it is in most companies that have a lot of positions like that.

    All in all, I prefer the way we do it.

  • Frank (unregistered)

    Yeah, I'll admit it... when I read the first half of the story I was thinking "Boy, that's silly! They could write a script to do that!". So I, too, got "served" by the real solution.

    Captcha: dreadlocks... yeah baby

  • (cs)

    I've been in GIS for 10-years (for the government) and have never heard of anything like this. How sad!

  • (cs) in reply to A. K. Bear
    A. K. Bear:
    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.
    I was not congratulated at all.

    When I was young and naive and had some free time at my old programming job, I would take over other peoples' bugs, write extra utilities to make life easier, etc., etc. This was all well and good until I did something bad.

    See, we had RTF templates that would be used to generate PDFs. My manager had written a windows process in C to do this. His solution was:

    1. Insert the RTF into a database queing table.
    2. His process would grab the file from the queue and write it to disk.
    3. Open up the file in MS Word.
    4. Print the file to a PDF using a PDF printer driver.
    5. Update the original database record with the new file.

    The servers that did this processing had to be rebooted once a night or they would crash the next day, because his process leaked memory like crazy. It also generated massive documents - each page was an embedded image in the PDF.

    I found that it was much easier to use some free tools on the command line under Linux. Not only was the process MUCH faster, it retained the actual TEXT instead of creating a massive image, resulting in MUCH smaller files - 15-20k instead of 300k+. We already had Linux servers running things and all the necessary tools were already on the servers, so it should be an easy project to have approved.

    I was excited. My manager would be happy about this, right? So, I told him, "Hey, check this out. This seems like a better solution, what do you think?"

    That was my first lesson in office politics: Egos are very, very easily bruised. If that ego happens to belong to your manager, watch out.

    Captcha: Smile!

    I'm currently young and naive, so I just have to ask:

    What was your manager's justification for not switching over to your new method? In the article, "Sergio" came up with a better method to obtain the same result. You, however, came up with a better method to obtain a BETTER result. Even if your manager isn't "excited" about it, wouldn't he at least reluctantly agree (then take the credit for it)?

    Captcha: False Associationism (how appropriate!)

  • (cs) in reply to jbinaz
    jbinaz:
    And one of the other college age girls I worked with? Yeah, she had to be "spoken to" about how appearing in a Two Live Crew video (this was in 1989) in a skimpy bikini grinding on every guy was NOT good for the department image. That little incident made it all the way to the top of the entire sheriff's office.
    It is a good thing she had a stern "spoken to" otherwise she might have gotten an English degree instead of the teaching certificate she was working on.
  • (cs)

    But... I threw Rock!

  • SuperQ (unregistered) in reply to A. K. Bear
    That was my first lesson in office politics: Egos are very, very easily bruised. If that ego happens to belong to your manager, watch out.
    The best thing to do would be to simply run your script on the machine and overwrite his PDFs without him knowing.. the database would be smaller, it would run reliably, and he wouldn't even know.
  • (cs) in reply to UNKLEGWAR
    UNKLEGWAR:
    Glad to see that the US isn't the ONLY goverment that pays unskilled workers too much money to do ridiculously unecessary jobs in the most inefficient way possible.

    Ironic CAPTCHA: Dubya

    But in how many other governments does this include the chief executive?

    Oh wait... I guess that's not too uncommon...

  • (cs) in reply to Former Jr. Programmer
    Former Jr. Programmer:
    Mark:
    All to common. You discover a better way and it isn't adopted simply because you and not them came up with it.

    That's not the WTF. Gustavo had JOB SECURITY with his slow job. If it's done in an instant with a script, Gustavo has to find another job.

    Captcha: ninjas - as in, script is relatively as fast as.

    No, the WTF is that Gustavo didn't start using this new way and playing Solitaire for the rest of the week. (Still sitting hunched over his desk and grunting, of course, so as not to arouse suspicion). But perhaps that wouldn't have felt like real work.

    I guess Camus was right - "One must imagine Sisyphos happy."

  • iw (unregistered) in reply to Erzengel
    Erzengel:
    RON:
    Damnit. That kind of stuff happens all the time here at work. It's usually not as bad as photoshopping, but I still see people wasting hundreds of hours doing manually repetitive tasks that would take 20 minutes to write a tool to do automatically on an almost daily basis.

    Since last year I have written over 80 automation tools that have eliminated manual processes that would have cost the company 20 developer-years over the past year.

    Of course, the problem is that not only did I not get congratulated for this, but now I'm expected to write tools every time we need something manual done instead, in addition to my normal workload.

    Taking initiative in modern corporations simply is not worth it. The bureaucracy always finds a way to stifle it.

    And what happens to the people that were doing the manual, repetitive tasks? Do they just get fired because your scripts do everything they used to do for the company?

    No, you find other, more useful repetitive tasks for them to do. I'm certain the government has no lack of them.

  • Per (unregistered)

    It would almost be faster to just sit there typing out what you read in the file list. Seriously.

Leave a comment on “The Indexer”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article