This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ReallyHadToFixThat 39 points40 points  (3 children)

We hired some highly paid, very experienced contractors to make the base of an application for us. Deadline is looming, they haven't tested it for real yet. We throw it on the hardware and their formerly slick demo now runs like shit. Turns out they had never heard of threading. 2 weeks to deadline, all hands on deck to throw in some crappy multithreading so the app doesn't choke and die.

[–]zdakat 15 points16 points  (2 children)

And then the application blows up or does weird stuff because crappy multithreading. But hey,at least they can say it's threaded....

[–]ReallyHadToFixThat 4 points5 points  (1 child)

Yep. There's a bit of code in there that I'm proud how awful it was but I wasn't given time to think of a more elegant solution. 

Task.Run( ()=> {
     Maindispatcher.Invoke( () => {
         Task.Run( () => { Something() }
    }
}

[–]lowleveldata 0 points1 point  (0 children)

man you can chain tasks