# 六種量化你代碼的方式 本文為譯文，譯者為Leo Hui(我自己！)。 ~~~ Businesspeople dig numbers. They don’t necessarily want to hear that you got something done; they want to hear how much you got done—especially relative to past results or some other relevant benchmark—and they want to know the value of what you did. ~~~ 商人關注的是量化，他們想從你哪里通道你做了什么，帶來了什么價值，而不是你做了多少。 ~~~ Some professionals have it easy when it comes to quantifying their job performance. Salespeople can measure their achievements in dollars and cents, for example, and many other fields also have clear-cut numbers with which to calculate their contributions. ~~~ 教授可以輕松地量化出他們的工作，銷售人員可以計算出他們的收益。其他的領域也可以通過一些方式算出他們的貢獻。 ~~~ For software developers and some other technology-based roles, however, quantifying your work can be a struggle without a straightforward solution. Yet doing so is crucial not just in job searches, but in many aspects of a software engineer’s career: performance reviews, effectively communicating up the chain of command, working efficiently with non-technical business units, and ensuring you’re properly valued within your organization. ~~~ 但是從事軟件開發以及技術相關的人員，量化工作確實一個困難的事情。量化這件事情，不是在求職，更是一個技術人員生涯的一部分。績效評估，有效的了解溝通，高效的和非技術人員合作，確保你再團隊或組織中的價值。 ~~~ So how do you measure the value of the applications you build, scale, monitor, test, and otherwise support? Here are some of the approaches used at New Relic, as well as industry best practices: ~~~ 但是我們要如何量化工作中的價值呢？這里有一些New Relic推薦的做法： ~~~ “I like to see work accomplishments described in terms of situation, action and results,” says Merilee Krebs, a technical recruiter at New Relic. “What was the business or technical problem to be solved? What unique actions did you take to resolve them and what was the resulting improvement.” ~~~ New Relic的技術招聘人員這樣說："我喜歡看到用情況，行動和結果去描述工作成果， 技術人員需要解決的問題是什么？采用什么樣的行動去解決和提升這個問題。" ~~~ What does that look like in the real world? Try asking yourself some pointed questions: Did your monitoring and testing lead to a code update that cut down on help desk tickets by X percent? That’s quantitative gold right there. Did you deliver a new app six weeks ahead of schedule? Yeah, you’ll want to brag about that (in a professional manner, of course). Can you connect your code to strategic company objectives? Please, do so. Are you doing something that’s outperforming the traditional standards in your industry? You should be able to quantify the achievement is some way. ~~~ 現實世界中是怎樣的呢？你試著問自己一些關鍵的問題：你有在更新你的代碼的時候去監控和測試...這就是量化的目標。如果你在日程表前六周就完成了一個app，你肯定會去炫耀一下。但是你有考慮公司的戰略目標嗎，如果沒有，請思考一下。... ~~~ If this exercise feels unnatural to you, you’re not alone—many programmers often aren’t born sales and marketing pros. If they were, they’d probably work in sales or marketing. So let’s consider six ways to better measure and communicate the value of your code and related work. ~~~ 你是不是感受到一些不同的感覺，這不是你一個人的問題，技術人員的通病。如果技術人員做好了量化這一塊，那么他們也許就去從事銷售了。所以，讓我們考慮六種去量化你代碼以及工作的方式： ### Think in percentages ### Get involved with open source projects ### Measure progress, not just products ### Keep a work journal ### Communicate in two languages ### Collect recommendations ### 參考資料 - [6 Ways to Quantify Your Code—and Why You Need to Do It](http://blog.newrelic.com/2014/12/16/quantify-your-code/)