nakedsushi's review against another edition
3.0
Ellen Ullman perfectly describes how a programmer relates to the world in this book. That's not to say only programmers should read this. Instead, I recommend non-programmers who ever have to work with programmers read this book because it describes why we're always cranky: half the time, nothing is working and the other half, we have no idea what we're doing.
She writes:
The corollary of constant change is ignorance. This is not often talked about: we computer experts barely know what we're doing. We're good at fussing and figuring out. We function well in a sea of unknowns. Our experience has only prepared us to deal with confusion. A programmer who denies this is probably lying, or else is densely unaware of himself.
The short version:
That said, although most of what Ullman describes rings true, there are some things I can't relate with because I was never a programmer in the 80s or even 90s and I never worked in a really corporate atmosphere. While she found that working as a contractor or consultant and not a "real" employee made her feel isolated, I wonder if this was a time before instant-messaging, Skype, and all the myriad of ways to real-time contact with remote-coworkers.
I definitely enjoyed the chapters about her work life more than the chapters of her love-life. I know this is probably supposed to be more like a memoir, but I found the chapters about Brian to be dull and wished she would just get over him. Also, there was by far, the least erotic sex-scene ever early on in this book, just a warning!
She writes:
The corollary of constant change is ignorance. This is not often talked about: we computer experts barely know what we're doing. We're good at fussing and figuring out. We function well in a sea of unknowns. Our experience has only prepared us to deal with confusion. A programmer who denies this is probably lying, or else is densely unaware of himself.
The short version:
That said, although most of what Ullman describes rings true, there are some things I can't relate with because I was never a programmer in the 80s or even 90s and I never worked in a really corporate atmosphere. While she found that working as a contractor or consultant and not a "real" employee made her feel isolated, I wonder if this was a time before instant-messaging, Skype, and all the myriad of ways to real-time contact with remote-coworkers.
I definitely enjoyed the chapters about her work life more than the chapters of her love-life. I know this is probably supposed to be more like a memoir, but I found the chapters about Brian to be dull and wished she would just get over him. Also, there was by far, the least erotic sex-scene ever early on in this book, just a warning!
geekypete's review
4.0
A unique perspective of the late 80's silicon valley culture from a communist cum capitalist. It was a bit scattered/stream of consciousness at times, but it does an excellent job of portraying the ideological clash between software developers and those that employ them.
nora__reads's review against another edition
challenging
informative
inspiring
reflective
medium-paced
4.0
I feel that Ellen Ullman is the modern Ada Lovelace, an incredible technical mind mixed with the heart of a poet - an incredible book
jacalata's review
4.0
An interesting read, basically a short window into what feels like a long time ago (1997) with a lot of descriptions of programmers/work/companies that could easily be applied today and a few that are startlingly historic.
luckypluto's review against another edition
4.0
Ellen Ullman’s novel The Bug is one of my favorite books, and I was excited to read Close to the Machine, her memoirs about working in Silicon Valley. Ullman’s take on the tech world is uniquely refreshing and mirrors my own in some key ways, and I think she offers a unique insight on the industry that is valuable for any software developer.
Close to the Machine did not disappoint. It was a fabulously interesting read, and while it only covers a short swath of Silicon Valley history, it is rich with insight and intelligence—a break from the usual feel-good tripe written about software development. Admittedly, some parts of it were a bit slow, particularly where she waxes philosophical about the nature of contract work, but overall I found it to be edifying and worth the time I put into it.
While she has plenty of articles floating around, her only other book (that I haven’t read) is By Blood. I’m impressed enough by both Close to the Machine and The Bug that I may just give By Blood a go at some point.
Close to the Machine did not disappoint. It was a fabulously interesting read, and while it only covers a short swath of Silicon Valley history, it is rich with insight and intelligence—a break from the usual feel-good tripe written about software development. Admittedly, some parts of it were a bit slow, particularly where she waxes philosophical about the nature of contract work, but overall I found it to be edifying and worth the time I put into it.
While she has plenty of articles floating around, her only other book (that I haven’t read) is By Blood. I’m impressed enough by both Close to the Machine and The Bug that I may just give By Blood a go at some point.