在解释为什么＆QUOT;只要添加另一列到DB＆QUOT;是一个坏主意，非程序员 [英] Explaining why "Just add another column to the DB" is a bad idea, to non programmers

问题描述

我有销售人员和谁试图定制销售给客户，这是好的豆专柜。但是，当一个复杂的变更请求进来，我发回了大量估计，他们感到困惑。他们经常回来我：为什么你就不能添加另一列？它通过一个，他们的意思是每个客户端十几自定义列。

I have sales people and bean counters who are trying to sell customizations to clients, which is fine. But when a complex change request comes in that I send back a large estimate for, they get confused. Often they come back at me with "Why can't you just add another column?" which by another, they mean a dozen or so custom columns PER client.

到目前为止，所有我能回来与被我们正在试图让数据库以及标准化，这意味着什么给他们。我告诉他们，我可以创建表的一个系统，让每一个客户来定义他们自己的自定义字段，当然，这需要比只是增加了一些列的更多的时间和金钱。当然，他们希望有自己的鱼与熊掌兼得了。

So far all I can come back with is "We are trying to keep the database well normalized" which means nothing to them. I tell them I can create a system of tables that allows each client to define their own set of custom fields, but of course that takes more time and money than "just adding a few columns". And of course they want to have their cake and eat it too.

所以，我怎样才能让他们明白？

So how can I make them understand?

推荐答案

我已经找到了最好的办法是告诉你如何创建一个新的功能的出来，他们在问什么为的你不能只用几个自定义列添加。特点是比定制好，尤其是当你可以收取别人吧。

The best way I've found is to show how you can create a new feature out of what they're asking for that you couldn't add with just a couple customized columns. Features are better than customizations, especially when you can charge someone for it.

试着让你的身边了良好的业务情况下，你在进入技术的东西了。

Try to make a good business case for your side before you get into the technical stuff.

这篇关于在解释为什么＆QUOT;只要添加另一列到DB＆QUOT;是一个坏主意，非程序员的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！