- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
It's just a wee little frist.
Admin
https://youtu.be/piWCBOsJr-w?t=39s
Admin
:giggity:
Admin
:hanzo: by 13 minutes.
Is there some dialect of English in which that means something other than :giggity:?
Admin
Not that I've come across...
@mott555?
Admin
@remy, @pjh, @aliceif, we've got another dupe.
Admin
FFS...
Admin
Reminds me of this formula:
You say 'X', but they don't hear 'X', they hear whatever they want to hear. Then they come back and blame you, and harrumph when you say to them 'No, I said X'.
It would just be easier if advocates of this stupidity-revealing dumbassery just Learned To Fucking Read, but of course, management has the ample meal-based-weight to throw around that it's somehow still your fault.
Admin
What some people seem to think: Things can be made good by filling them with Monty Python references.
The actual truth of the matter: Monty Python remains good, despite the people who continually reference it.
Admin
Agreed. On both counts.
From what I remember of the film, this article parodies a particular section of it. Not that this is the riason d'etra for my replying to the post other than to add: That I, cannot for the life of me, see anything in the "story" that warrants such treatment.
But, given that there is (supposedly) a grain of truth or two in these sort of stories; I suspect the bits about "...waiting and waiting..." and "...several months later..." could be them. This reminds me of a time in my life (a few decades ago now) where I was undertaking a leadership assessment course. One of the exercises was to make recommendations based on certain scenarios. One scenario "threads" was about situations that just got worse and worse. Each successive example was just a ridiculous extension of the previous.
Something had to break and I am afraid it was me. I had a serious sense of humour failure and just wrote "This [deterioration] should not have been allowed to progress this far" across all subsequent scenarios with increasing application of pressure.
Turns out they were looking for answers that simply stated "escalate" whereas I was trying to "fix" them.
My point being, I cannot understand why people do not "own" projects and problems and are quite prepared to create an SEP Field, to make them "go away". Anymore than I can understand how Companies and Organisations survive by creating a culture that nurtures such attitudes.
BTW The SEP Field was brought you by the same people that developed Bistromathics.
Admin
Typo/copy-paste/editing/brainfart error.
Admin
Part of the problem is that managers are promoted to their level of incompetence Peter Principle
Admin
@loose,
I think you meant "raison d'être"
Admin
ham ham ham eggs bacon and ham
Admin
If nobody is actually interested in making a project happen, should the organisation be doing it in the first place? (Sometimes the “interested” might be forced by regulation, which is a from-the-top approach, but that's still a valid reason.)
Admin
I hope he learned his lesson: Never bail out another department by doing their job.
Instead, the correct strategy (unless the head of the software team is immune from consequences due to nepotism) was to:
Yes, this strategy will hurt the company, but frankly, they deserve it for hiring such an inept software team.
Admin
The problem is that this does happen. At some point, things need to be not your problem. If things keep escalating they won't be fixed until you escalate till the first common manager.
Even if you follow up yourself, it is advisable to start CCing a next level of management (both sides) every couple of weeks of no progress.
Admin
I came up with a law a long time ago (I think I did, I have no recollection that I'm quoting someone else any way)
Which is my way of saying: Do it right the first time, even if it is a quick script. Otherwise, you will be haunted by your past mistakes or laziness :^)
Admin
Um, no. The project manager should be doing that. I should be bugging my PM (in addition to my boss).
Admin
Douglas Adams was pretty big, but there was only one of him.
SEP works amazingly well, though. At one company where I was given a troubleshooting role, there was a particular production assembly process of an electronic module that was giving problems. The manufacturing director, the assembly room manager and the technicians could walk right past this problem area without seeing it, leaving it up to the production supervisor.
It turned out that some genius thought that passivated screws were the same as tin plated screws, and passivated screws don't conduct electricity. As in this story, the customer was appointed to be in charge of QA and was not happy. The manufacturing director ended up running a convenience store in a seaside town.
Admin
Can we get a de-fictionalized version of this story like we did with Pizza Hacker
Admin
Would you prefer if there was a version of TDWTF called TDWTY?
Admin
This is the well known engineering law "The temporary is permanent, the long term will be obsolete next week."
I had a boss in the 1970s who was really nervous about this, and was anxious that we never just put something together in a hurry for someone, because we would then be supporting it forever. While he was away on a long job in China we had to put together a rush solution to an automation problem, so to ensure it didn't become permanent we put the industrial computer in a cardboard box (the on/off switch was a latching emergency stop button, the run button was a large green affair.) The idea was that the plant often had visitors, and this would ensure the cardboard box setup got replaced. It was still there when the boss got back and he was not pleased. But what particularly annoyed him was the operators reporting that they preferred big red and green buttons to the expensive illuminated keys we had been using up till then.
Admin
Except for a few names and the Monty Python dialogue, as well as some minor structure/gramming/phrasing, it's identical to the original submission.
Admin
Nice in-reference.
Admin
I think I was trying to say that. The point being that Tim was waiting for the API to be delivered and was quiet happy at it not being so. The story does not indicate if he escalated or CC'd anybody. As the
of this Site is to accurately document WTF's we must assume that if is not in the story, it didn't exist or it didn't happen.By all means try a fix a problem before it gets to bad, and in a way that does not increase your enemies. But, Operation Arse Covering Exercise needs to start quite quickly with Phase I - "There is a problem and I am trying to deal with it". Swiftly moving in Phase II when you think you have earned enough brownie points.
Admin
If that's your attitude then why don't you just write a completely fictionalized hacker drama or rename this to something. I honestly don't think that the daily WTF is entertaining to read anymore now that it's no longer about the WTF. The culture in the writers seems to indicate that it's more about these poorly-done embellishments.
If I want a story about people imagining they're doing something more fanciful than they actually are, then I'd just rather watch reruns of Muppet Babies.
You won't be hearing from me again
Admin
Admin
Based on what I saw in this organization, I'm guessing there was nobody approaching a competent PM. It's perfectly reasonable for him to ask as well.
Admin
It's funny when people post stuff like this and assume other people care. So long.
The trouble is, real hacking is boring to watch. There's a reason why hollywood uses the completely made up bullshit, and it's the same reason as the 10 mile long runway in the Fast and the Furious.Admin
Admin
He must be new here. Anyone who has been reading for a while knows we're all trolls here. So... we won again!!
Admin
Don't let the door hit you in the ass on your way out. Or do. It doesn't matter to us.
Admin
Do we really want to have to clean the assprint off the door though?
Admin
not likely, even pizza hacker was fictionalized to protect the innocent. besides the underlying WTFs in some of these stories are so weak the fictional story is really needed to punch it up and make it entertaining to read.
and even then no matter what the really interesting and :wtf: stuff always comes out in the comments anyway.
Admin
Meh. That's a problem for those low-paid workers of dubious nationality who come in after everybody else has gone home.
Admin
Dammit...got me.
Admin
All the details of real life tend to get in the way of interesting stories.
Admin
Admin
Damn you, reality! *shakes fist*
Admin
Exactly: Tim should've said "no, I didn't write any such thing" when management asked.
Admin
Exactly. TRWTF is Tim didn't complain to Roger[1]'s boss.
[1] Placeholder, in case I forgot the person's actual name.
Admin
The door's not glass, so as long as there's no stain, who cares?
Admin
Is it so bad to want things clean? :stuck_out_tongue:
Admin
No, but an average skinprint won't leave a visible mark on an opaque door.
Admin
Thanks for the visual of "what would an un-average skinprint look like?"
Admin
Admin
Years ago, working for a small software company, I had written a piece of software that used multiple, scheduled threads to keep data in sync. The core of the app was fairly simple: a single thread that kept track of all upcoming schedules, and spawned a thread to perform the sync operation and then die at the specified time.
My boss, however (who knew little to nothing about multi-threaded applications), decided that the application would be faster and more efficient if it just spawned a thread for each task that had to be synced and let each thread track its own schedule. He then decided that incoming and outgoing sync each needed their own thread for each task so that they would not conflict with each other. I argued, literally, for hours, but was "outvoted". I made sure that my argument was extremely public within the dev team.
Sure enough, the first time we had a project come up that had 12 sync tasks, the whole thing crashed during boot-up, because it hit the 24 thread limit for a single application (including the thread that was the service itself made 25).
Luckily, most everyone at the company was very aware that I was against the design, so I didn't get the brunt of the yelling directed in my direction.
Admin
While you're welcome, I assume no responsibility for your inability to not imagine things.
Admin
That depends on @mott555, and I doubt he's as much of a nice guy I am.
I only wrote up the non-embellished version that one time because a) the embellishments were somewhat dubious and b) I tried to prove a point. But we write stories here, not documentaries, and it's our liberty to reject the reality and substitute our own.
Because that's how we roll, COMPLAIN.
If that's your attitude, why don't you read a newspaper? Because this site is obviously not what you want.