The Ministry of Truth Rules for Good Software Design
•Download as PPTX, PDF•
1 like•641 views
A reworking of a lightning talk presentation first made by Allen Short at PyCon 2012.
Recommended
More Related Content
Similar to The Ministry of Truth Rules for Good Software Design
Similar to The Ministry of Truth Rules for Good Software Design (18)
Recently uploaded
Recently uploaded (20)
The Ministry of Truth Rules for Good Software Design
- 1. The Ministry of Truth Rules for Good Software Design
- 2. Principles of good software design are PRINCIPLES OF GOOD OBJECT DESIGN
- 3. War is Peace
- 4. Treat all inputs AS ATTACKS
- 6. A good interface IS NOT BROKEN BY BAD INPUT
- 7. throw { name: ”Bad Input Error”, message: ”Oh noes!” }
- 9. The more you constrain your code’s behaviour, THE MORE FREEDOM YOU HAVE TO ACT
- 10. run();
- 11. “There is only one mode, AND IT IS SECURE.”
- 13. Only give objects access to the THINGS THEY NEED TO DO THEIR JOBS
- 14. To write better objects… • Leave your object in a consistent state regardless of what your clients do. • Prevent clients from accessing things they aren't supposed to touch. • Only give your objects access to the resources they need to get the job done.
- 15. To write better programs… • Leave your program in a consistent state regardless of what your clients do. • Prevent clients from accessing things they aren't supposed to touch. • Only give your programs access to the resources they need to get the job done.
- 16. Thanks This lightning talk was originally by Allen Short and was presented at PyCon 2012
Editor's Notes
- Greetings from the Ministry of Truth. We would like to take this opportunity to educate you on some principles of secure software design.
- object/API/web service/module/plugin/extension/featureAnything with a public interface used by other code.
- If your code is prepared for war, you can be at peace.
- Treating all inputs as attacks protects all users.
- We all remember little Bobby Tables…Don’t let Bobby happen to you.
- A good object interface doesn't let bad input break it. Raise/throw exceptions.
- This is how you throw an exception in JavaScript. The object literal is key.
- Limit what can happen via your interface. The less choice a client has in how it interacts with your program, the more success you will have in securing it.
- The ideal secure interface looks like this.
- There should be one—and preferably only one—obvious way to do it.Adding features for convenience can constrain you later on. Lean development is better development.Do you have a requirement for it now? If not, don't code it.
- The less your code knows about the less it can break.
- Principle of least authority.Regardless of security, code cannot affect objects it doesn't know about. This means less bugs.This is why global variables are bad.Isolated code is easier to debug.