2009.02.22 21:18:52 105일만에 뒤집기 하다

하람엄마의 말에 의하면 열심히 시도하더니만 성공했단다…

---

[ 2009.02.27 20:26:56 Architects Must Write Code ]

40대가 되면서 IT종사자로서 고민되는 것중에 하나가

언제까지 프로그램언어를 이용해서 업무시스템구현하는 것을 할 수 있을 것인가?

실제 내가 가지고 있는 기술셋을 가지고 구현을 하는 것은 많은 즐거움을 준다.

하지만 조직은 연륜(단순히 나이가 많아지면)이 생기면 관리를 원한다..

이런 부분을 고민하는 중에 재밌는 글을 읽었다..

 Powerpoint architects

딱 우리 현실에 맞는 애기다. 다들 작업툴이 파워포인트다..ㅋㅋ

..이런 부분을 고민하는 중에 재밌는 글을 읽었다..

Architects Must Write Code

I had the opportunity to read Practices of an Agile Developer: Working in the Real World. The book has 45 tip to help developers become agile. And, it’s clear that Venkat and Andy know the problems of becoming an agile developer, because along with each tip, there’s a devil-thought to show people what happens in the real world. There are also angel-thoughts to show people why this tip works.

My favorite tip, and something I’ve been saying in my assessment reports for the last 10 years is “Architects Must Write Code.” (p. 155 in this book.) Venkat and Andy say this about ineffective architects:

They typically come in during the beginning of a project, draw all kinds of diagrams, and leave before any serious implementation takes place. There are many “Powerpoint architects” out there, and they aren’t effective because of lack of feedback.

I’ve been a part of projects for 30 years. I’ve been assessing projects for 10 years. And every time I’ve seen an architect who doesn’t participate in the code-writing part of the project, I’ve seen an architecture that doesn’t do what it’s supposed to do, never mind extend to inevitable changes in requirements that occur during the project.

Architects need feedback about their architecture. The only way to get feedback is to write the code, integrate it, and see what happens.

---

[ 2009.11.07 15:00:23 하람이 돌잔치 초대장.]

벌써 1년이 지났다…