Bøger af Jay Fields

In yoga teacher training you are taught how to teach the yoga poses but not necessarily much about the art of teaching. Or perhaps I should say the heart of teaching-how to show up as a human being with all of your gifts, passions, fears and insecurities and teach the best class you can. Whether a total newbie to teaching or a seasoned veteran, the 12 Principles for Teaching People, Not Poses are pillars to support you in being a truly remarkable yoga teacher. 1. Be yourself. 2. Practice. 3. Show your vulnerability and your expertise. 4. Teach from your own experience. 5. If you don't know, say you don't know. 6. Stay in your body. 7. Don't take it all so seriously. 8. Remember that your students are people. 9. Learn anatomy. 10. Plan enough so that you can be spontaneous. 11. Remember who and what supports you. 12. Don't try to please everyone. With a chapter dedicated to each principle, stories from Jay's fourteen years of experience as a yoga teacher, teaching tips and questions for you to reflect upon about your own experience as a teacher, this book helps you to find the truth of your own teaching. In turn, you become the most confident, real and inspiring yoga teacher you can be.

This book details Jay Fields' strong opinions on the best way to test, while acknowledging alternative styles and various contexts in which tests are written. Whether you prefer Jay Fields' style or not, this book will help you write better Unit Tests. From the Preface: Over a dozen years ago I read Refactoring for the first time; it immediately became my bible. While Refactoring isn't about testing, it explicitly states: If you want to refactor, the essential precondition is having solid tests. At that time, if Refactoring deemed it necessary, I unquestionably complied. That was the beginning of my quest to create productive unit tests. Throughout the 12+ years that followed reading Refactoring I made many mistakes, learned countless lessons, and developed a set of guidelines that I believe make unit testing a productive use of programmer time. This book provides a single place to examine those mistakes, pass on the lessons learned, and provide direction for those that want to test in a way that I've found to be the most productive. The book does touch on some theory and definition, but the main purpose is to show you how to take tests that are causing you pain and turn them into tests that you're happy to work with.

The Definitive Refactoring Guide, Fully Revamped for Ruby With refactoring, programmers can transform even the most chaotic software into well-designed systems that are far easier to evolve and maintain. What's more, they can do it one step at a time, through a series of simple, proven steps. Now, there's an authoritative and extensively updated version of Martin Fowler's classic refactoring book that utilizes Ruby examples and idioms throughout-not code adapted from Java or any other environment. The authors introduce a detailed catalog of more than 70 proven Ruby refactorings, with specific guidance on when to apply each of them, step-by-step instructions for using them, and example code illustrating how they work. Many of the authors' refactorings use powerful Ruby-specific features, and all code samples are available for download. Leveraging Fowler's original concepts, the authors show how to perform refactoring in a controlled, efficient, incremental manner, so you methodically improve your code's structure without introducing new bugs. Whatever your role in writing or maintaining Ruby code, this book will be an indispensable resource. This book will help you • Understand the core principles of refactoring and the reasons for doing it • Recognize "bad smells” in your Ruby code • Rework bad designs into well-designed code, one step at a time • Build tests to make sure your refactorings work properly • Understand the challenges of refactoring and how they can be overcome • Compose methods to package code properly • Move features between objects to place responsibilities where they fit best • Organize data to make it easier to work with • Simplify conditional expressions and make more effective use of polymorphism • Create interfaces that are easier to understand and use • Generalize more effectively • Perform larger refactorings that transform entire software systems and may take months or years • Successfully refactor Ruby on Rails code