Rather than thinking of these steps as a strict sequence, one should think of them as parallel processes with shifting resource allocations. Ultimately, the de

Rather than thinking of these steps as a strict sequence, one should think of them as parallel processes with shifting resource allocations. Ultimately, the development process comes down to the experience and habits of the developer. If you have a lot of experience, your marginal cost of "getting it right" from the beginning is lower, because you already have the necessary domain expertise. For example, if you're inexperienced, you might build a login system that simply stores plain text with a note to "hash passwords" later. You might then move through unsalted via manually salted hashing to finally arrive at something like bcrypt.