# Portfolio Programming Etiquette

If you want to make your software available on future 3DO hardware using future versions of the 3DO operating system, follow the advice in this chapter. If you follow the guidelines discussed below, your application will continue to run as the 3DO platform evolves.

Caution: Any application that doesn't follow all of these guidelines may break in the near future.

This chapter contains the following topics:

- Accessing Low Memory
- Making Assumptions About Memory Types
- Relying on Side Effects of Multitasking
- Using Busy Waiting
- Ignoring variable frame rates
- Using fixed pathnames
- Using Self-Modifying Code
- Leaving unused fields in DMA structures uninitialized
- Bypassing the API
- Hoarding System Resources