renkeyes

4 ms·

1.
by renkeyes 15y ago
I co-authored a chapter in "Beautiful Teams" at the urging of a friend, who was coordinating the project. Writing a chapter is quite a bit of work, so a book must be quite an undertaking. I feel that it's worth doing, though. Writing anythi
2.
by renkeyes 17y ago
In case you're curious, the Table of Contents are listed below: Copyright About the Author Preface Part I: Models of Designing Chapter 1. The Design Question Chapter 2. How Engineers Think of Design -- The Rational Model Chapter 3. What's W
3.
by renkeyes 17y ago
With NUMMI closing down any day now, "The Machine that Changed the World" by Womack, et al (1990) is almost as relevant now as it was then. The book describes the management and product development techniques used in the Japanese-owned auto
4.
by renkeyes 17y ago
I'd recommend "Crossing the Chasm" by Geoffrey A. Moore. It almost perfectly describes the lifecycle and challenges faced by the two software-product-based startups that I've worked for.
5.
by renkeyes 17y ago
Agreed, and SharePoint tends to be backed up on the DBMS backup schedule, which is usually more frequent than the file-share/NAS schedule, which is another bonus. It's the "non-sanctioned" aspect that tends to cause issues down the line, no
6.
by renkeyes 17y ago
Based on the implementation at my workplace, SP seems to have value as a hybrid intranet site and file share. Each department has their own section in which non-IT folks can create simple HTML content and can attach documents. It is also re
7.
by renkeyes 17y ago
I just saw this today...it might fit the bill: "Make: Electronics -- Learning Through Discovery" By Charles Platt; Released: December 2009 (est.) ; http://oreilly.com/catalog/9780596153755 "With this practical introductory guide, you'l