[轉貼] The Real Work of (Software) Management

The Real Work of (Software) Management

從開發者轉職到管理職的人時常會有一種... 沒有實際產出的感覺, 對吧? 有時總是會忍不住跳下去寫程式, 然後對於真的管理者該做的事卻反應慢半拍。好啦, 我以前有一陣子是這樣, 不過這兩年已經改善許多了。

這篇文章提到許多管理者該做的事情與其價值, 我覺得很不錯, 把這些事情 "具現化" 了, 大家可以參考一下, 以下列出幾點:

• 確認加入團隊的是對的人, 並且有正確的訓練
• 打造有生產力的工作環境, 並且確保有最棒的工具
• 保護團隊免於組織、公司的政治或分心的事
• 確保上層知道開發團隊創造出來的價值
• 確保團隊的努力有朝著公司、組織的目標

最後這篇文章的重點就是, "It's a REAL work", 大推這篇文章。


資料來源：http://weekly.codetengu.com/issues/11

[轉貼] Good Tech Lead, Bad Tech Lead

Good Tech Lead, Bad Tech Lead

這是 Foursquare 的技術團隊領導（Tech Lead）指南，從不同面向點出好壞 Tech Lead 的做法差異。簡單來說，好的 Tech Lead 應該要：

1. 視自己為團隊一份子、幫忙排除障礙（如減少不必要的瑣事）讓成員可以專心發揮所長
2. 掌握大局並做適當安排
   • 預見可能發生的問題
   • 了解每個團隊成員的能力與工作狀況
   • 掌握平衡，尤其是「準時完成」與「追求品質」
3. 溝通、討論：先把時間花在溝通而非編寫程式
• 參與產品規劃、不是一味接受需求
• 鼓勵成員間的討論、參與時不帶定見

資料來源：http://weekly.codetengu.com/issues/10

[轉貼] This Is What A GOOD Resume Should Look Like

This Is What A GOOD Resume Should Look Like

Note: This is for a US-focused resume. CVs for India and other countries have different expectations, although many of the points will be the same.

Although the example here is a developer resume, almost all of these points (everything but #9 and #11) apply to other positions as well.

1. One Page Resume: Recruiters do not read your resume; they do a 15 - 30 second "spot check" of your resume. When your resume is too long, it just takes your best stuff - the stuff that would have made the "one page cut" - and dilutes it with more mediocre content. Lengthy resumes do not make you more impressive, and there are many other reasons to keep your resume short too. A good rule of thumb is to keep your resume to one page if you have less than 10 years of experience or at most two pages if you have more than 10 years of experience. And if you think you can't get your resume to just one page, trust me, you can! You just need to think about what is really important for a recruiter to see.
2. No Objectives: All an objective does is state, in a wordy way, what position you're interested in. The company already knows that because you applied for a particular position. At best, it'll just waste space. At worst, it'll limit you since it'll exclude other positions that might have been interesting to you.
3. Use a Resume Template with Columns: Unless you're great with design, you probably shouldn't be creating your own resume template. It'll most likely look sloppy. Use a template, and make sure it has multiple columns. Using three columns, for example, will allow you to put the company name, position, and date all on one line. This makes it easier to read and saves space.
4. Use Tables: If you're using Microsoft Word to create your resume (which you probably should), use Microsoft Word's "tables." Just make sure to hide the borders afterwards.
5. Short Bullets: Because resume screeners only spend 15 - 30 seconds on your resume, length bullets - anything that feels like a paragraph - just won't get read. Keep your bullets to one to two lines (with one line being better than two).
6. Accomplishment Oriented: Your bullets should focus on your accomplishments - that is, the impact you had - rather than your responsibilities. What did you build, create, design, optimize, lead, etc?
7. Quantify: Whenever possible, you should quantify your accomplishments. If you optimized something, by how much? If you won an award, out of how many people?
8. Resume: The general rule of thumb is to list your GPA if it's at least 3.0 or higher, but there are two important rules to know here: (1) You may choose to list your in-major GPA if it's higher than your overall GPA, but you need to specify that it's your in-major GPA. (2) If your school uses a different scale (such as a 10-point scale), you may want to convert your GPA to a 4.0-scale which will be more widely understood.
9. Projects: Most candidates should pick their top 3 - 5 projects to list on their resume. These can be academic required project or independent projects. They do not need to be completed or launched either. As long as you've done a "meaty" amount of work on them, that's good enough!
10. Additional Experience: You can put additional experience, like leadership activities or awards, in a section like this (changing the name of the section depending on what you list). Be careful here to focus on what really matters. If you're applying for a coding role, your role as an eagle scout in high school is probably not very important!
11. Languages and Technologies: It's a good idea to list your languages and technologies, but remember that anything you list here is "fair game" for the interviewer to test. If you want to list a language but you happen to be a bit rusty in it, consider listing it as something like: "C++ (Proficient), C# (Prior Experience), ..."
12. What did you NOT include?: Is there anything impressive / interesting that you've done that you left out? About 50% of candidates leave out an important project or other component of their experience because it wasn't finished / "official" / etc. If you've done it, and it's impressive enough to "make the cut" (you shouldn't just list everything you've ever done), then it belongs on your resume!

Download This Template.


Reference: http://www.careercup.com/resume

[廚餘回收] Visual Studio 2015 底下使用 bower 還原封裝發生 ECMDERR ~ exit code of #128

文章已移至點部落：http://www.dotblogs.com.tw/supershowwei/archive/2015/10/28/153723.aspx

[料理筆記] ASP.NET 5 (MVC 6) First Sample on CentOS 7

文章已移至點部落：http://www.dotblogs.com.tw/supershowwei/archive/2015/10/28/153722.aspx

[料理筆記] ASP.NET 5 意外地從 beta5 升級到 beta6

文章已移至點部落：http://www.dotblogs.com.tw/supershowwei/archive/2015/10/28/153721.aspx

[料理筆記] Add Email Notification on Jenkins for .Net

文章已移至點部落 http://www.dotblogs.com.tw/supershowwei/archive/2015/10/16/153586.aspx