Comment On Boned

Being the consummate IT professional, John took pride in his ability to automate the more regular and mundane aspects of his job. While not everything bent to his scripting will, with the appropriate cmdlets, plug-ins and modules, there were few areas that were beyond his (automated) reach. [expand full text]
« PrevPage 1 | Page 2Next »

Re: Boned

2014-06-05 06:24 • by moz (unregistered)
After all, what's the worst John's brand new script could do?

Re: Boned

2014-06-05 06:24 • by WTF (unregistered)
Hard to read, uninteresting, WTF lacking story.

Unsubscribe.

Re: Boned

2014-06-05 06:25 • by Rnd( (unregistered)
Source for frist not found!

Re: Boned

2014-06-05 06:27 • by psuedonymous (unregistered)
John asked Roman what he had changed. Nothing, he was told

So, Roman's unchanged copy of the program pulled the config file and data from production (because he never changed to to look locally) and kept naffing up the production process by fighting for the same data?

Re: Boned

2014-06-05 06:31 • by Squiggle (unregistered)
Hello you're through to 3rd line support. How can I help?

Oh, the critical data import isn't working? Well that is to be expected, because $staffmember is currently on holiday.

Please check back in a week.

WONTFIX.
*click*

Re: Boned

2014-06-05 06:39 • by np (unregistered)
There is less risk in not changing anything.
Management doesn't know that John's new script won't break things in a catastrophic way.
Also some shops value a dev's work over IT.

As long as John handed the ropes over to Roman to maintain for the upcoming weeks/months of trying to figure out why a trivial local change broke production, who cares?
Roman may give up eventually and John's new script will get promoted. Or Roman decides he doesn't want to change anything and reverts his local changes and stops breaking production.

Re: Boned

2014-06-05 06:50 • by That admin guy (unregistered)
So the policy is to not try and fix something that isn't broken, so why doesn't the story just end with:

"And they put the old, working, .BAT file back into production and everyone lived happily ever after"

Re: Boned

2014-06-05 06:50 • by Kabi (unregistered)
434849 in reply to 434847
np:
Roman may give up eventually and John's new script will get promoted. Or Roman decides he doesn't want to change anything and reverts his local changes and stops breaking production.

Or Roman remembers that John already has a (possibly) working script, takes that and sells it to management as his brilliant fix...

Re: Boned

2014-06-05 07:04 • by QJo (unregistered)
TRWTF is:

a) not immediately finding the problem that caused the job to fail.

b) not immediately rolling back to the pre-Romanised version of the bat file, followed by Roman being required to share his proposed new (broken) version with John, who would then go over it with Roman to work out what it was that went wrong.

c) allowing Roman to continue with his broken script after the second time it happened.

