@SamC said:
Oh, that is only but a taste. In addition to "datas", it was also spelled "data", "datea", "dates"…
- data_of_query()
- average_datea()
- assign_datea_new_value()
- read_datam()
- remove_datea_where()
Oh, wait, that’s wrong…
@SamC said:
Oh, that is only but a taste. In addition to "datas", it was also spelled "data", "datea", "dates"…
Oh, wait, that’s wrong…
@Planar said:
Sorry, you fail the Y10k compliance test.
This also recalls not so fond memories of a number truncation function that converted the number to a string, truncated the string before the decimal point, and back to a numeric type. Guess what happens if the conversion to string decides to use scientific notation. Guess who managed to do some other shit which ultimately caused said function to be called with something like 1e-9.
Shit, whenever you convert an object of arbitrary type T to string, manipulate the string, and convert back to T, you should, dunno, at least read the wikipedia page about that type before trying again.
@morbiuswilters said:
@m said:Hey, this sounds familiar! To mitigate the situation, I suggest using a distributed source control system, and have a repository in production; it really helps merging the code when deploying your changes. And never help a co-worker who can't tell with which revision of the software they has a problem :-)
DCVS isn't going to fix anything. I like DCVS but it doesn't stop people from doing retarded stuff like not testing before deploying. Also, even with DCVS nobody should be able to push directly from their repo into the production repo...
It doesn't fix the WTFish environment, but it is a handy tool for working in it.
I don’t expect C# as new employee to have the possibility to enforce proper testing and deploying procedures (mind they don't have time for such fancy stuff, they're putting out fires), but he has the possibility to automate merging changes from developement to production, and, …, back.
Hey, this sounds familiar! To mitigate the situation, I suggest using a distributed source control system, and have a repository in production; it really helps merging the code when deploying your changes. And never help a co-worker who can't tell with which revision of the software they has a problem :-)
@morbiuswilters said:
Unless i is being modified within the loop itself (which would be another big WTF)They were probably told not to use gotos.
@Rhywden said:
I'm not sure, but is there actually a language which does not require using a function to calculate something like 10x?
Visual Basic, of course.
Seriously, a lot: Ada, Algol, …, Zeno.
@morbiuswilters said:
What I love is that so many languages have stuck with this despite the fact that I am 14 times more likely to need exponentiation over bitwise operations.FTFY
@Weps said:
@JoeCool said:if ((strString.isEmpty()) || (strString == null))
Even without the warning this is a wtf...
#define strString strString == null) || (strString
Fixed?
@toon said:
Allow me to be the guy to quash that sparkle in the pips of your eyes: nobody sees that code but us (well, except for this line since tonight), and we're using standard English U.S. keyboards.
Well, then I’ll have to corect myself: I see no (0) possible reasons for having this variable.
@morbiuswilters said:
Is there any keyboard where underscores are not present but $, u and s are?
Maybe the US version of this Linotype keyboard? But for computer keyboards: there are standard layouts, so certainly hundrets of keyboards with non-standard layouts have been built. Why should keyboard design be less WTFy then any other branch of engineering?
Having found out that writing ° is unexpectedly difficult with english keyboards (or were it hungarian), I see one (1) possible reason for having this variable.
@The poop of DOOM said:
That's not the biggest issue here...
Yes, from the last column its obvious, that the real nazis need more grammar/spelling nazis in there online communities.
The sad thing about the telephone number colum is, that the numbers seem to get converted to scientific notation only if the customer cared enough to give the country code (but was to lazy to add spaces/punctuation).