|
Size: 2227
Comment:
|
Size: 3170
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 23: | Line 23: |
| * [[책/AreYourLightsOn]] | |
| Line 28: | Line 29: |
| SoftwareArchitecture | SoftwareArchitecture. [[AOSA]] prefaces. |
| Line 30: | Line 31: |
| Eisenhower Matrix | The Eisenhower Matrix |
| Line 32: | Line 33: |
| Make it work, then make it better. problem space, solution space ... |
|
| Line 43: | Line 49: |
공통점과 차이점 찾기. 공통점을 공유하고, 차이점을 처리할 수 있는 기법을 습득한다. (OOP 다형성, 고차함수 등) |
|
| Line 57: | Line 65: |
| TDD is a design activity | TDD is a design activity ([[https://www.youtube.com/watch?v=d5Y1B1cmaGQ|DbC]]: Design by Coding) |
| Line 64: | Line 72: |
isolation use abduction. |
|
| Line 75: | Line 87: |
| 넘겨짚지 말고, 마술의 동작과 동작 사이를 잘 들여다보기. do not guess far. when you guess, validate it. |
|
| Line 79: | Line 95: |
| Here and now. recognize what's going on, inspect it, find root cause, and fix it. Don't wandering around searching web pages mindlessly. BDD, ATDD, SBE |
|
| Line 82: | Line 102: |
| take a look at extreme programming, not scrum, if you are a software developer. it includes a lot of effective technical principles. | If you are a software developer, you should consider extreme programming instead of scrum. It has many technical principles that can improve your work. |
| Line 87: | Line 107: |
| [[http://agile.egloos.com/5904102|협업의 미신]] | [[http://agile.egloos.com/5904102|협업의 미신]] ([[https://www.youtube.com/watch?v=I4xkw_0XqAs|영상]]) |
| Line 89: | Line 109: |
| [[https://twitter.com/kentbeck/status/1375936309458464769|pull request anti pattern]] | pull request anti pattern: [[https://twitter.com/kentbeck/status/1375936309458464769|Kent's twit]]. [[https://jessitron.com/2021/03/27/those-pesky-pull-request-reviews/|Those pesky pull request reviews]]. [[기술문서모음/PR과 코드리뷰|PR과 코드리뷰]]. |
| Line 93: | Line 113: |
| * Kent Beck, Extreme Programming Explained | * Kent Beck, [[책/ExtremeProgrammingExplained]] |
| Line 108: | Line 128: |
| ---- |
Contents
use data to make logic simple
- make DSL
- do not mix logic and data construction
Proverbs
Philosophy, Viewpoint, Programmer
책
last 5% automation
craft, not science
SoftwareArchitecture. AOSA prefaces.
The Eisenhower Matrix
Make it work, then make it better.
problem space, solution space
...
Philosophy, Viewpoint, Programmer: Advanced
programming is to make a language system. make vocabulary. take a look at Peter Norvig's code (pattern language, lisp hackers)
- SICP
- 패턴, 위키, 그리고 XP
Programming fundamental
공통점과 차이점 찾기. 공통점을 공유하고, 차이점을 처리할 수 있는 기법을 습득한다. (OOP 다형성, 고차함수 등)
책
- Refactoring 2/E
- Kent Beck, Implementation Patterns
- Robert Martin, Agile Software Development
TDD, Baby step, Evolutionary Design
Baby Step
quickly step back to closest green-bar when you see red bar
TDD is a design activity (DbC: Design by Coding)
short feedback cycle (loop)
bowling kata by robert martin
micro commit, one at a time
isolation
use abduction.
책
- Kent Beck, Test Driven Development
- Specification by Examples
Testing & Debugging
eliminate/reduce intermediate layers
넘겨짚지 말고, 마술의 동작과 동작 사이를 잘 들여다보기.
do not guess far. when you guess, validate it.
regression test
Here and now. recognize what's going on, inspect it, find root cause, and fix it. Don't wandering around searching web pages mindlessly.
BDD, ATDD, SBE
Collaboration
If you are a software developer, you should consider extreme programming instead of scrum. It has many technical principles that can improve your work.
pair programming: perform outstanding with other juniors
pull request anti pattern: Kent's twit. Those pesky pull request reviews. PR과 코드리뷰.
책
Kent Beck, 책/ExtremeProgrammingExplained
Learning, Expertise
To learn well from experts (CTA, CDE)
- 실용주의 사고와 학습
See Also: 프로그래밍 추천 도서