Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    In this concise book, JavaScript expert Cody Lindley (jQuery Cookbook) provides an accurate view of the language by examining its objects and supporting nuances.Libraries and frameworks help you build web applications quickly and efficiently, but when things go wrong or performance becomes an issue, knowing how and why they work is critical. If you're ready to go under the hood and get your hands dirty with JavaScript internals, this is your book. Get a short and digestible summary of ECMA-262, Edition 3, backed by real code you can run instantly Examine the creation of JavaScript objects Learn complex values, primitive values, scope, and inheritance Understand the importance of the head object Work with string, number, and Boolean objects and values Discover how to use the null value and the built-in math object Get into the details--beyond Mozilla's reference guide for JavaScript 1.5

    It covers various topics which include converting an HTML-based design to a pure positioning layout; styling a photo gallery; and others.

    Lead your team as a software architect, ask the right stakeholders the right questions, explore design options, and help your team implement a system that promotes the right -ilities. Share your design decisions, facilitate collaborative design workshops that are fast, effective, and fun-and develop more awesome software!With dozens of design methods, examples, and practical know-how, Design It! shows you how to become a software architect. Walk through the core concepts every architect must know, discover how to apply them, and learn a variety of skills that will make you a better programmer, leader, and designer. Uncover the big ideas behind software architecture and gain confidence working on projects big and small. Plan, design, implement, and evaluate software architectures and collaborate with your team, stakeholders, and other architects. Identify the right stakeholders and understand their needs, dig for architecturally significant requirements, write amazing quality attribute scenarios, and make confident decisions. Choose technologies based on their architectural impact, facilitate architecture-centric design workshops, and evaluate architectures using lightweight, effective methods. Write lean architecture descriptions people love to read. Run an architecture design studio, implement the architecture you've designed, and grow your team's architectural knowledge. Good design requires good communication. Talk about your software architecture with stakeholders using whiteboards, documents, and code, and apply architecture-focused design methods in your day-to-day practice. Hands-on exercises, real-world scenarios, and practical team-based decision-making tools will get everyone on board and give you the experience you need to become a confident software architect.

    The Lean Startup movement is very promising, but for many teams it ends up translating into an important question: ”Yeah, but what to build ?” “In ThoughtWorks, our response has been a process called an inception. We gather together a good sample of the people who will be affected by the product and have an intensive session to set an initial direction, using a series of exercises focusing on collaboration and the capture of broad goals. We don't attempt a detailed specification, as that is exactly the kind of thing that becomes out of date as soon as code hits production. But we do want to understand what kind of outcomes we are hoping for, the features that we think will drive these outcomes, and how to assess the effectiveness of our product. With The Lean Inception, Paulo has captured his experience in running these inceptions over the last decade. In particular it's focused on his work to boil the inception down to its essence, concentrating the activity on a single, if very intensive, week of work. Paulo shares how he makes this work, through writing a product vision, capturing personas, understanding the user journeys, and developing high-level features. The result isn't a detailed plan of work, which we find quickly rots into irrelevance. It is a guiding set of goals to set us off in the right direction. It doesn't plan out a final product, with all the features that our users will need, instead it focuses on an initial product that we can release and learn from - the Minimum Viable Product. “ – Martin Fowler, Chief Cientist at ThoughtWorks

    With expanded coverage of ethics, analysis processes, and approaches, authors Catherine Marshall and Gretchen B. Rossman, have updated this highly popular text to reflect the advances and challenges presented by provocative developments and new applications since the previous edition.

    I would love to write that book, but at this time I have no indication that such a book would be worth writing. Most books fail in the market, and most of them fail not because they are poorly written or edited, but because there aren’t enough people interested in them. They are not the right it.What you are reading now is a pretotype edition of the book. I wrote and “edited” it in days instead of months, just to test the level of interest in such a book. I had a few friends and colleagues review it, but don’t be surprised if you find typos, misspellings, bad grammar, awkward formatting and all sorts of misteaks.Releasing it in its present state is not easy for me.The toughest thing about pretotyping is not developing pretotypes, that’s the fun part. The tough part is getting over our compulsion for prema- ture perfectionism and our desire to add more features, or content, before releasing the first version. The tough part is getting our pretotypes in front of people, where they will be judged, criticized and – possibly – rejected.Reid Hoffman, founder of LinkedIn once said: “If you are not embarrassed by the first version of your product, you’ve launched too late.”I am plenty embarrassed. I must be on the right track.http://www.pretotyping.org/pretotype-...

    Today, most developers acknowledge the benefits of unit testing and rely on the increasingly sophisticated tools now available. The recently released JUnit 4.5 represents the state of the art in unit testing frameworks, and provides significant new features to improve the Java development process.JUnit in Action, Second Edition is an up-to-date guide to unit testing Java applications (including Java EE applications) using the JUnit framework and its extensions. This book provides techniques for solving real-world problems such as testing AJAX applications, using mocks to achieve testing isolation, in-container testing for Java EE and database applications, and test automation.Written to help readers exploit JUnit 4.5, the book covers recent innovations such as the new annotations that simplify test writing, improved exception handling, and the new assertion methods. You'll also discover how to use JUnit extensions to test new application styles and frameworks including Ajax, OSGi, and HTML-based presentation layers.Using a sample-driven approach, various unit testing strategies are covered, such as how to unit test EJBs, database applications, and web applications. Also addressed are testing strategies using freely available open source frameworks and tools, and how to unit test in isolation with Mock Objects. The book will also bring you up to speed on the latest thinking in TDD, BDD, Continuous Integration, and other practices related to unit testing.

    But how do you choose the right words? And how do you know if they work? With this practical book, you'll learn how to write strategically for UX, using tools to build foundational pieces for UI text and UX voice strategy.UX content strategist Torrey Podmajersky provides strategies for converting, engaging, supporting, and re-attracting users. You'll use frameworks and patterns for content, methods to measure the content's effectiveness, and processes to create the collaboration necessary for success. You'll also structure your voice throughout so that the brand is easily recognizable to its audience.Learn how UX content works with the software development lifecycleUse a framework to align the UX content with product principlesExplore content-first design to root UX text in conversationLearn how UX text patterns work with different voicesProduce text that's purposeful, concise, conversational, and clear

    If you're looking for a book like that, put this one back on the shelf.Rework shows you a better, faster, easier way to succeed in business. Read it and you'll know why plans are actually harmful, why you don't need outside investors, and why you're better off ignoring the competition. The truth is, you need less than you think. You don't need to be a workaholic. You don't need to staff up. You don't need to waste time on paperwork or meetings. You don't even need an office. Those are all just excuses.  What you really need to do is stop talking and start working. This book shows you the way. You'll learn how to be more productive, how to get exposure without breaking the bank, and tons more counterintuitive ideas that will inspire and provoke you.With its straightforward language and easy-is-better approach, Rework is the perfect playbook for anyone who’s ever dreamed of doing it on their own. Hardcore entrepreneurs, small-business owners, people stuck in day jobs they hate, victims of "downsizing," and artists who don’t want to starve anymore will all find valuable guidance in these pages.

    The Pinch revolves around a single enchanted day containing years, during which the antics of a group of Jewish mystics threaten to ravage the life of general store proprietor Pinchas Pin with miracles, and his nephew Muni's ardor for an alluring tightrope walker collides with his passion for chronicling the wonders of North Main Street. Their stories, gleaned by a hapless bookseller from a fabulist history book, transform the fate of the neighborhood.

    Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users?If you're a developer and don't want to be on call for 3AM for the rest of your life, this book will help.In Release It!, Michael T. Nygard shows you how to design and architect your application for the harsh realities it will face. You'll learn how to design your application for maximum uptime, performance, and return on investment.Mike explains that many problems with systems today start with the design.

    Expert software designers have specific habits, learned practices, and observed principles that they apply deliberately during their design work. This book offers sixty-six insights, distilled from years of studying experts at work, that capture what successful software designers actually do to create great software.The book presents these insights in a series of two-page illustrated spreads, with the principle and a short explanatory text on one page, and a drawing on the facing page. For example, "Experts generate alternatives" is illustrated by the same few balloons turned into a set of very different balloon animals. The text is engaging and accessible; the drawings are thought-provoking and often playful.Organized into such categories as "Experts reflect," "Experts are not afraid," and "Experts break the rules," the insights range from "Experts prefer simple solutions" to "Experts see error as opportunity." Readers learn that "Experts involve the user"; "Experts take inspiration from wherever they can"; "Experts design throughout the creation of software"; and "Experts draw the problem as much as they draw the solution."One habit for an aspiring expert software designer to develop would be to read and reread this entertaining but essential little book. The insights described offer a guide for the novice or a reference for the veteran--in software design or any design profession.A companion web site provides an annotated bibliography that compiles key underpinning literature, the opportunity to suggest additional insights, and more.

    FLYOVERS. STREETS IN THE SKY. ONCE, THIS WAS THE FUTURE. Was Britain's postwar rebuilding the height of midcentury chic or the concrete embodiment of Crap Towns? John Grindrod decided to find out how blitzed, slum-ridden and crumbling 'austerity Britain' became, in a few short years, a space-age world of concrete, steel and glass. On his journey he visits the sleepy Norfolk birthplace of Brutalism, the once-Blitzed city centre of Plymouth, the futuristic New Town of Cumbernauld, Sheffield's innovative streets in the sky, the foundations of the BT tower, and the brave 1950s experiments in the Gorbals. Along the way he meets New Town pioneers, tower block builders, Barbican architects, old retainers of Coventry Cathedral, proud prefab dwellers and sixties town planners: people who lived through a time of phenomenal change and excitement. What he finds is a story of dazzling space-age optimism, ingenuity and helipads -- so many helipads -- tempered by protests, deadly collapses and scandals that shook the government. Concretopia is an accessible, warm and revealing social history of an aspect of Britain often ignored, insulted and misunderstood. It will change the way you look at Arndale Centres, tower blocks and concrete forever.

     At any given moment, somewhere in the world someone struggles with the same software design problems you have. You know you don't want to reinvent the wheel (or worse, a flat tire), so you look to Design Patterns--the lessons learned by those who've faced the same problems. With Design Patterns, you get to take advantage of the best practices and experience of others, so that you can spend your time on...something else. Something more challenging. Something more complex. Something more fun. You want to learn about the patterns that matter--why to use them, when to use them, how to use them (and when NOT to use them). But you don't just want to see how patterns look in a book, you want to know how they look "in the wild". In their native environment. In other words, in real world applications. You also want to learn how patterns are used in the Java API, and how to exploit Java's built-in pattern support in your own code. You want to learn the real OO design principles and why everything your boss told you about inheritance might be wrong (and what to do instead). You want to learn how those principles will help the next time you're up a creek without a design pattern. Most importantly, you want to learn the "secret language" of Design Patterns so that you can hold your own with your co-worker (and impress cocktail party guests) when he casually mentions his stunningly clever use of Command, Facade, Proxy, and Factory in between sips of a martini. You'll easily counter with your deep understanding of why Singleton isn't as simple as it sounds, how the Factory is so often misunderstood, or on the real relationship between Decorator, Facade and Adapter. With Head First Design Patterns, you'll avoid the embarrassment of thinking Decorator is something from the "Trading Spaces" show. Best of all, in a way that won't put you to sleep! We think your time is too important (and too short) to spend it struggling with academic texts. If you've read a Head First book, you know what to expect--a visually rich format designed for the way your brain works. Using the latest research in neurobiology, cognitive science, and learning theory, Head First Design Patterns will load patterns into your brain in a way that sticks. In a way that lets you put them to work immediately. In a way that makes you better at solving software design problems, and better at speaking the language of patterns with others on your team.