实现功能与修复错误 [英] Implementing features vs. bug fixing

查看:146
本文介绍了实现功能与修复错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对与修正错误相比,实施新功能的日常工作时间有多少兴趣。

I am interested in how much of your daily work time do you spend on implementing new features compared to fixing bugs.

推荐答案

只要在我的软件中有一些不固定的错误,我不会编码任何新功能。

I don't code any new features as long as there are some unfixed bugs in my software.

我可以想到让我的软件中没有出现错误的唯一原因是修复它的代价绝对是昂贵的。在这种情况下,我们可能会选择将其从bug更改为已知限制或已知错误,并且我们会将相应的反馈修正给用户,以便用户准确了解发生了什么以及为什么不会固定(见下面的我的编辑)

The only reason I can think of to let a bug unfixed in my software is that it's definitely to costly to fix. In this case, we may choose to change this from 'bug' to 'known limitation' or 'known bug', and we fix the feedback we give to the user accordingly, so that the user knows exactly what's going on and why it's not fixed (see my edit below)

所以通常,只要QA抱怨某些东西,我会花费我所有的时间错误修复,和我所有的时间编码,当它不是! :)

So typically, I spend all of my time bug fixing as long as the QA is complaining about something, and all of my time coding when it's not ! :)

我这样做是因为:


  • 做了很多事情,但是随机崩溃,用户会觉得他不能依靠软件,还有没有可以解决这个问题。

  • When a software does a lot of things, but crashes randomly, the user will get a feeling that he cannot rely on the software, and there's NOTHING you can do to fix this. ever.

当软件缺少一些功能,但擅长做的事情时,用户会认为这可能是一个很棒的软件,太糟糕了它不支持X和Y ...我会在6个月内检查下一个版本。

When a software lacks some features, but is good at doing what it does, the user rather thinks "That may be a great software, too bad it doesn't support X and Y... I'll check the next release in 6 months".

Joel Spolsky在他的
12个步骤来更好地编码

Joel Spolsky has written an interesting post on that question in his 12 steps to better code.

编辑以回答评论:如果我遇到随机崩溃,这绝对是一个错误,而不是已知的限制。一旦我确切知道发生了什么,只有这样,我可以决定是否可以修复它。

Edit to answer comments : If I'm experiencing random crashes, that's definitely a bug, not a "known limitation". Once I know exactly what is going on, and only then, I can decide whether I can fix it or not.

我想起以下情况:


  • 错误是由不属于我的代码(通常是第三方库)引起的。如果实施解决方法非常复杂,请等待第三方供应商修复它。真实世界的例子:Clickonce在某些代理情况下不起作用...我希望微软最终解决它。

  • the bug is provoked by code that doesn't belong to me (typically a third party library). If implementing a workaround is very complicated, it might be OK to wait for the third party vendor to fix it. Real world example : Clickonce doesn't work in some proxy situations... I expect Microsoft to fix it, eventually.

如果错误是一个特定的功能在所有情况下都不起作用,而且这个功能对于特定情况来说太难实现了,我认为可以在之前向用户发出警告,他使用的功能就是要做的是没有实现,而不仅仅是崩溃。

If the bug is that a specific feature doesn't work in all situations, and that this feature is too difficult to implement for those specific situations, I think it's ok to warn the user before he uses the feature that what is trying to do is not implemented, rather than just crashing.

这篇关于实现功能与修复错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