What type of font to use? How big? How should those letters, words, and paragraphs be aligned, spaced, ordered, shaped, and otherwise manipulated? In this groundbreaking new primer, leading design educator and historian Ellen Lupton provides clear and concise guidance for anyone learning or brushing up on their typographic skills. Thinking with Type is divided into three sections: letter, text, and grid. Each section begins with an easy-to-grasp essay that reviews historical, technological, and theoretical concepts, and is then followed by a set of practical exercises that bring the material covered to life. Sections conclude with examples of work by leading practitioners that demonstrate creative possibilities (along with some classic no-no's to avoid).

    Working effectively to combat unconscious bias across differences such as gender, culture, generational, race, and sexual orientation not only leads to a more productive, innovative corporate culture but also to a better engagement with customers and clients. The Inclusion Dividend provides a framework to tap the bottom-line impact that results from an inclusive culture. Most leaders have the intent to be inclusive, however translating that intent into a truly inclusive outcome with employees, customers, and other stakeholders requires a focused change effort. The authors explain that challenge and provide straightforward advice on how to achieve the kind of meritocracy that will result in a tangible dividend and move companies ahead of their competition.

    We'll walk you through the key steps for every part of the process, and while it may seem repetitive at times, we want to make sure you have exactly the information you need, when you need it.And don't forget — this is a process! Publishing on Kindle is easy and takes only 5 minutes of your time — but correctly preparing your book for success on Kindle takes time and effort. Don't worry; if you follow the steps we outline here, you should feel confident you'll end up with a successfully designed and formatted book and one you will be proud to see for sale on Amazon.

    Instead you'll be able to absorb the most important content and begin applying it immediately after just one day!

    While some fear is healthy (often viewed as a conscience that tells programmers to be careful!), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.

    It is offered for sale in print format as a convenience.Get a head start evaluating Windows 8.1 - with early technical insights from award-winning journalist and Windows expert Ed Bott. Based on the Windows 8.1 Preview release, this guide introduces new features and capabilities, with scenario-based advice on how Windows 8.1 can meet the needs of your business. Get the high-level overview you need to begin preparing your deployment now.Preview new features and enhancements, including:How features compare to Windows 7 and Windows XP The Windows 8.1 user experience Deployment Security features Internet Explorer 11 Delivering Windows apps Recovery options Networking and remote access Managing mobile devices Virtualization Windows RT 8.1

    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

    Visual notetaking is the perfect skill for journaling, class lectures, conferences, and any other time that retaining information is key. Also referred to as sketchnoting, visual notetaking is ideal for documenting processes, planning projects, outlining ideas, and capturing information. And as you'll learn in The Art of Visual Notetaking, this approach doesn't require advanced drawing or hand-lettering skills; anyone can learn how to use simple lines, connectors, shapes, and text to take dynamic notes.   In The Art of Visual Notetaking, aspiring sketchnoters and journalers will find helpful "Getting Started" pages of icons and badges for common note-taking purposes, with tips and encouragement for creating you own unique icons. You'll go on to discover instruction and how-to techniques, tips, and tutorials that focus on visual notetaking for different settings, from a business meeting, workshop, or convention, to a college lecture or sermon. Expert instruction from a professional sketchnote artist and educator demonstrates how to visually arrange and compile ideas, focal points, and key concepts.

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    "

    Weissman does just that in Presentations in Action: 80 Memorable Presentation Lessons from the Masters. He teaches how to make spectacularly successful presentations by showing exactly how great presenters have done it. Weissman dives into his library of outstanding presentations, sharing examples from current events, politics, science, art, music, literature, cinema, media, sports, and even the military. His compelling examples don't just demonstrate what's universal about effective human communication: they also reveal powerful ways to solve the specific challenges presenters encounter most often. This book's five sections focus on each element of the outstanding contemporary presentation: Content: Mastering the art of telling your story; Graphics: Designing PowerPoint slides that work brilliantly; Delivery skills: How to make actions speak louder than words; Q&A: How to handle tough questions; Integration: How to put it all together. From clarifying "What's in it for you?" to crafting better elevator pitches, improving flow to using anecdotes, Presentation in Action is packed with solutions-and packed with inspiration, too!

    The goal of the book is to share the techniques of the best companies. This book is aimed primarily at Product Managers working on technology-powered products. That includes the hundreds of "tech companies" like Google, Facebook, Amazon, Twitter and the like, as well as the thousands of companies moving to leverage technology (financial companies, media companies, retailers, manufacturers, nearly every industry). Inspired covers companies from early stage start-ups to large, established companies. The products might be consumer products or devices, business services for small businesses to enterprises, internal tools, and developer platforms.Inspired is secondarily aimed at the designers, engineers, user researchers and data scientists that work closely with the product managers on product teams at these same companies.

    You think you can solve your human error problem by telling people to be more careful, by reprimanding the miscreants, by issuing a new rule or procedure. These are all expressions of 'The Bad Apple Theory', where you believe your system is basically safe if it were not for those few unreliable people in it. This old view of human error is increasingly outdated and will lead you nowhere. The new view, in contrast, understands that a human error problem is actually an organizational problem. Finding a 'human error' by any other name, or by any other human, is only the beginning of your journey, not a convenient conclusion. The new view recognizes that systems are inherent trade-offs between safety and other pressures (for example: production). People need to create safety through practice, at all levels of an organization. Breaking new ground beyond its successful predecessor, The Field Guide to Understanding Human Error guides you through the traps and misconceptions of the old view. It explains how to avoid the hindsight bias, to zoom out from the people closest in time and place to the mishap, and resist the temptation of counterfactual reasoning and judgmental language. But it also helps you look forward. It suggests how to apply the new view in building your safety department, handling questions about accountability, and constructing meaningful countermeasures. It even helps you in getting your organization to adopt the new view and improve its learning from failure. So if you are faced by a human error problem, abandon the fallacy of a quick fix. Read this book.

    This book draws on material Michael created for his renowned Object Mentor seminars, techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include: Understanding the mechanics of software change, adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform, with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structureThis book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    If you are an organization that really needs to start grokking UX this book is also for you. " -- Chris Bernard, User Experience Evangelist, Microsoft User experience design is the discipline of creating a useful and usable Web site or application--one that's easily navigated and meets the needs of both the site owner and its users. But there's a lot more to successful UX design than knowing the latest Web technologies or design trends: It takes diplomacy, project management skills, and business savvy. That's where this book comes in. Authors Russ Unger and Carolyn Chandler show you how to integrate UX principles into your project from start to finish. - Understand the various roles in UX design, identify stakeholders, and enlist their support- Obtain consensus from your team on project objectives- Define the scope of your project and avoid mission creep- Conduct user research and document your findings- Understand and communicate user behavior with personas- Design and prototype your application or site- Make your product findable with search engine optimization- Plan for development, product rollout, and ongoing quality assurance