Lesson 8. Conclusion.
Prev || Home || Next
In short, the devices behind writing a virus are not all
that complicated. There are many checks to counterattack, and part of the puzzle itself is
no find new ways to get around them. Find back doors. Give the code a personality. Make it
try to find the best way around a counterattack if it is able to detect one. Size is no
longer a constraint in today's memory-hog world. A virus of near 50k would probably go
undetected in modern-day storage, so don't feel constrained in that way. Time should be a
Make code that is efficient, so that users don't notice a slowdown when it is executed. All in all, your code is your work. Don't let it out of the bag until it works well and clean, and don't forget to leave no trace.