올해안에 디자인 패턴(Design Pattern)책 2번 읽기 목표를 두고 실행해보겠습니다.
이제 개발자로서의 어느정도 경력도 쌓였다보니, 개발능력의 향상을 위해 디자인 패턴(Design Pattern)책을 2번 읽어봐야겠습니다.
| 도서정가제 시행전 한빛미디어에서 나온 책 50%할인 구입. (0) | 2014.11.17 |
|---|---|
| 2014년 9월 8일/9월 15일 합본 타임지(TIME誌)의 표지 "The Answers issue" (0) | 2014.09.08 |
| 이공계열, 그 몰락의 이유 - 한국의 이공계는 글쓰기가 두렵다 발췌 (0) | 2014.09.07 |
| "리뷰의 기술" 책 정리한 슬라이드 소개 (1) | 2014.08.14 |
| 미국 통신망 사업체들의 브로드밴드 전쟁 도표 (출처: 2014년 8월4일자 타임지[TIME誌]) (0) | 2014.08.01 |
Buy me a coffee
출처: Python-Patterns https://github.com/faif/python-patterns
A collection of design patterns and idioms in Python.
Current Patterns:
| Pattern | Description |
|---|---|
| 3-tier | data<->business logic<->presentation separation (strict relationships) |
| abstract_factory | use a generic function with specific factories |
| adapter | adapt one interface to another using a whitelist |
| borg | a singleton with shared-state among instances |
| bridge | a client-provider middleman to soften interface changes |
| builder | call many little discrete methods rather than having a huge number of constructor parameters |
| catalog | general methods will call different specialized methods based on construction parameter |
| chain | apply a chain of successive handlers to try and process the data |
| command | bundle a command and arguments to call later |
| composite | encapsulate and provide access to a number of different objects |
| decorator | wrap functionality with other functionality in order to affect outputs |
| facade | use one class as an API to a number of others |
| factory_method | delegate a specialized function/method to create instances |
| flyweight | transparently reuse existing instances of objects with similar/identical state |
| graph_search | (graphing algorithms, not design patterns) |
| iterator | structure repeated, identical calls as a generator |
| mediator | an object that knows how to connect other objects and act as a proxy |
| memento | generate an opaque token that can be used to go back to a previous state |
| mvc | model<->view<->controller (non-strict relationships) |
| observer | provide a callback for notification of events/changes to data |
| pool | preinstantiate and maintain a group of instances of the same type |
| prototype | use a factory and clones of a prototype for new instances (if instantiation is expensive) |
| proxy | an object funnels operations to something else |
| publish_subscribe | a source syndicates events/data to 0+ registered listeners |
| state | logic is org'd into a discrete number of potential states and the next state that can be transitioned to |
| strategy | selectable operations over the same data |
| template | an object imposes a structure but takes pluggable components |
| visitor | invoke a callback for all items of a collection |
ps. 조만간 디자인 패턴(Design Pattern)내용을 한글로 번역해서 정리해볼 예정
| 애자일 선언 이면의 원칙 (0) | 2014.07.04 |
|---|---|
| 애자일 소프트웨어 개발 선언 (0) | 2014.07.04 |
| DevOps 설명하는 슬라이드 (1) | 2014.07.02 |
| [JAVA] java.lang.UnsupportedClassVersionError 해결방법 (0) | 2014.06.20 |
| 문서 데이터베이스에서 사용하는 용어 (0) | 2014.06.19 |
Buy me a coffee
