Task Solution: Yes, my feature request relates to the problem because, code has many review loops which take a lot of time, since we don't work full time. Waiting for feedback or comments to come in and not being able to work on the code in time, is/can be a huge problem, impacting to productivity and satisfaction of the whole framework. The solution I would like is; We should have a code analysis which not only get the number of issues in the code, but also where they are located in our code. With this, we will be able to get suggested solutions for each issue found in the code. It's helpful for us to quickly fix the issues and move ahead/forward. The alternative I consider is; We should come up with something that will help us to get to know ideally, how much time should it take to fix the bugs. With this we can be able to plan our code review process and correction periods/time accurately. Hope it helps. Thanks.
Task Solution: The code is amazing, it helps us be ahead of others through the service you deliver. We are rewarded as per your promise, thus encouraging us users to stick by it and collaborate in every motter arising. Above all the goods about the code, I also got a suggestion. Other frameworks measure their code's size in a consistent and structured way, most instead rely on subjective approaches to provide comparison and context. Since sizing does not have to be complex, I would suggest we increase the size of the code, to reduce the risk of system failure. How to tackle this; we should first know the size of the code, in order to provide effective metrics, improve estimation, target improvement initiatives and refine governance and the architectural processes. By doing all these, we will be able to come up with a suitable size for our code. Thanks.
Awesome
Email: je**08@gmail.com
Task Selection: Task 2: Finmail Add-in Code Review
Task Solution: Yes, my feature request relates to the problem because, code has many review loops which take a lot of time, since we don't work full time. Waiting for feedback or comments to come in and not being able to work on the code in time, is/can be a huge problem, impacting to productivity and satisfaction of the whole framework. The solution I would like is; We should have a code analysis which not only get the number of issues in the code, but also where they are located in our code. With this, we will be able to get suggested solutions for each issue found in the code. It's helpful for us to quickly fix the issues and move ahead/forward. The alternative I consider is; We should come up with something that will help us to get to know ideally, how much time should it take to fix the bugs. With this we can be able to plan our code review process and correction periods/time accurately. Hope it helps. Thanks.
Email: je**08@gmail.com
Task Selection: Task 2: Finmail Add-in Code Review
Task Solution: The code is amazing, it helps us be ahead of others through the service you deliver. We are rewarded as per your promise, thus encouraging us users to stick by it and collaborate in every motter arising. Above all the goods about the code, I also got a suggestion. Other frameworks measure their code's size in a consistent and structured way, most instead rely on subjective approaches to provide comparison and context. Since sizing does not have to be complex, I would suggest we increase the size of the code, to reduce the risk of system failure. How to tackle this; we should first know the size of the code, in order to provide effective metrics, improve estimation, target improvement initiatives and refine governance and the architectural processes. By doing all these, we will be able to come up with a suitable size for our code. Thanks.
Email: am**01@gmail.com
Task Selection: Task 2: Finmail Add-in Code Review
Task Solution: Please specify the meaning of the Add-in Code because there are some people who did not really understand it clearly.
Email: cr**st@gmail.com
Task Selection: -
Task Solution: Task 2: Code Review
File Upload Field: