Oh yes, they're hilarious. Especially since there is actually some genuine "motivation art" to be found at my current workplace.
I like this one best though:
brazzy
@brazzy
Best posts made by brazzy
-
RE: Art of Demotivation posters
-
RE: Overheard in the next cube
@zamies said:
Well that depends I think wether its a local
variable or an instance variable. At least if my memory doesn't fail to
serve me.
Local variables aren't initialized on declaration, but is unassigned a value?
If it's a java.lang.Boolean, then like all reference variables, it's
initialized to null. If it's a boolean primitive, it's initialized to
false, and there is no "unassigned" state, only true and false.
This is for class and instance variables. If you don't initialize a
local variable before using it, the compiler will reject the code.
Another area where booleans have an "unassigned" state would be DBs.
-
RE: Favorite Anti-Pattern
Mine would have to be the "GoF love affair". It occurs when someone has just discovered design patterns, read the book, and thinks they're the greatest thing since sliced bread.
For a while (often a long, long while) someone affliced by this will never write a dozen lines of code without thinking "where can I use a pattern here?". The probably worst cases are those in love with a specific pattern that gets used everywhere. Often Singleton.
-
RE: The "I hate Java club"?
@Cyresse said:
I personally can't stand Java.
I don't like the following
<font face="Arial">- Static typing...
- ...On methods
- Throws x exception handling
- Interfaces
- Lack of multiple inheritance
- Huge, clunky on load JVM
- Incompatible JVM's
- 15 classes, 15 files
- A class involved in "Hello World"
- BufferedStreamReader reader = new BufferedStreamReader(new InputStreamReader(con.getInputStream())); to read from console
- Gets & Sets
</font>
Based on such wonderful arguments, it's just as easy to "prove" that relative to Java, Python stinks (What kind of sick mind does it take to come up with syntactically relevant whitespace??). About a third of your points above is valid, the rest is a mix of laughable details, and good things of Java. Basically, you're just saying "I hate Java because it's not Python".
-
RE: The "I hate Java club"?
@Savior said:
Man, forget these people. They can't keep a conversation without having
to bitch and rant about this or that. And now, you should have also
learned that they can't understand other's points...
pot... kettle... black...
@Savior said:
Just look at the initial post:
"Since we have the I hate Oracle club, I was thinking, doesn't Java should have this "privilege" too? "
And now, read the replies...
Yes, please do so. You will notice that all replies were calm and civil
objections to having another pointless language flamewar.
Then, in your second post, you said "I'm not willing to start a flame
war", but did exactly that with a plethora of stupid and wrong strawman
arguments. For example:
@Savior said:
Oh, wait, but you can deploy once, run EVERYWHERE! See? Oh, no, wait,
this java application requires the JRE 1.4.1, and will not run you
yours, since it's 1.4.0. All you have to do is download a new 60 MB
runtime.
First, the 1.5 runtime (latest and biggest) is 15 MB. Second, if an app
runs on 1.4.1 but not 1.4.0, it either depends critically on a bugfix
in 1.4.1, which is commonplace in current applications in ANY language.
Or the programmers were incompetent. Most likely, it would run just
fine in any 1.4 or 1.5 VM and the maker was just too lazy to test on
more than one VM or let users try a different VM, which might generate
more bug reports.
In the past 3 years, I've worked on two very big Java apps, and encountered a whopping total of THREE VM-version-related bugs.
As for Mr. Westhauser, he's so full of shit it's almost funny:
OO taken to the utmost stupidity. I mean such convoluted garbage as: String s = new String("java sucks"); And that's the beginning!
That's convoluted garbage indeed, since it's unnecessary and most Java books will tell you NOT to do that since String s = "java rules"; works without creating an extra String object.
Considering that you started this thread and then turned it into a flamewar when nobody else did, it looks to me like you're simply a troll.
-
RE: Brillant is her name.
@murphyman said:
I for one have been glad to see the
'Brillant!11!!' comments slowly disappearing from the forums. Am I the
only one to smell the nasty whiff of sexism about the whole thing? I
mean, her case doesn't even come close to the worst WTFery we've seen
on these boards, yet she is easily the most referred to, the most
quoted, and the most mocked.
Her only mistake was to get a job typically the reserve of men, and not take it seriously. Big deal.
Umm... no. The gender of the person in question had NOTHING to do with
it. It would have been exactly as WTF-worthy and exactly as
well-remembered if a male programmer had, after 3 months work, nothing
more to show for it than a Hello World program in which he called
himself brilliant... and misspelled it.
Latest posts made by brazzy
-
RE: Project Managers
Sounds like the projects are simply set up wrong. Why is the project manager provided by the client in the first place? Legal requirements? Corporate politics? Or just because "that's the way we've always done it"?
The actual project manager should be someone in your company who knows how IT development projects work. The person on the client side should just be a customer representative; they can sill be formally the superior of the project manager if necessary. It is then the project manager's responsibility (amongst other things) to make sure that person delivers the required input and teach them what they can and cannot expect from an IT development project. You may still have to deal with their technical illiteracy, but their job is not to be technical, their job is to provide domain knowledge, requirements and feedback.
-
RE: Opinions Requested
@Voidpointer said:
Chip datasheets would undoubtedly have this information, or enough information for you to calculate it. It would depend on a ton of factors though (DRAM? access speed/frequency? rewriting huge blocks? etc), the RAM simply being full isn't what causes power consumption. In fact, RAM "at rest" (be it full or empty) probably uses very close to 0W.
Actually, DRAM (which is pretty much the only kind used for main memory nowadays) constantly uses power to "refresh" its contents, which would otherwise get lost - this typically happens a dozen or more times a second. However, I don't know whether that power usage is significant compared to the CPU (probably not, since RAM modules are typically not actively cooled) and whether it's actually possible to save that power by not refreshing unused RAM blocks where you don't care about the contents getting lost.
-
RE: Password storage system
@NullAndVoid said:
A quick search for "password manager" came up with several possibilities, but I've never used them so I can't recommend any in particular. However, I'm curious: If you're going to consolidate all passwords in one place (presumably all recoverable by a single password), wouldn't it be just as secure to use that same password on all of the systems?
Some systems have mutually contradicting requirements for passwords (e.g. one requires a mix of exactly 8 numbers, upper- and lowercase letters, another only accepts letters but requires at least 10). Some systems require you to change the password regularly. And most importantly (if it's for general use rather than just company-internal systems): do you really want the owner of any dinky web forum you use to know your online banking password?
-
RE: ASP.NET: Singletons
@morbiuswilters said:
@brazzy said:
Ouch. Singleton is the object oriented version of a global variable, and usually exactly as bad. There are very few problems for which Singleton is the correct solution.
Except it is much easier to add debuging and lazy instantiation to a singleton method. Global variables and singletons are fine, the problem is with using them carelessly. Seriously, how would you handle a globally-needed resource?
The problem is that many developers don't really consider whether a resource truely needs to be globally accessible (IMO very few), or could just as well be passed as a parameter or added to an object that is. Instead of taking the time to think it through and do it the right way (which may require some refactoring), they'll just create the 137th Singleton, until every other line contains at least one getInstance() call.
"throwing Singletons around like there is no tomorrow", as the OP put it, sounds exactly like that case.
-
RE: ASP.NET: Singletons
@Ice^^Heat said:
Lately, I have been throwing Singletons around like there is no tomorrow (hey why use all that memory?? Just make a singleton!).
Ouch. Singleton is the object oriented version of a global variable, and usually exactly as bad. There are very few problems for which Singleton is the correct solution.
-
RE: Understanding HTML
@aristos_achaion said:
There's an inherent security issue with allowing an unknown, untrusted site to execute code on your machine. Granted, it's not like this is as huge an issue as some people make it
Wrong, this is actually a VERY huge issue in an age when an increasing number of people do an increasingly large part of their financial transactions online. Learn more here.
-
RE: A relational database? What's that?
@flaxeater said:
@rel said:
That makes it look like you think that the ability to declare relationships between tables is why we call it the relational model. But that's not why it's called the relational model, nor why we refer to implementations as "relational databases".
Because your not coming right out and saying it. Your refering to relational algebra in comparison to what a relational database is right?
You don't really need to go that far. A relational databse is called that because each table forms a relation (in the mathematically defined sense of a set of n-tuples). This is different from the older hierarchical databases. Of course, in this sense, a collection of flat files is a relational database as well...
-
RE: Six sigma WTF?
@upsidedowncreature said:
By the way, why can't we have cool green/yellow/black belts in software development? I mean, real belts?
You mean, like like this?
-
RE: String conversion is fun!
@danixdefcon5 said:
I think it'll work out ... as long as you don't use accents, umlauts... oh well, anything that you might encounter with non-English languages. Oops!
Even then it can fail with the rare non-ASCII-compatible encoding like EBCDIC.
OTOH it can (and did) work when the hardcoded encoding, Javas platform default encoding AND the one actually used by the XML data just happen to be identical. Quite a feat - most naive string conversion code just fails when the data's encoding doesn't match the platform default.
-
String conversion is fun!
Recently found this deep in the code that processes XML data from the backend. And they were wondering why their umlauts got garbled... can you count the WTFs and especially the number of completely uneccesary and potentially destructive byte[]/String conversions? Anyone care to explain how someone who's apparently aware of the concept of string encodings could produce this code?
public boolean setContent(byte[] xml)
{
boolean retVal = false;
if(xml != null)
{
this.keys.clear();
SAXBuilder builder = new SAXBuilder();
builder.setValidation(false);
try
{
String strEncoded = new String(xml,encoding);
retVal = this.setContent(strEncoded);;
}
catch (UnsupportedEncodingException e)
{
SystemProperties.getLogger().logException(getClass(), "Wrong Encoding", e);
retVal = false;
}
}
return retVal;
}
public boolean setContent(String xml)
{
boolean retVal = false;
if(xml != null)
{
this.keys.clear();
SAXBuilder builder = new SAXBuilder();
builder.setValidation(false);
try
{
document = builder.build(
new InputSource(
new StringReader(
new String(xml.getBytes(),encoding))));
} catch (JDOMException e)
{
retVal = false;
} catch (IOException e)
{
SystemProperties.getLogger().logException(getClass(), "Cannot create JDOM document", e);
retVal = false;
}
initMap();
}
return retVal;
}