http://eblog.cisanet.org.tw/other/Preview.aspx?ArticleID=650
Bill of Material Cost : 製造業在接單當下，往往需要馬上判斷出該筆訂單可接受的最低價格，因此需要預先估算出此筆訂單的母件按照 BOM 展開之後成本應為多少，此即為 BOM COST；實務上有些公司會只計算出材料標準用量之下所需要的標準成本當做 BOM COST，用該 BOM COST 數字除以業務接單的標準售價，公司明定政策BOM COST高於多少百分比即可能需要跑電子簽核到哪一關；另外也有些公司會把標準料工費通通算進 BOM COST 之中當做標準成本，該數字運用通常屬於管理會計的範疇，或者分析月結後實際成本與 BOM COST 估算原因差異分析。
2011年5月6日 星期五
2011年5月2日 星期一
徐慶石頭火鍋
http://pshge0624.pixnet.net/blog/post/26497069
http://tw.myblog.yahoo.com/jw!rNwwPciUFRuG_m6rNPjJ3P3eYKs-/article?mid=91&prev=153&next=81
竹東鎮長青路三段80號
電話:
03-5103649
0917-1989289
http://tw.myblog.yahoo.com/jw!rNwwPciUFRuG_m6rNPjJ3P3eYKs-/article?mid=91&prev=153&next=81
竹東鎮長青路三段80號
電話:
03-5103649
0917-1989289
十大軟體開發注定失敗的警訊
http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=a76eab63-70f0-48b4-8b75-66c366a651cd
十大軟體開發注定失敗的警訊
1. Trying to do too much in the first version. See Raymond's point above.
第一個版本就做太多功能
2. Taking a major dependency on unproven technology.
太依賴於未經證實的技術
3. Competing with an existing internal project that was either a cash cow or had backers that are highly placed in the corporate hierarchy.
與內部競爭的project, 要有強力的backer或你身處在當紅的部門!
4. The team is understaffed. If you have less people than can handle the amount of work you have to do then the right thing to do is to scale back the project. Practically every other choice leads to failure.
團隊人員不足.
5. Complexity is one of the goals of the project because "complex problems require complex solutions".
複雜性是project成功的目標之一, 因為複雜的問題需要複雜的解法!
6. Schedule Chicken
開發人員因為無法承受時程的壓力，而做出一些敷衍、耍小手段等扭曲的行為，好讓自己的工作看起來已經達到預定進度了。
7. Scope Creep
不斷變動需要實作的範圍
8. Second System Syndrome
第二版並不是要更強大, 更厲害
9. No Entrance Strategy. When a project can't articulate how it goes from a demo or prototype to being in the hands of end users, there's a problem. This is particularly relevant in the "Web 2,0" world where many startups only strategy for success is getting a mention on TechCrunch and the fact that their service has "viral" features.
缺乏進場策略
10. Tackling a problem you don't know how to solve. It's pretty amazing how often I've seen this occur.
解決一個你不知道如何解決的問題
十大軟體開發注定失敗的警訊
1. Trying to do too much in the first version. See Raymond's point above.
第一個版本就做太多功能
2. Taking a major dependency on unproven technology.
太依賴於未經證實的技術
3. Competing with an existing internal project that was either a cash cow or had backers that are highly placed in the corporate hierarchy.
與內部競爭的project, 要有強力的backer或你身處在當紅的部門!
4. The team is understaffed. If you have less people than can handle the amount of work you have to do then the right thing to do is to scale back the project. Practically every other choice leads to failure.
團隊人員不足.
5. Complexity is one of the goals of the project because "complex problems require complex solutions".
複雜性是project成功的目標之一, 因為複雜的問題需要複雜的解法!
6. Schedule Chicken
開發人員因為無法承受時程的壓力，而做出一些敷衍、耍小手段等扭曲的行為，好讓自己的工作看起來已經達到預定進度了。
7. Scope Creep
不斷變動需要實作的範圍
8. Second System Syndrome
第二版並不是要更強大, 更厲害
9. No Entrance Strategy. When a project can't articulate how it goes from a demo or prototype to being in the hands of end users, there's a problem. This is particularly relevant in the "Web 2,0" world where many startups only strategy for success is getting a mention on TechCrunch and the fact that their service has "viral" features.
缺乏進場策略
10. Tackling a problem you don't know how to solve. It's pretty amazing how often I've seen this occur.
解決一個你不知道如何解決的問題
那些十年的軟體開發經驗, 教我的十件事
http://www.taylor.se/blog/2007/03/22/top-ten-things-ten-years-of-professional-software-development-has-taught-me/
那些十年的軟體開發經驗, 教我的十件事
1. Object orientation is much harder than you think
物件導向比你想的還難
2. The difficult part of software development is communication
軟體開發最困難的部份溝通
3. Learn to say no
學會說不
4. If everything is equally important, then nothing is important
如果每件事都一樣重要, 那沒有事情是重要的
5. Don’t over-think a problem
不要對問題過度考慮
6. Dive really deep into something, but don't get hung up
伸入核心, 但別被套牢了
7. Learn about the other parts of the software development machine
學習除了軟體開發以外的東西
8. Your colleagues are your best teachers
同事就是最好的老師
9. It all comes down to working software
貼近使用者需求, 就對了!
10. Some people are assholes
這世上有些人是豬頭!
那些十年的軟體開發經驗, 教我的十件事
1. Object orientation is much harder than you think
物件導向比你想的還難
2. The difficult part of software development is communication
軟體開發最困難的部份溝通
3. Learn to say no
學會說不
4. If everything is equally important, then nothing is important
如果每件事都一樣重要, 那沒有事情是重要的
5. Don’t over-think a problem
不要對問題過度考慮
6. Dive really deep into something, but don't get hung up
伸入核心, 但別被套牢了
7. Learn about the other parts of the software development machine
學習除了軟體開發以外的東西
8. Your colleagues are your best teachers
同事就是最好的老師
9. It all comes down to working software
貼近使用者需求, 就對了!
10. Some people are assholes
這世上有些人是豬頭!
訂閱：
文章
(
Atom
)