After b) has happened, it would then be confirmed that it *was* something that Roman had done that broke it. (Note that it still has not been established that Roman's changes did in fact break it -- it could have been coincidental). It would also be an opportunity to call Roman out on his untruth that he never did nuffink.

Re: Boned

2014-06-05 07:06 • by faoileag (unregistered)
Erm... 44 lines, 831 words and 4848 characters just to say: "In company X management prefers to find the root cause of a problem first, even if that means waiting longer, before applying a fix"?

And it's not as if that would be a wtf.

Actually, saying "I don't know what causes the problem, but here is a replacement script that does not exhibit the same problems, so it must be a fix", that's wtf.

Re: Boned

2014-06-05 07:19 • by S (unregistered)
434854 in reply to 434852
faoileag:
Actually, saying "I don't know what causes the problem, but here is a replacement script that does not exhibit the same problems, so it must be a fix", that's wtf.


Well, it certainly can be. But on the other hand, when production is already failing, it's a lot easier to justify that kind of thing... telling the boss "I don't know what caused the bug, but the relevant code no longer exists".

Re: Boned

2014-06-05 07:33 • by Craig (unregistered)
TL;DR - Management being management

Re: Boned

2014-06-05 07:39 • by DaveK
434857 in reply to 434842
moz:
After all, what's the worst John's brand new script could do?
It might replace their forums with Discourse :( :( :(

Re: Boned

2014-06-05 07:44 • by Schol-R-LEA (unregistered)
434858 in reply to 434857
DaveK:
moz:
After all, what's the best John's brand new script could do?
It might replace their forum-going with intercourse :) :) :)

FTFY.

CAPTCHA: ratis - this sort of cheap humor barely ratis as worth the trouble, but I did it anyway.

Re: Boned

2014-06-05 07:53 • by anonymous (unregistered)
434859 in reply to 434843
WTF:
Hard to read...

Agreed!

Re: Boned

2014-06-05 07:56 • by geocities
No picture. I didn't even start reading because there's no picture!

Re: Boned

2014-06-05 08:17 • by cyborg (unregistered)
434861 in reply to 434860
geocities:
No picture. I didn't even start reading because there's no picture!


Given your name I presume it'd have to be a small animated gif of a rotating bone?

Re: Boned

2014-06-05 08:22 • by GWO (unregistered)
TBW, DR.

/ Too Badly Written, Didn't Read

Re: Boned

2014-06-05 08:28 • by Steve The Cynic
434864 in reply to 434851
QJo:
It would also be an opportunity to call Roman out on his untruth that he never did nuffink.

TRWTF is believing any colleague who says he didn't change anything.

NEVER believe such a statement. For working-relationship purposes, it's usually a bad idea to directly challenge it, but you turn it around. "I didn't change anything." "OK, so what did you do?" This isn't guaranteed to get a useful answer, but starting from "What did you do?" instead of "What did you change?" is possibly more useful. "Show me what you did." might be even better.

Re: Boned

2014-06-05 08:34 • by Smug Unix User (unregistered)
I'm sure a bash script would work much better.

Re: Boned

2014-06-05 08:34 • by Florent (unregistered)
434866 in reply to 434843
WTF:
Hard to read, uninteresting, WTF lacking story.

Unsubscribe.


After unsubscribing, remember to stop commenting.


captcha: enim, an enumeration with roman numbers.

Re: Boned

2014-06-05 08:41 • by Ziplodocus (unregistered)
434867 in reply to 434866
Florent:
WTF:
Hard to read, uninteresting, WTF lacking story.

Unsubscribe.


After unsubscribing, remember to stop commenting.



Maybe they're commenting on a replacement version of the production program that creates the article on his own PC

Re: Boned

2014-06-05 09:28 • by tin
434868 in reply to 434861
cyborg:
geocities:
No picture. I didn't even start reading because there's no picture!


Given your name I presume it'd have to be a small animated gif of a rotating bone?


And flashing text in a really odd colour over a really bad pixelly background.

Does anyone else wish Yahoo had kept Geocities around just for laughs?

Re: Boned

2014-06-05 09:43 • by Josh (unregistered)
434869 in reply to 434845
psuedonymous:
John asked Roman what he had changed. Nothing, he was told

So, Roman's unchanged copy of the program pulled the config file and data from production (because he never changed to to look locally) and kept naffing up the production process by fighting for the same data?


TRWTF is that it was a move and not a copy

CAPTCHA: distineo. The production file's distineo was Roman's local machine.

Re: Boned

2014-06-05 09:52 • by QJo (unregistered)
434870 in reply to 434864
Steve The Cynic:
QJo:
It would also be an opportunity to call Roman out on his untruth that he never did nuffink.

TRWTF is believing any colleague who says he didn't change anything.

NEVER believe such a statement. For working-relationship purposes, it's usually a bad idea to directly challenge it, but you turn it around. "I didn't change anything." "OK, so what did you do?" This isn't guaranteed to get a useful answer, but starting from "What did you do?" instead of "What did you change?" is possibly more useful. "Show me what you did." might be even better.


"But I didn't do *anything*."

"What, nothing at all? Absolutely nothing at all?"

"That's right, I didn't do *anything*!"

"So remind me again: why do we pay you?"

Re: Boned

2014-06-05 10:01 • by Anonymous Coward (unregistered)
434871 in reply to 434868
tin:
cyborg:
geocities:
No picture. I didn't even start reading because there's no picture!


Given your name I presume it'd have to be a small animated gif of a rotating bone?


And flashing text in a really odd colour over a really bad pixelly background.

Does anyone else wish Yahoo had kept Geocities around just for laughs?

Well, they did keep it around for Japan.
There's also always Neocities.

Re: Boned

2014-06-05 10:20 • by phuzz (unregistered)
Did someone say they wanted Geocites back?

Re: Boned

2014-06-05 11:05 • by Bill (unregistered)
434873 in reply to 434870
QJo:
"That's right, I didn't do *anything*!"
This ranks right up there in the collection of common lies along with LUsers describing their problems to the help desk:

HD: Do you see any kind of error message?

LU: Nothing.

HD: What's on your screen now?

LU: Nothing.

HD: Your screen is completely dark?

LU: Well not exactly.

HD: What color is it then?

LU: Mostly gray, except for some funny words at the top.

HD: I see. And what do those words say?

LU: (proceeds to relay the error message that didn't exist two seconds before...)

Re: Boned

2014-06-05 11:44 • by Nagesh
I did not get the punchline for this story.

Re: Boned

2014-06-05 11:44 • by Spanner number 3 (unregistered)
434875 in reply to 434872
Obligatary XKCD reference...

http://www.torwuf.com/xkcd-geocities/

Re: Boned

2014-06-05 12:22 • by Chelloveck (unregistered)
So, BAT file watches a magic directory for a file to appear, then ftps the file to another machine. Developer does something on his dev machine and the production system breaks. SysAdmin writes a replacement BAT file using Powershell. Management decides to keep BAT file in place until the root cause is found.

Scenario 1: Developer changed the production code or the production config file. Proposed solution: Rewrite the BAT file in Powershell. This *might* work, but will require test time and is likely to introduce new problems. Actual (but not suggested) solution: Revert the changes. Duh.

Scenario 2: Developer didn't change the production code or the production config file. That means his dev work is somehow preventing the file from being put into the magic directory, or manages to delete the file from the magic directory before the production code processes it. Proposed solution: Rewrite the BAT file in Powershell. This will *not* work, because the BAT file is not the problem. The file still won't be in the magic directory when the new Powershell script runs. Actual (but not suggested) solution: Fix Developer's dev environment so it doesn't touch production.

So, can anyone come up with *any* scenario here in which rewriting the production code from scratch is actually the right thing to do? 'Cause I sure as heck can't think of any.

Re: Boned

2014-06-05 12:30 • by CigarDoug (unregistered)
This is one of the few stories I have read on the Daily WTF where the villain is not clear after the first couple of paragraphs.

It is certainly the first one where I STILL don't know who the bad guy is after finishing the article. So, what was the WTF, and was there a solution?

Re: Boned

2014-06-05 12:35 • by Coyne
Looks to me like the well of understanding is bone dry; since it seems very unlikely that Roman will bone up on reality.

I feel in my bones that this is now a permanently manual process. This tickles my funny bone, since it will be Roman (the cause of the problem) wearing his fingers to the bone.

Re: Boned

2014-06-05 12:43 • by CigarDoug (unregistered)
434881 in reply to 434880
Coyne:
Looks to me like the well of understanding is bone dry; since it seems very unlikely that Roman will bone up on reality.

I feel in my bones that this is now a permanently manual process. This tickles my funny bone, since it will be Roman (the cause of the problem) wearing his fingers to the bone.

I think your understanding of the story is too marrowly defined.

Re: Boned

2014-06-05 12:53 • by Valhar2000 (unregistered)
To be fair, PowerShell is quite a bit more powerful than CMD (even CMD is more powerful than most people realize). You can generally make a shorter and clearer script to do something in PS than you can in a BAT file.

Given that, it may not be that bad an idea to replace the BAT.

Re: Boned

2014-06-05 12:58 • by Zylon
434883 in reply to 434879
CigarDoug:
It is certainly the first one where I STILL don't know who the bad guy is after finishing the article. So, what was the WTF, and was there a solution?

Turns out the president's daughter was deleting the source files off the server.

Re: Boned

2014-06-05 12:59 • by rekcuf rehtom uoy siht esrever (unregistered)
So the WTF is not using source control to track changes to the batch files?

Or is the WTF that the story is unreadable?

Re: Boned

2014-06-05 13:26 • by MoarCynical (unregistered)
434885 in reply to 434864
Steve The Cynic:
TRWTF is believing any colleague who says [s]he didn't change[/s] anything.

FTFY :-)

Re: Boned

2014-06-05 13:26 • by chubertdev
Does anyone else feel that this story was accidentally truncated, despite it being ten times as long as it should have been?

Re: Boned

2014-06-05 13:27 • by MoarCynical (unregistered)
434887 in reply to 434885
MoarCynical:
Steve The Cynic:
TRWTF is believing any colleague who says [s]he didn't change[/s] anything.

FTFY :-)

