Honestly, it seems like barely anyone in this thread even tried to understand it. A poor effort. Here's a pro-tip: don't declare something a WTF until you understand it. Otherwise, you just advertise your ignorance.

Bitcoin is a logical solution for the given requirements (the WTF comes only from the fact that it's a solution looking for a problem). Here's another pro-tip: if you try to understand it, focus less on the mining and more on how you verify transactions (the mining is just there as an incentive, to try and have more computing power in legit users than attackers).

In other news, Bitcoin is somehow still alive.

@Nitehawk said:

 @silenceisdefeat said:

TRWTF is that you think that social engineering = software engineering.

 The whooshing sound is the sound of a 21st floor window being left open. It is certianly not the sound of a joke flying over your head.

 Right.

Fyi, this is The Daily WTF, not The Daily Lame Joke. Yes, this is the side bar, but it is still expected to be WTF-related.

Because more things make us ask WTF than just code

 TRWTF is that you don't realise this forum is serious business, not a big truck that you just dump things on.

@Nitehawk said:

A while back our office put up a bunch of crappy motivational posters, warning us about security. They all had horrific art on them and were promptly removed.

 My favorite one read:

"Beware of Social Engineers."

Hmm, I am a Software Engineers. I like to hang out and go to the bar after work. I like hanging out with the cool people from work. I feel that I am friendly and well liked around the office.

 Aparently they should beware of me.

TRWTF is that you think that social engineering = software engineering.

@f4c4d3 said:

Interesting. Got this while trying to post a different WTF.

TRWTF is that it isn't a WTF.

 TRWTF is hiring a woman to do a man's job.

 @MasterPlanSoftware said:

If you have applications written in VB6, you should be porting them to VB.NET. That is all there is to it.

I really don't see why it's necessary to spend hundreds of man hours porting/refactoring code just to get it to compile cleanly under VB.NET when it works perfectly with VB6. When a solution already perfectly fits a problem, there is no "advantage" in spending that much developer time to only make it work as well as before...

On the other hand, "new" applications should be written in VB.NET.

 No surprises there.

@MasterPlanSoftware said:

it sounds like you are using them for a fixed range of dates which might even be more of a WTF

You really fell right into that one.

@bjolling said:

@silenceisdefeat said:

@bjolling said:

@silenceisdefeat said:

@Jake Grey said:

VB.NET isn't universally regarded as an improvement anyway

 

Define "improvement". The only real disadvantage with VB.NET is that it isn't backwards compatible (but that's also an improvement in some ways).

 

Oh my God!

Please don't talk about things you obviously have no clue about.

 

 

Oh my God!

Starting posts like that is the perfect way to be taken seriously.

 

I had no intention of being taken seriously on this one. But after re-reading your post, I see that I should only have quoted Jake Grey.

Still, you seem to underestimate the big improvements that have been made

 

Oh my God!

I LOVE nested quotes btw.

Big improvements eh? Like being unable to make an array that goes from 1900 to 2050?

Hold on a second, that's not an improvement!

@bjolling said:

@silenceisdefeat said:

@Jake Grey said:

VB.NET isn't universally regarded as an improvement anyway

 

Define "improvement". The only real disadvantage with VB.NET is that it isn't backwards compatible (but that's also an improvement in some ways).

 

Oh my God!

Please don't talk about things you obviously have no clue about.

Oh my God!

Starting posts like that is the perfect way to be taken seriously.