进入一个新的开发项目 [英] Getting into a fresh development project

问题描述

大家好，



我被分配到一个新的MVC.net开发项目，并且还有一个开发人员。根据要求，团队规模会增加。

请建议我应该为项目的顺利进展做好准备。

另外，从文档的角度来看，所有的我应该学习的工具。



谢谢



我尝试了什么：



我正在刷MVC，jquery& sql server。

Hi Everyone,

I have been assigned to a fresh MVC.net development project and along with me there will be one more developer. As per the requirement team size will increase.
Please suggest what all i should prepare for the smooth progress of the project.
Also, for the documentation point of view what all tools i should learn.

Thanks

What I have tried:

I am brushing up MVC, jquery & sql server.

推荐答案

鉴于我从头开始创建一个MVC项目并且当时比较新，我将解释一些我的想法。其中一些可能是显而易见的，但你的问题并不是很清楚你想要什么。



这些是我根据自己的经验提出的意见。并不意味着它的权利或100％你应该做的。如果有机会，我可能会做一些不同的事情。



1）从控制器中抽出代码。这将允许可重用​​性。这意味着如果你有一个计算器操作并且逻辑直接嵌入你的控制器。将它拉出到计算器类中。



你永远不知道什么时候你可能需要在其他地方使用它并且不希望必须处于连续循环中重构。



2）查看Web API。您现在可能只构建一个MVC应用程序，但如果您需要构建一个淡化的门户网站或移动应用程序，您可以在Web api中拥有一个中间层，而无需在整个地方拥有相同的代码。



你的MVC应用程序将与web api层集成。



3）不要吝啬单元测试。在组环境中，如果你编写一些没有文档或单元测试的代码，可能会花大量时间来解释你的代码如何工作，直到你最终记录它，或编写单元测试。



在我看来，单元测试不仅仅是测试，而且它们是展示代码使用方式的好方法。如果有关于如何使用您编写的库的问题，而不是一遍又一遍地重新解释自己，您可以指导您的同事进行您编写的测试以显示它们的使用方式。



这方面的好处是，现在，如果有人对您的图书馆进行了更改，您就会知道它的中断时刻。



我绝不提倡吝啬文件，但在现实世界中......必须切割文件，文件就是其中之一，直到有时间。



4）从一开始就建立一个构建服务器（例如：团队城市）并让它在签入时构建你的代码。你会立刻知道构建何时中断。



5）逻辑组织你的javascript文件并强调可重用性。不要将代码直接嵌入到视图中（在合理范围内）。你显然会有类似

Given that I started an MVC project from scratch and was newer at the time, I'll explain some of my thoughts. Some of these may be obvious but your question isn't very clear in terms of what exactly you want.

These are my opinions from my experience. Doesn't mean its right or 100% what you should do. Just some things I may do differently if given the chance.

1) Abstract your code out from the controller. This will allow reusability. So meaning if you've got a calculator operation and the logic is embeded directly into your controller. Pull that out into a Calculator class.

You'll never know when you may need to use that elsewhere and don't want to have to be in a continuous loop of refactoring.

2) Look into Web API. You may be building just an MVC application today, but if you need to build a watered down portal, or a mobile application, you can have a middle tier in web api without having to have the same code all over the place.

Your MVC application would integrate with the web api layer.

3) Don't skimp on unit testing. In a group environment, if you write some code without documentation or unit tests, probably plan on spending a lot of time explaining how your code works until you finally document it, or write unit tests.

In my opinion, unit tests aren't just tests but they are a good way to show how the code is used. If there are questions on how to use a library you wrote, rather than re-explaining yourself over and over, you can just direct your coworkers to the tests you wrote to show how they are used.

The "side" benefit from this is that now, if someone makes a change to your library you'll know the moment it breaks.

I am by no means advocating skimping on documentation, however in the real world...things have to be cut and documentation is one of them until there is time.

4) Set up a build server from the start (ex: Team City) and have it build your code on checkin. You'll know immediately when a build breaks.

5) Organize your javascript files logically and emphasize reusability. Don't embed code directly into the view (within reason). You'll obviously have stuff like

（function（）{MyJsFile.runFunction（）;}）;,但不要在视图中嵌入整个javascript函数/ jquery代码。



鼓励可重用并将其抽象为文件，编写插件/ js模块。



6）观看你的技术债务。不要欠超过你能偿还。

---



可能有更多花絮的东西我会做的不同，但那些是最好的。

(function() { MyJsFile.runFunction(); });, but don't embed the entire javascript function/jquery code inside a view.

Encourage reusability and abstract it to a file, write plugins/js modules.

6) Watch your technical debt. Don't "owe" more than you can "repay".
---

There are probably a lot more tidbits of things i'd do different but those are some of the top ones.

这篇关于进入一个新的开发项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！