Как писать быдлокод

ъ?

Introduction

Never ascribe to malice, that which can be explained by incompetence.
- Napoleon

In the interests of creating employment opportunities in the Java programming field, I am passing on these tips from the masters on how to write code that is so difficult to maintain, that the people who come after you will take years to make even the simplest changes. Further, if you follow all these rules religiously, you will even guarantee yourself a lifetime of employment, since no one but you has a hope in hell of maintaining the code. Then again, if you followed all these rules religiously, even you wouldn't be able to maintain the code!

You don't want to overdo this. Your code should not look hopelessly unmaintainable, just be that way. Otherwise it stands the risk of being rewritten or refactored.
General Principles

Quidquid latine dictum sit, altum sonatur.
- Whatever is said in Latin sounds profound.

To foil the maintenance programmer, you have to understand how he thinks. He has your giant program. He has no time to read it all, much less understand it. He wants to rapidly find the place to make his change, make it and get out and have no unexpected side effec

Учитесь...

// Нахождение последнего элемета массива:

for ($i = 0; $i < count($arr); $i++) {
    $res = $arr[$i];
}

echo($res);

моск лопнул О_О

fixed.

>>// Нахождение последнего элемета массива:

Зато потом можно еще будет требовать доплату за оптимизацию. Вы не шарите, короче.

Хм.job security в данный момент времени не помешает :)