- Paperback: 304 pages
- Publisher: Yahoo Press; 1 edition (March 18, 2010)
- Language: English
- ISBN-10: 0596803028
- ISBN-13: 978-0596803025
- Product Dimensions: 7 x 0.6 x 9.2 inches
- Shipping Weight: 12.8 ounces (View shipping rates and policies)
- Average Customer Review: 6 customer reviews
- Amazon Best Sellers Rank: #532,065 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Developing Large Web Applications: Producing Code That Can Grow and Thrive 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
"Children of Blood and Bone"
Tomi Adeyemi conjures a stunning world of dark magic and danger in her West African-inspired fantasy debut. Learn more
Frequently bought together
Customers who viewed this item also viewed
Customers who bought this item also bought
Producing Code That Can Grow and Thrive
About the Author
Kyle Loudon is a software developer at Yahoo! where he leads a group doing user interface development. Some of Kyle's experiences prior to joining Yahoo! include working on the user interface for the original Apple iPod, writing software for various other mobile devices, and leading the user interface group at Jeppesen Dataplan (a Boeing company) in the development of a flight planning system used by airlines around the world. He also spent a small amount of time with IBM in the early 1990s. For several years, he has taught object-oriented programming part-time at the University of California, Santa Cruz while working as a software developer in Silicon Valley.
Kyle received a B.S. in Computer Science from Purdue University in 1992 with a minor in French, and was elected there to the Phi Beta Kappa honor society. He has also done some advanced education in Computer Science at Stanford University.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
tl;dr - has some stuff you should know, but better to let a framework(s) do it for you.
Even though the book is only a few years old, I was reminded of how very fast the web changes by how dated some of the material seems. For example there are discussions of XHTML and XML (hybrids, validation, closing slashes, etc.), and of HTML vs. CSS (for example HTML tags one should never use.) Clearly it hews to the old master paradigm of web pages that hyperlink to other web pages, including applications being constructed of a sequence of web pages. The newer master paradigm of "single page applications" is never even mentioned as a future possibility. This shows clearly in the "slideshow" example, which requests a brand new complete web page from the server every time the screen flips to a new picture.
I was interested in knowing more about the care and feeding of well-known websites: How does one roll out new code into a live production website? How does one monitor its action, and back it out quickly and cleanly if there's a problem? How are these things done differently if the content is delivered by a CDN (with the website basically "mirrored" tens or hundreds of places)? What protections are necessary to keep developers from inadvertently breaking production websites while they're making improvements? What sorts of source control systems are needed? Which kinds of code should be kept in source control systems, and where should those systems be? What sort of real-time monitoring is necessary? How does one arrange to find out "we have a problem" a comfortable length of time _before_ "our website has gone completely off the air"? How does one measure usability, and the effect of changes on it? (For example Google found that a difference of only 100ms in response time, although completely undetectable by an individual, had a measurable impact on the reactions of large groups of users. How does one find out similar things?)
One of the good points is that uses examples about what is talking about, examplify them, and mention other tools and external sources. Applies too the concepts of the "Even faster websites" book and explaining why the code is that way.
The bad point is that soon or later returns to YUI (Yahoo! Interface Library) maybe because he was the depeloper leader; but in some chapter is overuse of it, in others the way it is applied is not exclusive of the library. It needs more 'equilibrium' on it, les recurrent.
Sometimes it looks like a "how i implement the solution at Yahoo!", but give good clues to make our own choices
Un buen libro, se enfoca en como los grandes sitios web funcionan. Es un libro cuyos capítulos deben ser leidos en orden, ya que siempre hay referencia a los capítulos previos; como es el caso del último capítulo, donde agrupa todo lo generado en los capítulos anteriores.
Se enfoca en temas como arquitectura, consistencia, modularidad, y otros elementos basados en php, js, css y html. En mi opinión, hace un sobre uso de OOPc, pero es meramente mi opinión.
Uno de los puntos de interés, es que usa ejemplos acerca de lo que trata, ejemplificando su uso y mencionando otras herramientas provenientes de terceros. Aplica igualmente algunos de los conceptos mencionados en el libro "Even faster websites" indicando como son llevados.
El punto negativo, es que tarde o temprano siempre regresa a YUI (Yahoo! Interface Library) tal vez porque era el líder de desarrollo, pero en uno de los capítulos hace un sobreuso de ello, mientras que en otro lo menciona código como si fuese exclusivo de la librería, siendo que no es así. Se requiere equilibrar esos puntos.
Algunas veces parece un "Como implementé la solución en Yahoo!", pero ofrece algunas pistas interesantes para uno tomar sus propias decisiones.