一般解决问题的程序 [英] procedure to solve the issue generally

问题描述

我是一个新兴的开发人员，任务分配时我经常遇到问题，通常我是从我的逻辑开始的，后来我认为在某个阶段或高层提出了想法，然后我意识到这不是解决问题的更好的逻辑或更好的过程我遵循了.
我很担心.....

因此，我想问的小组是什么时候分配任务的，那么您通常会遵循什么步骤?

hi group,


i am a new in development,i faced problem many times when the task assign,generally i started by my logic,later i thought in some stage or senior gave idea then i realize that was not the better logic or better procedure to solve the issue which i followed.
i am worry about.....

so group i want to ask when a task assigned then what procedure you follow in generally & in system wise too.

推荐答案

让我给您一个想法-从不同的角度来看. 我最了解的大多数成功项目都写过两次.

现在，每个人都在谈论代码重用，尤其是负责项目截止日期和团队工作时间使用的经理.人们普遍认为，重写项目只是浪费时间.这是最愚蠢的现代趋势之一.人们假装第一个版本将足够成熟以投放市场，而不是将该项目的第一个版本用作可以工作的原型，而该模型通常对于学习该领域和技术非常有用，并且为第二个版本中的成熟项目制定了明确的计划，所以人们却假装第一个版本将足够成熟以上市. .这种幻想的结果是该项目的巨额成本:一次"完成，但是改进"而不会日趋成熟.

尽可能彻底地规划您的逻辑和体系结构，但是……根据您的经验和学习到的错误，不要害怕重新开始.大多数人和团队无法将所有事情都放在第一位，所以要现实一些.

—SA

Let me give you one idea — from a different stand point. Most successful projects I knew well were written twice.

Now everyone talks about code reuse, especially managers responsible for project deadlines and use of team working time. There is common vision that re-writing of the project is just a waste of time. This is one of the most stupid modern trends. Instead of having first version of the project to be used as a working prototype mostly useful to learn the field and techniques and crystallize a plan for a mature project in its second version, people pretend that a first version will be mature enough to go to market. The result of this delusion is enormous cost of the project: it is done "once" but is being "improved" without maturing — ever.

Plan your logic and architecture as thoroughly as possible but… Don''t be afraid to start over, based on your experience and learning your mistakes. Most people and teams cannot design everything in advance in first place, so be realistic.

—SA

自信并编写自己的逻辑.获得解决方案.
要求您的前辈间歇性地检查您的逻辑/解决方案，以便他们指出任何可能出错或未优化的内容.这将是学习新的更好方法来解决问题的最佳方法之一.

Be confident and write your own logic. Get a solution working.
Request your seniors to review your logic / solution intermittently so that they can point out anything that may be wrong or not optimized. This would be one of the best ways to learn new and better approaches to solve problems.

开发中的一件事是没有完美的方法"进行编码.一切都取决于每个开发人员如何编写代码.这些都是有用的东西，最终确实会产生巨大的变化:

1.了解功能要求或了解为什么突然弹出错误.
2.像其他人所说的那样，要有充分准备的逻辑流程并要有信心.了解每次都有总有改进的空间.
3.千万不要错过单元测试.有时这对您可能是一个很大的福音.完美的发行版要花费一天的时间，要比包含许多错误的早期发行版更好.
4.始终坚持要求上司进行代码审查.这不仅可以在发生问题之前指出错误，还可以通过上司提示的一些技巧从中学到很多！

祝你好运！

One thing in development is that there is no "perfect way" to code. Everything depends on how each developer does his job in writing code. These are some helpful stuff which indeed make a huge difference in the end:

1. Understand the requirements of a feature or understand why a bug has suddenly popped up.
2. Like others said, have a well prepared logical flow and be confident. Understand that there is always room for improvement everytime.
3. Never miss out on Unit Testing. This can be a great boon to you sometimes. A perfect release which took a day longer is better than an early release with many bugs.
4. Always insist on a code review from your superiors. Not only does this point out something wrong before it happens, you can also learn a great deal from this through some techniques hinted by your superiors!

Good Luck!

这篇关于一般解决问题的程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！