原文：You Are Not a Software Engineer (Yet)
PARAGRAPH3
**Constantly Examine Your Day With a View to "Optimize for Value". **
There is a surprisingly large part of a coder's day that is wasted on things are frankly not worth the effort.If an activity brings you or your company no value, then why are you spending time on it?Often time this might take the form of meetings, people or "process"
Recently a friend of mine lamented to me that since being promoted to "Team Leader" he felt like he could never get anything done.So he decided to track his time. At the end of the week he had discovered that he had been able to spend a total of 20 minutes on engineering.Now, if the rest of his time had been taken up with mentoring or leading his team than this would not be a bad thing but sadly most of his time was "spent" by others; Other teams; Other departments and so on.
PARAGRAPH4
Please don't let me misguide you into thinking that collaboration and communication is not absolutely imperative.
My point is as engineers, we should focus on finding the best solution. That is what an engineer does.
For example:
If a meeting is about "syncing up" then consider being proactive and publishing your status on a wiki, internal blog or via email distribution. Let other "self-service" the information at a time and rate that suits them.
If you are a team or department lead and feel like you spend your entire time in meetings that achieve very little then delegate. This not only frees you up but it will allow your team members to experience more and grow. Be sure to empower those your delegate to make some or all the decisions, otherwise people will insist on your presence. Also be sure to back your team members decisions; they need confidence to make decisions and represent your interests without fear.
If your boss wants on know "what's been worked on" or "what was achieved" then find a tool that works for you and use it. Keeping a list of tasks up to date is a minor task that all team members can do at little cost.
If the "process" requires that you take 5 steps to complete a task but most of are mind-numbing mechanical stuff. (e.g. generating a change log or sending an email notification) then use your skills as a programmer to automate as much of it as you can. Consider a simple the task takes 10 minutes and you must do it once a day. If you spend 2 hours to make a script that reduced that task from 10 minutes to 2 minutes then your time would be "paid back" in 15 days!
Find yourself constantly distracted by email or IM notifications? Close the apps! As programmers our work requires a great deal of concentration and any little distraction can upset your flow and otherwise slow you down. One of the great advantages of text-based communication is that it's designed to be "disconnected"; this means you are free to interact with it at your pace. Some people take this a step farther with concentrated bursts of concentration using the Pomodoro technique. While I recommend trying this, it's not for everyone and I frequently find it hard to stick to.
翻譯
PARAGRAPH3
--不斷從“價(jià)值優(yōu)化”的角度來檢查你度過的每一天
++不斷從“優(yōu)化價(jià)值”的角度來檢查你度過的每一天
程序員每天多的讓人驚訝的時(shí)間浪費(fèi)在沒有意義的事情上逗扒，坦白說，是在作無用功延欠。
如果一件事不會(huì)給你或者你公司帶來任何價(jià)值涛酗，那為什么要花時(shí)間在上面呢铡原？通常這種事情是會(huì)議、聚會(huì)或者"流程”之類商叹。
最近我一個(gè)朋友向我抱怨燕刻，自從升為“團(tuán)隊(duì)領(lǐng)導(dǎo)”之后，自己幾乎沒完成任何一件事情剖笙。
所以他決定回顧檢查自己的時(shí)間酌儒。他發(fā)現(xiàn)一周之后，自己僅僅在“工程”方面花的時(shí)間總共20min枯途。
現(xiàn)在忌怎，如果他的其他的時(shí)間是花在指導(dǎo)或領(lǐng)導(dǎo)團(tuán)隊(duì)上倒是還好，但不幸的是大部分時(shí)間”花在“其他人酪夷、其他團(tuán)隊(duì)榴啸、其他部門等等。
PARAGRAPH4
請(qǐng)不要把我的觀點(diǎn)誤解為合作和交流完全沒必要晚岭。
我的意思是作為工程師鸥印，我們的重點(diǎn)是找到最佳解決方案。這才是工程師要做的坦报。
比如說：
- 如果會(huì)議是關(guān)于“同步”的（團(tuán)隊(duì)成員之間同步進(jìn)度）库说，那就積極一些。把你的進(jìn)度狀態(tài)發(fā)布到wiki片择、內(nèi)部博客或者郵件列表潜的。讓其他成員及時(shí)了解你的進(jìn)度，適應(yīng)大家的節(jié)奏字管。
- 如果你是團(tuán)隊(duì)或者部門領(lǐng)導(dǎo)啰挪，并且感到在會(huì)議上花很多時(shí)間去解決小問題信不，那就放權(quán)，交給下屬亡呵。這不僅僅騰出你的大量時(shí)間抽活，而且讓團(tuán)隊(duì)成員積累更多經(jīng)驗(yàn)，更快成長(zhǎng)锰什。請(qǐng)務(wù)必授權(quán)下屬進(jìn)行部分或者全部決策下硕，否則，解決問題的人會(huì)要求你不斷參與進(jìn)來汁胆。同時(shí)務(wù)必要支持下屬的決策卵牍；他們需要自信來進(jìn)行決策，表達(dá)你意見的時(shí)候不要到這懷疑的情緒沦泌。
- 如果你老板想要指導(dǎo)“哪些正在做”或者“哪些已經(jīng)完成”糊昙，那最好找個(gè)工具匯報(bào)這些事情。建立一個(gè)隨時(shí)更新的任務(wù)列表谢谦，這是一個(gè)團(tuán)隊(duì)成員花一點(diǎn)點(diǎn)精力就可以做到的小任務(wù)释牺。
- 如果“流程”要求你用5個(gè)步驟完成任務(wù)，但大部分是麻木機(jī)械的工作回挽。（比如生成改變?nèi)罩净蛘甙l(fā)送郵件提醒）没咙，那你就發(fā)揮你作為“碼農(nóng)”的特長(zhǎng)，盡量自動(dòng)完成千劈。想一下祭刚，如果有個(gè)簡(jiǎn)單任務(wù)要求你每天要花10min完成。那你花2小時(shí)寫個(gè)腳本把這個(gè)任務(wù)簡(jiǎn)化到2min墙牌，“浪費(fèi)”的時(shí)間只需要15天你就賺回來Ｎ型浴！喜滨！
發(fā)現(xiàn)自己經(jīng)常由于email或者即時(shí)通訊消息所干擾分心捉捅？那就關(guān)掉這些應(yīng)用！作為程序員我們的工作需要集中注意力虽风，任何小干擾都可能搞亂我們的流程棒口，打亂節(jié)奏。這種在電腦上通過文本的交流方式有一個(gè)最大的優(yōu)點(diǎn)辜膝，那就是“異步”无牵；這意味這你可以在任何空閑進(jìn)行交流。一些人采用“番茄工作法（http://pomodorotechnique.com/ ）”來解決這個(gè)問題厂抖。雖然我建議你試試茎毁，但是這并不適合每個(gè)人，我試了試覺得很難堅(jiān)持验游。（譯者：臥槽充岛，那你還推薦）