Sorry, I forgot strike-through doesn't work here. Maybe it works better on Discourse? :-(

Re: Boned

2014-06-05 13:29 • by haero (unregistered)
434888 in reply to 434868
tin:
cyborg:
geocities:
No picture. I didn't even start reading because there's no picture!


Given your name I presume it'd have to be a small animated gif of a rotating bone?


And flashing text in a really odd colour over a really bad pixelly background.

Does anyone else wish Yahoo had kept Geocities around just for laughs?

I thought that's why Yahoo kept themselves around?! LOL

Re: Boned

2014-06-05 13:31 • by faoileag (unregistered)
434889 in reply to 434875
Spanner number 3:
http://www.torwuf.com/xkcd-geocities/

My Eyes! The goggles do nothing!

Re: Boned

2014-06-05 13:35 • by faoileag (unregistered)
434890 in reply to 434887
MoarCynical:
Sorry, I forgot strike-through doesn't work here. Maybe it works better on Discourse? :-(

It does.

Re: Boned

2014-06-05 13:37 • by chubertdev
434891 in reply to 434887
MoarCynical:
MoarCynical:
Steve The Cynic:
TRWTF is believing any colleague who says he didn't change anything.

FTFY :-)

Sorry, I forgot strike-through doesn't work here. Maybe it works better on Discourse? :-(


