Kent Beck on How to Get a Paper Accepted at OOPSLA
(A panel at OOPSLA-93, pages 429-436 of the proceedings) [I found this on the web somewhere, and didn't want to risk losing it so I shamelessly created a private copy. -- MWG] Comments by Kent Beck I will not talk about a topic area, like my distinguished fellow panelists. I will present the process I use as I am writing my papers. You can adapt it for your writing process, or you can use it as a
Early Development
These patterns talk about how you begin developing a system. How do you learn what you need to from the client without alienating them? How do you make sure your understanding is consistent with the needs of the program? How do you accept and take advantage of the inevitable changes in your client's thinking? The patterns are: 1. Story 2. Early Program 3. Architecture Prototype 4. Interface Protot
TDD Intro, Episode 1, first 10 minutes, unedited
Verify to continue To continue, please confirm that you're a human (and not a spambot).
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}