If you're an experienced developer then you should be able to tell what is costing you time due to learning the new platform versus solving the problem at hand.
Keep track of what you do (using a screencap application could help here) and if it's pure research (reading articles, looking up documentation) then don't bill it. Also, if you're fixing a bug that turns out to be a newbie mistake (such as misunderstanding some information), then don't bill that. The rest of your time will have been spent in productive work for the client, and that should be what is billed.
It sort of goes without saying, but your client would be the one to determine if they even want to go with you as a consultant if you don't know the language/platform they want you to work on, and they would also be the ones to tell you whether or not they will pay for you to "learn as you code". You just need to be upfront and honest with everything from the start. Don't act like you know a platform/language if you don't.
No - its not unethical. Our profession demands that we learn something new on a constant basis. This is why we can be expected to charge / get paid what we do. Employers are often willing to not only buy books for us, but also pay for certifications, seminars, and any time we spend at said extended learning. The rationality behind it is that if we learn something new, there is inevitably a payoff for them (be-it efficiency, performance, etc).
I suspect that you'll argue that its different because you are freelancing so I'll pose the question - why is it any different? Your employer is your client - if you feel that they'll gain benefit from said platform over another then you are doing them a service and should be compensated as such.
It sounds like you're all talking of "Time and Materials" projects where the client pays you however much time you take to complete the job. On a project like that I can see how this comes into play and I would recommend being honest.
Most of the projects I work on are "Fixed Price". The customer gives us an idea of what they want. We then work up a "Fixed Price" quote. If the customer doesn't like the numbers they go elsewhere, if they're ok with the numbers then they agree to the price. Whether we have to learn something to get the job done or not the customer's price remains the same. In this situation it doesn't matter. The customer either agrees to the price or not and it doesn't matter how much time it takes you.
I've been in a situation like this with adobe air. Yes it's not exactly like jumping from Java to .NET or from PHP to Python since I already knew javascript. Actually I was affraid that I'd come off as too expensive and gave a below margin price for the project. But didn't regret it because the client was very satisfied and returned with another 2 projects later.
If the price you offer is acceptable to your client and you are absolutely sure you can deliver a high quality product there's nothing unethical with it.
发布评论
评论（6）
如果你透露你的主要专业知识是在他们雇用你进行开发的平台以外的平台上，我认为这里没有道德问题。
I see no ethical problem here if you disclose that your primary expertise is on platforms other than the one that they're hiring you to develop on.
假设您按小时计费：
如果您是一位经验丰富的开发人员，那么您应该能够分辨出学习新平台与解决手头问题花费的时间是什么。
跟踪你所做的事情（使用屏幕截图应用程序可能会有所帮助），如果它是纯粹的研究（阅读文章，查找文档），那么就不要计费。 另外，如果您正在修复的错误最终被证明是新手错误（例如误解了某些信息），那么就不要为此付费。 您剩下的时间将花在为客户进行富有成效的工作上，这应该是计费的内容。
Assuming you're billing hourly:
If you're an experienced developer then you should be able to tell what is costing you time due to learning the new platform versus solving the problem at hand.
Keep track of what you do (using a screencap application could help here) and if it's pure research (reading articles, looking up documentation) then don't bill it. Also, if you're fixing a bug that turns out to be a newbie mistake (such as misunderstanding some information), then don't bill that. The rest of your time will have been spent in productive work for the client, and that should be what is billed.
这是不言而喻的，但如果您不知道他们希望您使用的语言/平台，您的客户将决定他们是否愿意与您一起担任顾问，而且他们也将是告诉您他们是否愿意付费让您“一边编码一边学习”。 您只需要从一开始就对一切保持坦诚和诚实即可。 如果您不了解某个平台/语言，请不要表现得好像您了解该平台/语言。
It sort of goes without saying, but your client would be the one to determine if they even want to go with you as a consultant if you don't know the language/platform they want you to work on, and they would also be the ones to tell you whether or not they will pay for you to "learn as you code". You just need to be upfront and honest with everything from the start. Don't act like you know a platform/language if you don't.
不——这并不不道德。 我们的职业要求我们不断学习新东西。 这就是为什么我们可以预期我们所做的事情会收取费用/获得报酬。 雇主往往不仅愿意为我们购买书籍，还愿意支付认证、研讨会以及我们花在上述扩展学习上的任何时间。 其背后的合理性是，如果我们学习新的东西，他们不可避免地会得到回报（无论是效率、性能等）。
我怀疑你会说它不同，因为你是自由职业者，所以我会提出一个问题 - 为什么它有什么不同？ 您的雇主就是您的客户 - 如果您认为他们会从该平台而不是其他平台中受益，那么您就是在为他们提供服务，并且应该得到相应的补偿。
No - its not unethical. Our profession demands that we learn something new on a constant basis. This is why we can be expected to charge / get paid what we do. Employers are often willing to not only buy books for us, but also pay for certifications, seminars, and any time we spend at said extended learning. The rationality behind it is that if we learn something new, there is inevitably a payoff for them (be-it efficiency, performance, etc).
I suspect that you'll argue that its different because you are freelancing so I'll pose the question - why is it any different? Your employer is your client - if you feel that they'll gain benefit from said platform over another then you are doing them a service and should be compensated as such.
听起来你们都在谈论“时间和材料”项目，无论您完成工作所需的时间多少，客户都会向您支付费用。 在这样的项目中，我可以看到这是如何发挥作用的，我建议诚实。
我从事的大多数项目都是“固定价格”。 客户让我们了解他们想要什么。 然后我们制定“固定价格”报价。 如果客户不喜欢他们去其他地方的数字，如果他们对这些数字感到满意，那么他们就会同意这个价格。 无论我们是否需要学习一些东西来完成工作，客户的价格都保持不变。 在这种情况下，这并不重要。 客户要么同意这个价格，要么不同意，不管你花多少时间。
It sounds like you're all talking of "Time and Materials" projects where the client pays you however much time you take to complete the job. On a project like that I can see how this comes into play and I would recommend being honest.
Most of the projects I work on are "Fixed Price". The customer gives us an idea of what they want. We then work up a "Fixed Price" quote. If the customer doesn't like the numbers they go elsewhere, if they're ok with the numbers then they agree to the price. Whether we have to learn something to get the job done or not the customer's price remains the same. In this situation it doesn't matter. The customer either agrees to the price or not and it doesn't matter how much time it takes you.
我用adobe air就遇到过这样的情况。 是的，这并不完全像从 Java 跳到 .NET 或从 PHP 跳到 Python，因为我已经了解了 javascript。 事实上，我担心自己的价格太贵，因此为该项目给出了低于保证金的价格。 但我并不后悔，因为客户非常满意，后来又带着另外两个项目回来了。
如果您提供的价格是您的客户可以接受的，并且您绝对确信您可以提供高质量的产品，那么这并没有什么不道德的。
I've been in a situation like this with adobe air. Yes it's not exactly like jumping from Java to .NET or from PHP to Python since I already knew javascript. Actually I was affraid that I'd come off as too expensive and gave a below margin price for the project. But didn't regret it because the client was very satisfied and returned with another 2 projects later.
If the price you offer is acceptable to your client and you are absolutely sure you can deliver a high quality product there's nothing unethical with it.