We could end up in the situation when we have to deal with problems without the ability to debug or know for sure what is going on. That’s why we need to base our development on the best practices and documentation for the language that we are using, and avoid common mistakes.Īs mentioned, when software goes live, things could go wrong, and code could start executing in a way we didn’t plan. Most of the times we have to deal with potential problems in a theoretical scenario: we know that a problem can happen, but we can not test it. Software performance in production is hard to analyze. In described and safe situations our code will work fine, but in production under heavy load or some other external factors, unexpected problems could occur. In these cases, we also don’t have to deal with heavy loads of the server, or concurrent users trying to do the same thing at the same time. In these situations, we have at our disposal tools for analyzing different variables that are affecting our code and software.
SCIDA COURSE FULL
An example is our development machine, or an integration environment which we have full access to. Given this reality, things usually go as planned when we work in controlled environments.
NET developers are no exception to this. Some are not under our control, some are unknown to us in the moment of the actual code execution, and some are directly controlled by us. We as developers need to take a lot of different variables into account.
Software development can be a very complicated process.
0 kommentar(er)
