Development log - red & black (2) (轉)
Development log - red & black (2)
Black - If I can do this again.
By Zhang Hui
When the SA date is coming, an a aften occurs in my mind. That is - if I can do this again.
An old book read that if an old man can reborn and re-walk along his life from begining, he will
avoid most of the errors & fault in his life. It's also true for we developers.
If I can do this again. I will not follow the water-pool software model. It's not right for our
development. The timespan is over one year. The marketing is changing. The requrirement is changing. The UI spec
is not lock down until 3 month before SA. All are changing, all are not fixed. Yes, we can blame
someone else on slow UI spec, on always changing requriement. But actually, we can blame no one
else except ourselves. Under such condition, it's not right to do "requirement" & "high level design"
for such a long time. The more we do, the more waste we produce. Actually, we need a to
discuss with our customers, internally, UI designer and marketing guys.
If I can do this again. I will follow some rules, to test first, to release quickly. to do the
simplist design that can meet current requirement. to avoid over-disign, to communicate more. Since
we are facing with the changing world, why not exbrace the XP rule?
If I can do this again. I will use prototype to communicate with the UI designer, the marketing guys.
I have no excuse to blame on them. It's natural for anyone to say "that's not what I want" after 6
month of isolated development. It's very easy to use & PyQt/wx to make a prototype
application to capture the real requirement.
If I can do this again. I will use less time to argue with UI team. It's cost time & energy to get
little effect. I will focus on the conceptual model by myself. It's not their duty to do this level design.
I will not argue with them on the "visual effect" or some UI detail such as this checkbox should be
rectangle. The UI feature is decided by UI . We are just use standard widget. Any argument on
such issue is just a waste of time. More over, I will not argue on some "natural" things. Such as should
the pass edit display "*****" or original text. It's funny to discuss such issue.
Always do the right thing, you surely have such confidence
=======================================
版權所有 copyright 張輝
本文可原封不動的複製和自由地再發行,但在複製和再發行的複製中必須
原封不動地含有這段版權宣告。
.NET/">http://forestsong.blogone.net
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10748419/viewspace-963189/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Development log - red & black (1) (轉)dev
- Game Development Methodology for Small Development Teams (轉)GAMdev
- Red and Black(DFS入門題)
- Red and Black Plaid Shoes Golden GooseAIGo
- DX: Full Screen GUI Development 2 (轉)GUIdev
- Web2py App Development CookbookWebAPPdev
- Beans Development Kit (BDK)分析(四) (轉)Beandev
- Beans Development Kit (BDK)分析(五) (轉)Beandev
- Beans Development Kit (BDK)分析(六) (轉)Beandev
- trick整理:序列二分log^2轉log
- Red Flag 技術文件下載(轉)
- Red Hat Linux 入門指南!(轉)Linux
- Codeforces Round #249 (Div. 2) A. Black Square
- Red hat公司對Oracle的回應(轉)Oracle
- red hat linux 9.0安裝求助!(轉)Linux
- WebLogic的初步研究(2)--結構篇 (轉)Web
- game development -- flowGAMdev
- 《Fluid Engine Development》 學習筆記2-基礎UIdev筆記
- 美聯邦航空轉用Red Hat企業版Linux(轉)Linux
- Red Hat linux9 初裝配置(轉)Linux
- 製作Red Hat Linux急救盤組(轉)Linux
- 安裝red hat 9.0遇到的問題(轉)
- 安裝Red Hat9.0兩三事(轉)
- 系統操作程式:Red Hat linux inittab(轉)Linux
- Red Hat計劃公開Java原始碼 (轉)Java原始碼
- mulitpath配置+udev(red5+red6)dev
- Beaglebone Black教程Beaglebone Black的引腳分配
- Red TaiwanAI
- SharePoint online Multilingual support - Development(2)dev
- 《Expert One-to-One J2EE Design and Development》誰有???dev
- macOS Development - Auto LayoutMacdev
- office365 developmentdev
- What is strategy development process?dev
- BW: 80% of development costsdev
- Web Development Job in 4Webdev
- weblogic 2Web
- Red Hat套件讓你的EC更輕鬆(轉)套件
- Oracle 9i Installation on Red Hat Linux (轉)OracleLinux