“Quality must be enforced, otherwise it won’t happen. We programmers must be required to write tests, otherwise we won’t do it.”
Yegor Bugayenko, Code Ahead: Volume 1
WHY BEST PRACTICES ?
What happened if you don’t follow best practices?
Well , Even world wold III can be begun if it is a Defence project.And there are many disadvantages including
- Low project , product , software quality
- Unacceptable performance
- Hard to maintain or extend
- Inaccurate understanding of end user needs
- Unable to deal with changing requirements
- Late discovery of serious Development flaws
What are the root causes of poor software development?
- Insufficient communication between developers and other members
- Overwhelming complexity
- Insufficient and poor testing
- Insufficient requirements management
What are the best practices in software engineering?
SIMPLICITY
Every application should be simple but complex enough to the exact task.Any application should be created in the most efficient way without unnecessary complexity. Simple answers are the best even for complex questions and usually correct , and this thought perfectly meets the requirements of the development process.
YAGNI – You aren’t gonna need it
Don’t write code that you think you may need in future, but don’t need yet. Coding for imaginary future use cases is not right , and inevitably the code will become wasted code or need rewriting because the future use case can turns out to work differently from how you think or imagined it.
COHERENCE
Teamwork is very important for big projects and it’s impossible without a high level of consistency. Code coherence stands for the creation to a common writing style for all developers who develop software. This will allow other developers to tell who the author of a given code is. Yes, when the code has the same style, it’s coherent.
Consistency helps a lot because testers will be able to test, edit or continue the work of each other. Vice versa, inharmonious projects can cause many troubles for your team and slow down the development process and it will cost more for the project.
DO NOT REPEAT YOURSELF
Keep in mind that do not repeat yourself i repeat do not repeat your self.Always try to write reusable codes and try to use them after
MANAGE REQUIREMENTS
Most of the clients are not aware what they really need and how technology can help them to achieve what really need. so getting the right requirements is hard. sometimes user requirements can be evolve in the middle of development so managing requirements is good practice to follow.
TESTING
Testing is very important for any software and on any stage. From the very first test run to the final evaluations, developing team should always test the product.
nowadays software engineers have access to powerful tools such as automated tools to run millions of tests each second. crucial thinking helps when developers have to choose a testing type: functional, performance, integration or unit. If developers choose the tools and testing types carefully, developers can find bugs and others issues that can ideally be removed out before the deployment of the product.
MAINTENANCE
Unlike physical products, the software has the potential to be immortal. This would only be possible with maintenance including regular updates, more tests and analysis. You’ve probably seen a warning before about an software that isn’t compatible you’re your device. Good maintenance can improve the performance of a software
This principle is a bit controversial as not all developers need to spend time on product compatibility with every hardware. However, developers should focus on maintaining code to allow software to work on wide range of devices as well as new devices. so, the product will meet the needs of more users and help old softwares to remain useful.
Computer Science and Software Engineering 
Leave a comment