快速进行C#编码 [英] Quickly doing coding for C#

问题描述

我必须使用C#快速进行编码，并且需要实现一个自动化框架，这就是我接下来的2个月的任务，否则我的工作就没了了:(任何认真的建议.

I have to do coding fast in C# and need to implement an Automation framework, thats my task for next 2 months, otherwise my job is gone :( any serious suggestions.

推荐答案

唯一严肃的建议:缓慢编码.这是满足截止日期的唯一方法.

不要误会我的意思:编码应该非常快，因为如果执行得太慢，您可能会浪费太多时间来实现某些错误的设计.您总是需要留出一些空间来重新实现(不要试图愚弄自己:它总是会发生，所以最好为它做计划)，并且要腾出空间，您的工作应该相当快.

另一方面，您的工作应该始终保持整洁和健康，否则相反的效果就容易出现:您快速创建了一个工作系统，但是永远无法使其达到可接受的质量，因为您将无法整理您创建的混乱；在这种情况下，无论如何，有效地将您的工作转移到了垃圾桶上，但是更糟糕的是，这样可以节省时间，浪费时间.更重要的是，您不仅浪费时间，还浪费了同事的时间. 我称其为负面贡献，因为根本不做任何工作更糟.

我在这里的标准是:您应该在头脑中保持良好的平衡，不要过分强调自己.有时候，如果您的工作进展顺利，您可能会劳累过度并感到非常疲倦-没有人会因此而丧命.但是，如果永久发生这种情况，则说明您仅在为垃圾桶生成文件，这是一个好兆头-快速.避免使用它-比不做任何事情要糟糕得多.



两个月-是否足够?显然，这取决于工作要求.我只建议一件事:将整个工作计划为一个月，或者最好三个星期，将剩余时间保留下来.计划在第一周内制作第一个完全正常工作的原型；仅基于关键要求，首先实施工作框架.不要犯初学者常见的常见错误:未经测试就不要编写太多代码.您应该在第一天就可以运行一些系统，并在每个小步骤之后重新运行它，以确保您不会脱离现实.始终使用某些版本控制系统.

—SA

The only serious suggestion: code slowly. This is the only way to meet deadlines.

Don''t get me wrong: coding should be pretty fast, because if you do it too slowly, you may waste too much time to implement some wrong design. You always need to leave some room for re-implementation (don''t try to fool yourself: it always can happens, so it''s better to plan for it), and to make this room, your work should be reasonably fast.

From the other hand, your work should be neat and healthy at all times, otherwise the opposite effect easily comes into place: you quickly make a working system, but won''t be able to bring it to acceptable quality, ever, because you won''t be able to sort out the mess you created; in this case, effectively your work goes to garbage can anyway, but worse, as by saving time you wasted time. More importantly, you waste not just your time, but the time of your colleague. I call it negative contribution, because it''s much worse that doing no work at all.

My criteria here is this: you should feel good balance in your mind, don''t stress yourself too much. Occasionally, if your work goes well, you can overwork and get really tired — nobody died because of just that. But if it happens permanently, it''s a good sign that you are producing files only for a garbage can — fast. Avoid it — it would be much worse than doing no job.



Two months — is it enough or not? Apparently, it depends on the requirements for a job. I would advice only one thing: plan your whole work for just one month, or, better, three weeks, leave remaining time in reserve. Plan to make a first fully working prototype in first week; implement a working skeleton first, based on key requirements only. Don''t make a common mistake typical for beginner: don''t code much without testing. You should have some system runnable in first day and re-run it after each small step, to make sure you did not go out of reality. Always utilize some Revision Control System.

—SA

在任何项目中真正杀死您的事情之一没有明确的要求.仅获得所需的操作，您就很容易失去一个月.另外，您最好熟悉将要实现的设计类型.如果您没有执行多层实现，而是必须执行一个多层实现，则您可能会发现自己不得不重新做一些事情，因为您做了不好的事情，需要纠正或解决它.

换句话说，我相信除了最简单的项目之外，它对于其他任何事情都非常严格.

One of the things that will really kill you in any project is not having clear requirements. You can easily lose a month just getting what you need to do. Also, you better be familiar with the type of design you will implement. If you have not done a multi-tier implementation, and then have to do one, you will probably find yourself having to rework things because you have done something bad, and need to correct it, or work around it.

In other words, I beleive it is really tight for anything but the simplest project.

这篇关于快速进行C#编码的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！