Gary Hall – författare

How philosophers and theorists can find new models for the creation, publication, and dissemination of knowledge, challenging the received ideas of originality, authorship, and the book.

In Pirate Philosophy, Gary Hall considers whether the fight against the neoliberal corporatization of higher education in fact requires scholars to transform their own lives and labor. Is there a way for philosophers and theorists to act not just for or with the antiausterity and student protestors—“graduates without a future”—but in terms of their political struggles? Drawing on such phenomena as peer-to-peer file sharing and anticopyright/pro-piracy movements, Hall explores how those in academia can move beyond finding new ways of thinking about the world to find instead new ways of being theorists and philosophers in the world.

Hall describes the politics of online sharing, the battles against the current intellectual property regime, and the actions of Anonymous, LulzSec, Aaron Swartz, and others, and he explains Creative Commons and the open access, open source, and free software movements. But in the heart of the book he considers how, when it comes to scholarly ways of creating, performing, and sharing knowledge, philosophers and theorists can challenge not just the neoliberal model of the entrepreneurial academic but also the traditional humanist model with its received ideas of proprietorial authorship, the book, originality, fixity, and the finished object. In other words, can scholars and students today become something like pirate philosophers?

It is now recognized that any non-trivial WPF or Silverlight application needs be designed around the Model-View-ViewModel (MVVM) design pattern in order to unlock the technology''s full data-binding potential. 

However, the knowledge of how to do this is missing from a large part of the development community—even amongst those who work with WPF and Silverlight on a daily basis. Too often there is a reliance on programmatic interaction between controls and not enough trust in the technologies'' data-binding capabilities. This leads to a clouding of design values and an inevitable loss of performance, scalability, and maintainability throughout the application.

Pro WPF and Silverlight MVVM will show you how to arrange your application so that it can grow as much as required in any direction without danger of collapse.

Write code that can adapt to changes.

By applying this book’s principles, you can create code that accommodates new requirements and unforeseen scenarios without significant rewrites. Gary McLean Hall describes Agile best practices, principles, and patterns for designing and writing code that can evolve more quickly and easily, with fewer errors, because it doesn’t impede change.

Now revised, updated, and expanded, Adaptive Code, Second Edition adds indispensable practical insights on Kanban, dependency inversion, and creating reusable abstractions. Drawing on over a decade of Agile consulting and development experience, McLean Hall has updated his best-seller with deeper coverage of unit testing, refactoring, pure dependency injection, and more.

Master powerful new ways to:

• Write code that enables and complements Scrum, Kanban, or any other Agile framework

• Develop code that can survive major changes in requirements

• Plan for adaptability by using dependencies, layering, interfaces, and design patterns

• Perform unit testing and refactoring in tandem, gaining more value from both

• Use the “golden master” technique to make legacy code adaptive

• Build SOLID code with single-responsibility, open/closed, and Liskov substitution principles

• Create smaller interfaces to support more-diverse client and architectural needs

• Leverage dependency injection best practices to improve code adaptability

• Apply dependency inversion with the Stairway pattern, and avoid related anti-patterns

About You

This book is for programmers of all skill levels seeking more-practical insight into design patterns, SOLID principles, unit testing, refactoring, and related topics. Most readers will have programmed in C#, Java, C++, or similar object-oriented languages, and will be familiar with core procedural programming techniques.