What is FTW?

FTW is an Internet slang that stands for "For The Win".

It is usually added at the end of a message or a post to show enthusiasm on the subject.

USAGE

Guy1: Have you seen the new iMac?
Guy2: new iMac FTW!

Guy1 asked if anyone has seen the new iMac, Guy2 reaffirmed this. Whether or not the response of Guy2 was genuine or sarcastic depends on how we interpet it.

On the other hand, FTL - which is the exact opposite of FTW - stands for "For the Lose".

Starcraft Jargons

These are Starcraft jargons that originated from (where else) South Korea, also known as Starcraft country. So memorize these jargons just in time for Starcraft II.

kekeke = laugh
babo = stupid
^^ = :)

Gosu = master
Hasu = average
Chobo = noob
HUK = OMG

HUK U BABO CHOBO KEKEKEKE ^^

*courtesy of Slashdot.

What is IANAL?

You have probably seen this acronym across technology-related websites or blogs, and turned-off by it. Who wouldn't? It denotes a bad meaning. But don't worry, pinoytechie is here to explain the real meaning of IANAL.

IANAL is an acronym which stands for "I Am Not A Lawyer". The use of this abbreviation serves as a warning for the reader not to take the opinion as professional legal advice. [wikipedia] The expression became more and more common on online web forums starting from the year 2000, when debate about file sharing and peer-to-peer applications started to focus on copyright, privacy, and fair use issues. [wikipedia]

USAGE

An example commentary on peer-to-peer applications.

Reader1: If ever I will upload a file on rapidshare.com, will I get sued?
Reader2: IANAL, but if the file is a copyrighted one, I think you will get sued.

Reader1 should not take seriously the words coming from Reader2, because as Reader2 clarified, he is in no position to say legal things rather he is just stating his own personal opinion.

What is YAGNI?

This is generally a software engineering term that stands You Ain't Gonna Need It.

Basically in software development a programmer should never create a "generalize" module for the sake of generalization, adding complexity to things that will probable never exist. This usually happens when a programmer over thinks too much about code reuse should be advocated in every modules he will create.

A best advice usually given is keeping all modules in the simplest state as possible. And adding new features as needed so that modules might not lead to code bloat.