Download PDF Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg
Download PDF Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg
Now, supplying the books for you is kind of vital thing. It will certainly certainly aid you to find the book quickly. When you really need the book with the same topic, why do not you take Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg currently as well as below? It will not be so hard. It will be so easy to see exactly how you intend to discover the book to read. The presentation of people who enjoy this book to check out is a lot better.
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg
Download PDF Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg
In this age of contemporary period, making use of net must be made the most of. Yeah, net will certainly help us very much not only for vital thing but also for everyday tasks. Many people now, from any type of degree could make use of internet. The sources of internet connection can additionally be appreciated in lots of locations. As one of the benefits is to obtain the internet book, as the world window, as many people suggest.
Why should be this publication? It's all that you need currently. Or perhaps you do not need the message of this publication directly currently, you could find the benefit some day. Someday, you will feel that you are truly fortunate to find Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg as one of your reading materials. If you start to feel it, possibly, you can't advise about this book and also can't locate where this publication is. For this reason, you could check out once again this book in this web site, a site with million catalogues of the books.
And also why should read this book? Many know that in this era, some publications are covered in hefty things to load. Some other will certainly be also complemented in language problem to comprehend. Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg is among the most recent released publications that has simple concept of assumed with amazing truths and also lessons. It will show you couple of things simple with easy language to recognize. Also you are from the foreigners, this book is likewise simple sufficient to be equated.
Be the very first to get this publication now and obtain all reasons you require to read this Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg Guide Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg is not simply for your responsibilities or necessity in your life. Publications will consistently be an excellent buddy in every time you review. Now, let the others learn about this page. You can take the benefits as well as discuss it likewise for your pals and also individuals around you. By through this, you can really get the significance of this publication Dreaming In Code: Two Dozen Programmers, Three Years, 4,732 Bugs, And One Quest For Transcendent Software, By Scott Rosenberg profitably. Exactly what do you consider our suggestion right here?
Amazon.com Review
In the 80s, Tracy Kidder's The Soul of a New Machine attempted to define the story of the development of a minicomputer: from the new science to the business and nascent culture of electronic hardware and software that was characteristic of that time. Scott Rosenberg's Dreaming in Code draws on Kidder's model as it attempts to document the state of software, the Internet, and everything circa 2006 through the lens of Chandler, an as-yet-unfinished software application for the management of personal information. The Chandler project--driven by Mitch Kapor, the founder of Lotus Development and main designer of its 1-2-3 spreadsheet, and later co-founder of the Electronic Frontier Foundation--isn't the primary point of Dreaming in Code, though reading about software people and their social behavior is at least as interesting as reading about that of meerkats or monkeys. Rather, Chandler is a rhetorical device with which Rosenberg takes on the big questions: How do software development teams work (or not)? Why does the reuse of software modules rarely work altogether correctly? Does open-source development by volunteers on the Internet lead to innovation or just insanely bifurcated chaos? Chandler helps his readers think more clearly about all of these issues; however, "answers" to these questions are, of course, not to be had, which is one of his points. The problem with books about technical subjects that aspire to appeal to a general audience, particularly computers and software, is that such subjects are so far outside the realm of familiarity of most people that the prose bogs down in analogy and metaphor. Rosenberg manages to avoid too much of that and deliver a readable account of software development and culture. --David Wall
Read more
From Publishers Weekly
Software is easy to make, except when you want it to do something new," Rosenberg observes—but the catch is that "the only software worth making is software that does something new." This two-tiered insight comes from years of observing a team led by Mitch Kapor (the creator of the Lotus 1-2-3 spreadsheet) in its efforts to create a "personal information manager" that can handle to-do lists as easily as events scheduling and address books. Rosenberg's fly-on-the-wall reporting deftly charts the course taken by Kapor's Open Source Applications Foundation, while acknowledging that every software programmer finds his or her own unique path to a brick wall in the development process. (The software is still in development even now.) With equal enthusiasm, Rosenberg digs into the history of the computer industry's efforts to make programming a more efficient process. Though there's a lot of technical information, it's presented in very accessible terms, primarily through the context of project management. Even readers whose computer expertise ends at retrieving their e-mail will be able to enjoy digressions into arcane subjects like object-oriented programming. (Jan.) Copyright © Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
Read more
See all Editorial Reviews
Product details
Hardcover: 416 pages
Publisher: Crown; First Edition edition (January 16, 2007)
Language: English
ISBN-10: 1400082463
ISBN-13: 978-1400082469
Product Dimensions:
6.2 x 1.4 x 9.6 inches
Shipping Weight: 1.5 pounds
Average Customer Review:
3.9 out of 5 stars
105 customer reviews
Amazon Best Sellers Rank:
#501,318 in Books (See Top 100 in Books)
"Dreaming on Code" are two books mixed together into one. One of the books is the observation of the author of a multi-year high-profile software development project. The project eventually failed, but that wasn't clear yet at the end of the book. The second book is the authors search for better ways of developing software. The book is structured as a few pages about the development project and a few pages of exploration.For me, the book about the software project was the most interesting. The project is called Chandler done by a company called Open Source Applications Foundation (OSAF) by Mitch Kapor (the founder of Lotus). It's vision is to develop the next generation personal information manager (PIM), which is basically a calendar, email and note-maker integrated in one product. Chandler had a large investment and attracted some high-profile developers. Scott Rosenberg followed the Chandler project over a couple of years and the book describes his observations or narrative of the project.The Chandler project is fascinating as they aim to do things different... and end up making all the mistakes of traditional software projects. They want to get something out quickly and facilitate an open source community to build up the product. They end-up over-designing, late delivering and over-complicating the whole project. It is really painful to follow the project (at least for me) as I could see them make the mistakes and would want to say "nooo!" but they did it anyways. Eventually the book ends without knowing the end of Chandler, but if you search online you'll discover that it unfortunately never delivered its vision.The second book is the authors search for delivering better software. He basically picks a theme and describes that and explains some of the history. For example, at some point it explains what open source is and how open source was created. Similarly, it explains lots of aspects of software development. Most of these ought to be nothing new for nearly any software developer... and it suggests the book is actually targeted to people who aren't directly involved in software development but are curious about how it would work. The explorations were interesting but purposefully shallow, which made them a bit boring for me. Usually I ended up reading through them and wanting to go back to the Chandler project story to know what would happen there.All in all, the book was well written. I enjoyed the Chandler parts a lot (4 stars) and felt the explorations were just ok (3 stars). I decided to average it out to 3 stars, especially for software developers who probably know all the explorations already. 4 stars for people who are interested in discovering more about software development. A pretty ok book.
This book is likely to be of interest to developers and systems professionals, as well as a few others who are really interested in software development but don't participate in it actively. This latter group is the luckier one: for the rest of us, watching this train wreck in slow motion is painful and frequently exasperating.There are two distinct matters to be discussed here: 1) the principle story of the book, and 2) how the subject matter is delivered.The principle story of the book is Chandler, a Personal Information Manager(PIM)/Groupware-type software that was conceived and developed as an open-source project. The project was abandoned after several years' effort without having achieved its defining goals, and Dreaming is a narrative of the first few years.The blame for the failure must be place squarely at feet of the project's founder and chief evangelist, Mitch Kapor. Mr. Kapor was the heroic developer of Lotus 1-2-3. For the growing number of you who have no idea what that was, it was the one app that made a PC worth having in the late 80s. It was the killer app for a long time.Chandler was meant to be Kapor's extension of a PIM product that had once shown some promise at Lotus. He had the lofty idea of making this system capable of tying together all of the elements of PIM practice (calendar, task list, email, notes) into a seamless, ephemeral whole, without storage dictated by data type, and by the way, open source. Get it? Well, nobody else did either.This project failed because its goal could not and cannot be articulated in a short sentence. It was consistently defined by its desired attributes, without the faintest idea of how it could be achieved. In fact, when examined more closely the defining attributes seemed to be in direct contradiction to each other.If you will forgive me, the situation reminded me a lot of the health care bill of 2010. It was just forever before there ever was a bill. For at least two years, it existed as list of lofty attributes. For the few brief moments between the time it actually became a bill and the time it was passed into law, the Speaker of the House famously noted that we have to pass it to see what's in it. But when it was finally dissected, it contained a number of conflicting requirements that could not live together successfully.And so it was with Chandler. I marvel at the fact that in the august collection of software professionals, no one at any point pitched a fit that the project had no clearly articulated mission, that they had not a clear image of what they were building, and how such building would occur. I presume it is because that in this particular open-source project, the developers were getting paid.The open source idea was intended to harness the executional capacity of the masses, but again, the project was too ethereal for the masses to work on. There was no unifying mantra, such as "Write a free Unix!" or "Replace IIS!", for the masses to recite in unison. A candidate cry might have been "Replace Outlook!", but Chandler was meant to be so much *more* than Outlook. Unfortunately, "Transcend Outlook!" just never caught on. So Kapor paid a number of available systems development heavy hitters to develop the open-source project. Most of them moved along to other pastures once they saw that the emperor was in fact naked.And all of that is pity, but again, the greater pity is that the disaster could not have been averted by a well-placed person pulling the emergency brake. In my experience in software development, you have a problem on your hands if your programmers start out by designing the splash screen. Similarly, that the software was named after the dog, the dog after the author, and the releases after the setting of the author's stories just makes me want to puke. Perhaps we could get the cart and the horse in the right order.***A number of reviewers of this book have noted that the book is just as unfocused and wandering as the software project, and that is true. It isn't entirely clear to me how it could have been otherwise, and moreover, it does not render the book unuseful. The father Berenstein Bear made an industry of showing the little tyke bear what not to do. Well, same here. Plus, the wandering captures the spirit of the endeavor.What I do not sufficiently hear in the review-o-sphere is the dramatic turn the book makes at chapter 9, into the history of software development methodologies and personalities. For 75 pages (a bit less than a quarter of the book), we get a fine tour of software craftsmanship over the decades. Along the way, every major title in software development (and not a few minor ones) is cataloged and discussed. This discussion and the attendant bibliography is easily worth the price of the book (and maybe worth the cost of reading the other 75% of the book),One issue the author had was when to stop the book, as the software never came to any cohesive point. So it just stopped, just like the software project did a couple of years later.I think the title was a poor choice. It has nothing whatever to do with the book except a tangential reference, and a great opportunity to say something conclusive about the project was lost. I suppose that the jury had not yet completely returned on the project when the book went to press, however, "The Road to Nowhere: Hazards of Following the Pied Piper" or "Good Money After Bad: How and Idea, a Bucket of Money, and a Dynamic Personality Weren't Enough," would have been a lot more on point.
The best aspect of "Dreaming in Code," by Scott Rosenberg, is the question it poses: why is developing software so hard? Why are software projects chronically late; why do so many fail? Rosenberg investigates that issue by embedding with the "Chandler" development team, in an open source project funded and led by multi-millionaire Mitch Kapor.Learning about Kapor, who founded Lotus Development Corporation and designed the wildly popular spreadsheet software, Lotus 1-2-3, was in itself enough to make this book a worthwhile read for me. Nevertheless, "Dreaming in Code" fails in its major objective. The faults of the Chandler project - chiefly, "paralysis by analysis" - should have been glaringly obvious from the start, in 2001. It is little surprise that a project will be late or worse when it lacks a clear objective. What is atypical about Chandler is that it took so long to peter out. Its failure is a reminder that having a sugar daddy and no deadlines is more a prescription for failure than success.Rosenberg monitored the work on Chandler for three years before he called it quits and wrote his book. Since then, Mitch Kapor has left the project, and withdrew funding in 2008. Chandler is available for download, but shows no sign of being the world-changing software tool that it was hoped to be.
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg PDF
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg EPub
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg Doc
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg iBooks
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg rtf
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg Mobipocket
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, by Scott Rosenberg Kindle
Tidak ada komentar:
Posting Komentar