如何说服我的部门实施版本控制系统? [英] How can I convince my department to implement a version control system?

查看:27
本文介绍了如何说服我的部门实施版本控制系统?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近加入了一家大型保险公司的 IT 部门.虽然部门的名称是IT",但很多代码都是在这里写的;Java、JSP、JavaScript、COBOL 甚至一些我听说过的 C++.允许保险公司、经纪人和其他系领带的白领工人签发新合同并与客户打交道的所有程序都运行在该部门生成的代码上.有人告诉我,按照母公司的标准,该部门相当不错,我们甚至还获得了一两个内部奖项.我们部门有 17 人,分成 2 或 3 人一组. 正如您从 COBOL 部分进一步猜到的那样,平均年龄超过 40 岁(作为参考,我是 29 岁).

I recently joined the IT department of a big insurance company. Although the department's title is "IT", a lot of code gets written here; Java, JSP, JavaScript, COBOL and even some C++ from what I've heard. All the programs that allow insurers, brokers and the rest of the tie-wearing, white-collar workers to issue new contracts and deal with clients runs on the code produced by this department. I've been told that the department is pretty good by the parent company's standards and that we've even received an internal award or two. We're 17 people in the department, split in smaller groups of 2 or 3. As you might've guessed from the COBOL part further up, the average age is over 40 years (as a point of reference I'm 29 yo).

目前,还没有适当的版本控制系统(尽管存在通用备份方案).需要时,文件通过共享文件夹传递.通常,每个组中都有一个人负责将文件的最终"版本复制回生产服务器.我觉得这很荒谬,甚至有点危险.

Right now, there is no version control system in place (there exists a general backup scheme though). When needed, files are passed around through shared folders. Usually there's one person in every group responsible for copying the "final" version of the files back to the production server. I find this absurd and even a bit dangerous.

我怎样才能说服管理层我们应该在我们的部门实施 VCS 计划?我自己从未部署过 VCS,但我工作过的所有其他地方都有.我想我会从第一步就遇到我们一直都很好,为什么要麻烦"的墙,再加上我大多数同事的年龄都会觉得这一步是不必要的障碍.

How may I try to convince management that we should implement a VCS scheme in our department? I've never deployed a VCS myself but every other place I've worked at had one. I think I'll hit a "we've been OK until now, why bother" wall from the first step, coupled with the age of most of my co-workers that will feel this step is an unnecessary hurdle.

我知道 VCS 的基本优势(可追溯性、粒度备份、问责制等).我希望用现实案例和实施成本的真正附加值示例来支持我的案例,而不仅仅是但是-但是-但是,我们必须拥有一个 VCS,你们这些傻瓜!":-)

I know the basic advantages of VCS (traceability, granular backups, accountability etc). I'm looking to back my case with realistic cases and examples of real added value over the implementation costs, not just a "but-but-but, we must have a VCS you fools!" :-)

推荐答案

您不一定需要他们的许可.

You don't necessarily need their permission.

在您的机器上安装 svn,开始使用它,然后开始说服您的团队成员也使用它.

Install svn on your machine, start using it, and then start convincing your fellow team members to use it too.

然后观看,看看会发生什么.

Then watch and see what happens.

编辑

  • 其基本思想是展示比讲述更容易.
  • 用可行的实施/解决方案来支持您的想法是个好主意.
  • 当然,如果您成功了,并且他们希望系统在部门/公司范围内使用,您必须准备好支持过渡,知道如何安装和使用软件.
  • 继续使用行业公认的东西比讨论应该使用什么系统更快.
  • 有一个很好的变化,这会让你注意到.您也可能会得到同龄人的尊重和支持.

正如建议的那样,可以在其他领域采取相同的方法:

As suggested, the same approach can be made on other areas:

.. 任何可以明显提高您的工作质量,但不会(还)破坏现有方法和实践的项目.

.. any item that will visibly add quality to your work, but doesn't (yet) disrupt existing methodologies and practices.

这篇关于如何说服我的部门实施版本控制系统?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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