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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- trick整理:序列二分log^2轉log
- log4j2使用及log4j2.xml分析XML
- 《Fluid Engine Development》 學習筆記2-基礎UIdev筆記
- Math.log2() 方法
- 【Postopia Dev Log】Day 2dev
- POJ 1442 Black Box
- C. Black Circles
- game development -- flowGAMdev
- Development Studio 2021,dev
- JavaScript Math.LOG2EJavaScript
- Log新增MongoDB驅動2MongoDB
- The Red Button
- Web Development Job in 4Webdev
- SpringBoot—整合log4j2入門和log4j2.xml配置詳解Spring BootXML
- Java的Log架構(Log4j2 + Slf4j)Java架構
- Black Out for mac (影像模糊工具)Mac
- ABC 322 E Product Developmentdev
- SAP EPD - Enterprise Product Developmentdev
- Apache JMeter 5.4.1 Build DevelopmentApacheJMeterUIdev
- TGDC | Evolving AAA Game DevelopmentGAMdev
- Mysql系統變數中 log_error_services | log_filter_internal; log_sink_internal 和 log_error_verbosity | 2 解釋MySql變數ErrorFilter
- PostgreSQL DBA(22) - MVCC#2(commit log)SQLMVCC#MIT
- log4j2生效
- mininet Red-ecn
- CF1626E Black and White Tree
- 使用 Black 自由格式化 PythonPython
- [Black Watch 入群題]PWN 1
- 為什麼加上<log4j2.version>配置就可以更新log4j2的版本?
- webpack 開發模式管理 DevelopmentWeb模式dev
- Python Geospatial Development reading note(1)Pythondev
- SEHS4517 Web Application DevelopmentWebAPPdev
- IEMS5731 Software Design and Developmentdev
- 帶你深入Java Log框架,徹底搞懂Log4J、Log4J2、LogBack,SLF4JJava框架
- Log4j 1.x 將直接升級到Log4j2
- Red Hat 7.5 Yum Replacement
- Review: Red Star over ChinaView
- Red Giant Magic Bullet SuiteUI
- 2 萬字 + 30 張圖 | 細聊 MySQL undo log、redo log、binlog 有什麼用?MySql
- Yii2 log 模組,訊息日誌