CODING LAWS
(C) KRUGER/Delirium Tremens
__________________________________________
1.Assembly speed is reverse
proportional to the number of bells and whistles in the inter-
assembler face.
2.The degree of optimization is inversely proportional
depending on the memory capacity of your computer.
3.The program can only be optimized
by speed or volume, and never one
temporarily.
4.The most dangerous glitch is detected only
after you have completely packed and
screw up your program.
5.The most perfect way to remove ba-
gov -their description in the file ReadMe.txt
Consequence: a text editor is the most
perfect debugger.
6.Probability of glitches that kill
assembler, as well as the probability of disabling
the value of electricity depends on how
It's been a long time since you saved the source.
Output: unsaved source overloaded
there is an electrical network.
7.If you decide to debug the program and
this did not save the source, thenSTSusually
sometimes it's not loaded.
8.Probability of damage to the zero track during
protected disk is directly proportional to its
cost.
9.Free programs -are buggy.
10.All you have to do is "lose" the necessary pro-
gram, as all your friends wash it from
yourself from the disks.
Addition: when you do buy it, that's it.
your friends will call you and tell you that they can
let you copy it.
11.The most interesting articles in electronic
magazines copied by Ignore...
Consequence:if the magazine is fully operational,
that means there is nothing to read there.
12.Programs that everyone should have, none
who doesn't.
13.Time spent on writing
grams refers to the time spent
to debug this program as 1:3.
14.Never write a file HELP.txt for
of your program. Doesn't matterno one
will read.
15.The most necessary and lengthy procedures are yes
are stored in logs that do not have a save function.
understanding of the text.
16.Assemblers that do not have the IMPORT function,
usually get to you without a con-program
vertora.
17.Writing a program usually takes
300% of the planned time.
18.Addition: when trying to write
readable source - 600%
19.Disable the program by
less one bug than another.
Addition:at the same time destructive
properties of the new bug compared to the old one
the eye is doubled. Consequence: the most efficient are
There are versions that have not undergone glitching.
20.Your processor always has less
tov than this program requires.
21.The number of glitches is growing geometrically
sky progression as they are discovered.
22.Lamers don't have glitches - it's theirs
writing style.
23.The length of the source is directly proportional
the cost of a bottle of beer.
24.All demo-party have hidden part.
25.The stupidest programs are written at the top
coding skills.
26.The coolest demos on your computer
they won't go.
27.Disks with source files "die"before
total.
28.Having removed all the glitches from your program,
you will definitely miss the most important one.
29.The scarcest microcircuit burns out
first.
30.If you have lost the receipt from the box with the dis-
kami, then they will definitely turn out to be defective
nym.
Explanation: if the disks turned out to be normal
No, look in your pockets for the receipt.
31.The procedure that you need at this time
moment in the library is usually absent.
Consequence: once you write it, itthere will be.
32.Power surges turn on the drive
only in format mode.
33.The modem always breaks down at the moment when
where you are almost finished downloading the file.
It is worth rebooting the computer, as it is installed -
the swarm miraculously begins to function
nirate.
34.If the magazine consists of two disks -
one with texts, and the other with an application, and
you don’t have a second disk, then rest assured -
all texts on the first one are devoted to programs
on the second.
35.Coding is dangerous not only for your
health, but also for social status.
36.If you don’t know how to remove the glitch,
leave everything as it is.
37.All errors in the source are detected
after all INCLUD'son the second pass.
38.The difference between tokenized and non-tokenized
kenized assembler is usually absent
exists.
39.The KEMPSTON detector always gives a
living result, regardless of availability
you have this device.
40.Programs without an interrupt table are pre-
property goes to owners of cars with
unstable vector.
41.90% of your disks are full of software that
you don't use it.
42.It’s worth formatting these disks,”kill
You will need these programs.
43.The number of lamers sitting on this
type of computer is directly proportional topopularity of the platform.
44.The degree of optimization is in no way
depends on the time spent on it.
Tip:don't waste your time.
45.Mark names tend to be forgotten-
Xia.
Addition:if you write them on a hard drive
smear, then it will be lost.
46.You can protect the program from hacking to no avail.
limbs, trying to protect themselves from hacking
mu protection.
47.If you write a program in assembly language,
never make transitions along JR - that's all
it will still have to be forwarded.
48.All of the above is crap.
Consequence: you're in deep shit.
49.All lamers are bastards.
50.I'm not a lamer, I'm worse.
Review of everything ancient
sux'n'shit'a...
Share your thoughts about the article