????你已經(jīng)被聘為軟件工程師？恭喜你！

????不過，這只是完成了一半的挑戰(zhàn)。另一半呢？從一開始就迅速有力地行動起來。因為，不管你是在谷歌山景城總部豪華舒適的環(huán)境中編程，還是在舊金山尚處于起步階段、只有10名員工的創(chuàng)業(yè)公司里努力工作，還是在其他什么地方堅持不懈，對軟件工程師的需求一如既往非常高。如果你擅長這份工作，誰知道你的面前會出現(xiàn)什么機會呢？

????如何讓新工作變成展示才華的機會？教育創(chuàng)業(yè)公司Codecademy聯(lián)合創(chuàng)始人扎克?西姆斯提供了下面幾個建議：

????盡早設(shè)定期望值。搞清楚雇主依賴的工具是什么。一家公司使用的技術(shù)平臺常常會決定他們內(nèi)部的工作方式。一些工具，比如MongoDB，能夠幫助開發(fā)開源技術(shù)。而管理源代碼可以通過Bitbucket、GitHub或者Subversion這樣的系統(tǒng)實現(xiàn)。了解這些工具以及自己團隊使用它們的方式，這些對你在團隊中正常發(fā)揮作用至關(guān)重要。

????了解公司的架構(gòu)同樣很重要：是不是所有人都在一個地方工作，或者說是不是有一些員工是進行遠(yuǎn)程辦公的？西姆斯解釋說，一些公司，比如應(yīng)用開發(fā)商37Signals或者問答網(wǎng)站StackExchange是由很多遠(yuǎn)程辦公人員構(gòu)成的。這些公司的企業(yè)文化往往有別于那些所有人集中在一起辦公的公司【37Signals創(chuàng)始人杰森?弗里德曾就這個主題寫出了《遠(yuǎn)程》（Remote ）一書】。如此以來，在這樣的環(huán)境中工作常常涉及大量的溝通，同時也要求擅長獨立開展工作。

????企業(yè)文化是否允許失?。克腥硕紩稿e，但每家公司應(yīng)對錯誤的方式不盡相同。一些規(guī)模較小的公司通過快速迭代獲得成功。如果公司能夠快速行動——硅谷企業(yè)家埃里克?萊斯曾在2011年出版的著作《精益創(chuàng)業(yè)》（The Lean Startup）一書中介紹過這種方法——那么只要你能汲取教訓(xùn)，改正錯誤，失敗就是可以被接受的。但其他規(guī)模更大的公司通常擁有固定的發(fā)布日期，而且不允許產(chǎn)品代碼中存在漏洞。西姆斯說：“了解生產(chǎn)和穩(wěn)定性的標(biāo)準(zhǔn)指引著一件產(chǎn)品的創(chuàng)造流程?！?/p>

????尋找一位導(dǎo)師。如果沒有導(dǎo)師的指引，公司里的后起之秀通常無法做出令人印象深刻的成績，軟件工程師在這方面也不例外。西姆斯建議在公司內(nèi)外尋找一位導(dǎo)師。這個人顯然要有更豐富的經(jīng)驗，但“也只是領(lǐng)先一步”，而不是那種層次太高的大神。西姆斯說：“想要為新手設(shè)計一種學(xué)習(xí)過程，這個人就得了解、記得一無所知是什么樣的一種情形。”（財富中文網(wǎng)）

????譯者：王燦均??

????So you've been hired as a software engineer. Congratulations.

????That was half the challenge. The other? Hitting the ground running from day one. Because whether you're coding from the plush comforts of Google's (GOOG) Mountain View headquarters, toiling at an early-stage San Francisco startup of 10, or plugging away elsewhere, the demand for software engineers is as high as it has ever been. If you excel at this job, who knows what opportunities will come your way for the next?

????Zach Sims, co-founder of the education startup Codecademy, offer several tips for ensuring that new job becomes a showcase for your talent.

????Set expectations early. Figure out which tools your employer relies on. Companies use technology stacks that often dictate how they work internally. Some, like MongoDB, help to develop open source technologies. And managing source code may happen via Bitbucket,GitHub, or a system like Subversion. Knowing these tools and how your team uses them is essential to functioning well on a team.

????It's also important to understand the company's structure: Does everyone work in one place, or do some employees work remotely? Some companies, including web app maker 37Signals or question-and-answer network StackExchange, are composed of lots of remote workers, explains Sims. These cultures tend to be different from those where everyone is located in the same office. (To wit, 37Signals founder Jason Fried penned the book Remote on the subject). As such, working in this kind of environment tends to require over-communication and being adept at working independently.

????Okay to fail? Everyone makes mistakes, but each company handles them differently. Some smaller companies iterate their way to success. If the company moves quickly, an approach Valley entrepreneur Eric Ries explained in the 2011 book The Lean Startup, failure is acceptable so long as you learn and can fix your mistakes. But other, larger companies usually have solid ship deadlines and can't permit bugs in production code. "Knowing the standard for production and stability guides how a product goes through the creation process," says Sims.

????Find a mentor. Rising stars within a company don't often impress without a mentor guiding them, and software engineers are no exception. Sims recommends finding someone inside the company or outside who clearly has more experience, but also is "just ahead of the curve from them" as opposed to some advanced wunderkind. Says Sims: "To design a learning process for a beginner, you need to remember and understand what it's like to not know everything."??