FTFY

Re: Boned

2014-06-05 13:37 • by chubertdev
434892 in reply to 434887
EDIT: double post o_O

Re: Boned

2014-06-05 14:06 • by CEO of IBM (unregistered)
WTF is the need to mention 'all over again' all over again right after saying 'déjà vu'?

Use our cloud services and Watson to avoid embarrassing mistekes like these. Watson doesn't have much work these days anyway lol.

Re: Boned

2014-06-05 14:54 • by FormalWare (unregistered)
TRWTF is the implication that it is EVER summer in Winnipeg. Winnipeg has 3 seasons: Winter, Mosquito, and Roadwork.

Re: Boned

2014-06-05 14:54 • by Anon (unregistered)
434896 in reply to 434845
psuedonymous:
John asked Roman what he had changed. Nothing, he was told

So, Roman's unchanged copy of the program pulled the config file and data from production (because he never changed to to look locally) and kept naffing up the production process by fighting for the same data?


That is the way I read it as well.

So, TRWTF is that Roman's development environment had modify access to critical production files.

Also that they didn't just disable Roman's copy of the BAT (I'm assuming he had it scheduled) until Roman could grok it enough to fix it.

It seems that John intentionally encouraged Roman to leave his broken instance running so there would continue to be a production issue to justify John working on a new script.

Re: Boned

2014-06-05 15:06 • by anonymous (unregistered)
434898 in reply to 434887
MoarCynical:
MoarCynical:
Steve The Cynic:
TRWTF is believing any colleague who says [s]he didn't change[/s] anything.

FTFY :-)

Sorry, I forgot strike-through doesn't work here. Maybe it works better on Discourse? if you do it correctly. :-(

FTFY.

Re: Boned

2014-06-05 17:59 • by deleted (unregistered)
Maybe the president's daughter got boned with a vibrating .bat
« PrevPage 1 | Page 2Next »

Add Comment