- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- 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
Mouth, nostrils, eyes, ears, urethra, anus, belly-button, nipples and sweatglands - where's the problem?
Admin
These and a couple of the successors caused me to LOL.
But I really think it would be better as a possible infinite loop:
Admin
Admin
WPF still does a whole lot that Silverlight cannot, especially in reguards to 3D capabilities, among other things. They are slowling taking the best new features of each and putting them into the other so I do see a merger at some point. In the mean time, you can multi target both Silverlight and WPF using many framerowrks out there and if you are smart about how you manage your assemblies.
There was some people over-reading into Microsoft's lack of mentioning .Net support in the next version of Windows at a specific conference. That focus of that conference was at casual developers, not professional developers. You can use HTML and Javascript to create gadgets in Windows Vista and 7 now, so I do not see why people are running scared. There is a reason Windows phone apps are based in Silverlight. I have also read rumors about WPF/Silverlight being heavily baked into the new UI for Windows, but we will see...Admin
Absolutely nothing, other than having hot fucking coffee coming out of anything other than the first two listed...
Admin
I don't know about you, but the last time I checked, my belly button was not an orifice since birth... now it's just some wrinkled "dimple" in my fat-bastard belly.
Admin
It is getting to be a useless metric in a lot of respects. I know pepople that have been using .Net for years and still can not write decent code.
Admin
Yeah, I totally agree about number of years != developer skills, but I do watch out for some red flags. Technical ability is great, but if they're going to lie to me before even starting, then show them the door.
Addendum (2011-06-15 16:06):
Yeah, I totally agree about number of years != developer skills, but I do watch out for some red flags. Technical ability is great, but if they're going to lie to me before even starting, then show them the door. I wouldn't, however, pass someone over if they claim on their resume that they have 5+ years of WPF, and it's only been our for 4.5 years. I tend to round "up" when it comes to experience as well... :)
Admin
Out of a cannon.
And into the sun.
Admin
Admin
Admin
Admin
Admin
'Multiple exclamation marks,' he went on, shaking his head, 'are a sure sign of a diseased mind.'
Admin
Hey! That's enough of that - this is a respectable place. We don't tolerate retards making fun of retards.
Admin
Admin
You're welcome.
Admin
[code] //Fixed too many Activates beign called occasionally /* This woz a troublsome bug that had everyone stumped
int numTimesCalled = 0; try { Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; Activate(); numTimesCalled++; } catch (Exception e) { switch(numTimesCalled) { // Note: We want this code to drop through - break statements are for wusses case 0: Activate(); // Note: We want this code to drop through - break statements are for wusses case 1:
// Note: We want this code to drop through - break statements are for wusses case 2: Activate(); // Note: We want this code to drop through - break statements are for wusses case 3: Activate(); // Note: We want this code to drop through - break statements are for wusses case 4: Activate(); // Note: We want this code to drop through - break statements are for wusses case 5: Activate(); // Note: We want this code to drop through - break statements are for wusses case 6: Activate(); // Note: We want this code to drop through - break statements are for wusses case 7: Activate(); // Note: We want this code to drop through - break statements are for wusses //Default: can't happen anyways coz I am brillant, do nothing default: }
}
Admin
Admin
Admin
EVERYBODY has missed the real WTF here.
An Enterprise Architect has NOTHING do do with IT, computers, software, et. al. The role of an EA is to define a strategy for the Enterprise as a whole. Some examples:
How should manufacturing (if applicable) be handled? Our own Factories? OutSourced
How should Financial Aspects be Structured?
How should Products (if applicable) be sold? Our own Stores? Franchises? Outlets?
etc. etc. etc.
Basically everything that makes the company what it is.
If all computers were to vanish tomorrow, the ROLE of an EA would not change. The viable options definately would, but the role itself would not.
So if you were hired as an EA..then perform that role. Research all aspects of the companies operations, do comparitive analysis of other relevent companies, markets, etc. When you have analyzed all of theis and have come up with a set of Strategic Initiatives, along with their risk/cost/benefit analysis and are ready to present them to the CEO for approval and execution. Then you are an EA.
(Of course it is much more likly that you were hired as an Applications/Software/Systems/Solutions Architect)
Admin
we were lucky this time.
This is our normal bugfixing - if something doesn't work repeat it. This has been through 3 fixes, and so far we believe we have the issue under control. When we get to 10 repetitions we consider using a loop. Once we're looping, we can increase the repetition rate quicker. If we ever get to a thousand repetitions, there is a small chance the issue is actually somewhere else, and we're only masking the problme...
captcha: bene - "Bene Grazie, e Lei?"
Admin
Uhm...then why didn't you say 3 - it would have taken less typing. Actually, "several" means "more than a couple" ie ("more than 2"), but implies a non-specific quantity (like "we didn't actually bother counting them, but it was more than 2") - if you want to specify an exact quantity, several probably ain't the right word....
several != 3 (although it may refer to it): *several == 3 sometimes.
Admin
Bah Humbug, they are much the same thing, except Several implies more than two, whereas few simply implies a small number - I am always amused when people try to quantify them, given that I would think their whole purpose is to avoid quantifying (I'm guessing the yankees {who as an old teacher used to remind me "never learnt to speak English properly" might say quantification or quantificating).
Some definitions, carefully chosen to support my thoughts:
Few –adjective 1. not many but more than one : Send me a few. –noun 2. ( used with a plural verb ) a small number or amount: Send me a few.
Several –adjective 1. being more than two but fewer than many in number or kind: several ways of doing it. –noun 6. several persons or things; a few; some.
Admin
We all know you're just a pedantic F*&k. I've had a solid 15+ years .Net experience - and that's just in the last 18 months....Before that, I was having 20+ years solid Java experience - and all before I'm 30!!
Admin
Apparently it is possible from the eyes....
Admin
WOW!!! I didn't know bikes can go backward that fast!!
Admin
I worked on a tool using Autodesk Maya and MEL scripting, and there was a particular operation that would get close each time you ran it, and so it actually took about three tries for it to actually work (or get close enough to be imperceptible to humans). Unfortunately that led to constructs JUST like this WTF.
Admin
Developers(); Developers(); Developers(); Developers(); Developers(); Developers(); Developers(); Developers();
Admin
Admin
Damn fucking convoluted logic. Who have coded it? I think i understood. 2 = few 3 = few 4 = few / several 5 = several 6 = many
Admin
TRWTF is consumption of diarrhoea. Mrs. Nagesh seriously needs some food hygiene training.
Admin
I haven't tested what happens with i> 10, so I don't know when Several stops and only Many continues....
Admin
Admin
Perhaps this is the developer who committed such horrid code. Looks like you put as much thought into your comments as your code....
Admin
Am I the only one seeing "activate()" thought "MAIN SCREEN TURN ON!"? Probably not.
Admin
Admin
Danger(); Danger(); Danger(); Danger(); WillRobinson();
Admin
lets google:
http://msdn.microsoft.com/en-us/library/system.windows.window.activate.aspx
Attempts to bring the window to the foreground and activates it.
But why 10 time?
Admin
Because we want to be sure, dammit!
Admin
Hahaha, omg.
Admin
Should have put it in an external function:
static int activeMult = 1; void doActivate(int n) { for(i=0;i++;i<(n*activeMult)) { activate(); } }
That way you can increase the multiplier as requirements change.
Admin
Reading comprehension fail? The function only "Attempts" to do it...
Admin
Without a comment why it is done eight times it is a WTF. If there is a reason but no comment giving the reason then it is an even bigger WTF than doing it with no reason at all.
Admin
If you are an Enterprise Architect, are you going to have them change the "Active" function to "Engage" ?
Admin
It doesn't loop because you waited 100ms, to give time for the enable() to take effect.
Of course, you might have only had to wait 50ms, or 20, or 70 - so some time has been wasted. But as another commenter has pointed out, it's someone else's time...
Admin
MakeItSo();
Admin
Number riker = new Integer(1); riker.makeItSo();
Admin
Several of you are missing the point. It's much easier if you quantify thus:
One Two Many Lots
Admin
Here's the Swing version (I've actually seen this in code-in-the-wild):
For the uninitiated, Swing events are processed sequentially on the SwingEventQueue. You have limited ability to manipulate items on the queue, but anything GUI-related (repainting) should be processed there. To put the item on the end of the queue, you use the utility method: SwingUtilities.invokeLater. What happens in the run method is what happens when that event is processed. What is going on above is: "When you get to my event, add another event to be processed when all the other events after me get processed." "WTF is the motivation!!!!!!!!" you ask? Developer in question was trying to solve some sort of timing issue. This is a (stupid) way to delay an event, hoping and praying it somehow happens at the right time.
(Yes, I know I used anonymous inner classes and didn't explain what they were. I'll leave that as an exercise for the curious).