# Development is iterative ## The path isn't curvy, it's circular. Development follows a path, but is, at the core, an iterative process. It almost never happens that a developer gets something perfectly right the first time they do it. Development is testing and testing is development. This is a misconception I’ve seen many times over the years. Clients think that testing can be skipped or skimped on, but it is a part of the development process and any cutting back on this means that the system will be incomplete. Additionally, the improvement of systems is iterative. The best set of features that can be built within the given amount of time is built, promoted, sold, and then reviewed for customer feedback and iterated on in the next release. For more information on the general process, [take a look at the chapter on Continuous Integration.](/saas-build-process/steps-to-developing-a-saas/continuous-integration.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.howtokicksaas.com/saas-build-process/things-to-know-and-expect/development-is-iterative.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.