Programming Security
You have to be careful how you expose your coding objects to the outside world.
Global variables are a great example of bad programming. Global functions too.
Generally it is bad to expose the inner workings of your objects. Bad in the full sense of the word.
Ideally, each piece of code should be encapsulated in its own locked box, built of titanium no less than 800 millimetres thick, and buried beneath the ocean floor at its deepest point, at least twelve kilometres from breathable air. It is still possible that subterannean creatures could evolve the ability to withstand the intense presure at such depths, and find ways of penetrating the box and modifying the value of your internal variables. Wiring the titanium box with a nuclear warhead is thus considered best practice.
Add or view comments about this page
|
Articles
Just Wally
The Correct Order for a First Time Viewing of The Lord Of The Rings
A new era for Android.
Mind-boggling Demo of New Gaming Genre, aka Folder-Based Hangman, aka Fun with Recursion
Got CSV in your javascript? Use agnes.
Complete secretGeek Archives
TimeSnapper: automatic screenshot journal
NimbleText: Code Generator, Text Manipulator, Data Extractor
25 steps for building a Micro-ISV
3 Minute Guide Series
Universal Troubleshooting Checklist
Top 10 SecretGeek articles
ShinyPower Now at CodePlex
RealTime Online CSS Editor
Gradient Maker
How to be depressed
You are not inadequate.
Recommended Reading
 the little schemer
The Best Software Writing I
The Business Of Software (Eric Sink)
Recommended blogs
Jeff Atwood
Joseph Cooney
Phil Haack
Scott Hanselman
Julia Lerman
Rhys Parry
Joel Pobar
Thomas White
OJ Reeves
Eric Sink
Aggregated Links
proggit
dzone
hacker news
dot net kicks
Human Link Machines
interesting finds
a continuous learner's weblog
arjan's world
weekly link post
LogEnvy - event logs made sexy
Computer, Unlocked. A rapid computer customization resource
PhysioTec, Brisbane Specialist Physiotherapy & Pilates
|
|
|