읽고 싶은 책을 읽지 못하는 괴로움

오랫만에 돌아왔습니다 ^-^
아직도 새 제품 릴리즈 덕분에 밤낮으로 열심히 달리고 있습니다

그나저나 요즘 출판되는 책들이 많은데
손을 데지 못하고 있어서
개인적으로 가슴이 아픕니다 ...
특히나 이번에 한빛에서 정식 발매하는 O'Reilly
책들이 더욱 그러한데요.

잠깐 살펴 보기로 할까요?

제가 가장 읽고 싶은 책은 두권인데요

Beautiful Teams 와

97 Things Every Software Architect Should Know 입니다.

먼저 간단하게 책에 대해서 알아볼까요?
Beautiful Teams는 Beautiful Architecture와 비슷한 제목이라서 더욱 친숙한데요

What's it like to work on a great software development team facing an impossible problem? How do you build an effective team? Can a group of people who don't get along still build good software? How does a team leader keep everyone on track when the stakes are high and the schedule is tight?

Beautiful Teams takes you behind the scenes with some of the most interesting teams in software engineering history. You'll learn from veteran team leaders' successes and failures, told through a series of engaging personal stories -- and interviews -- by leading programmers, architects, project managers, and thought leaders.

전 왠지 이런 이야기를 읽으면
간접 경험을 하는 것 같은 느낌이 들어서 재밌더라구요

97 Things Every Software Architect Should Know 역시 비슷한 내용입니다.

In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de h ra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:

• Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar)
• Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm)
• Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards)
• Simplicity Before Generality, Use Before Reuse (Kevlin Henney)
• For the End User, the Interface Is the System (Vinayak Hegde)
• It's Never Too Early to Think About Performance (Rebecca Parsons)

To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.

아직 읽진 못했지만
Pragmatic Bookshelf에서 출판하고
위키북스에서 번역본을 출간한
마틴 파울러의
소트웍스 앤솔러지 같은 책들이 좋습니다.

다른 사람들의 경험담을 듣고
거기에서 필요한 것을 캐치하는 것은
은근히 재미 있는 작업이고, 저에게는
너무나 흥미로운 작업이거든요 ^^

사실 아직은 그렇게 얻은 정보를
특별하게 써먹을 곳이 있다던가 한 것은 아니지만
그런 사실보다는 하나의 지적 유희로써도
충분히 만족하기 때문에 좋아하고 있습니다.

뭐 제가 너무 쓸데없는 짓을 하고 있진 않은거죠? ^^

결론은 갱재가 빨리 나아져서
저희 가정도 살아났으면 하는 겁니다
그래야 책을 마음 놓고 사죠... ㅎ
(아! 환율도 좀 떨어졌으면...)