YumSale

Debug It! will equip you with the tools, techniques, and approaches to help you tackle any bug with confidence. These secrets of professional debugging illuminate every stage of the bug life cycle, from constructing software that makes debugging easy; through bug detection, reproduction, and diagnosis; to rolling out your eventual fix.

Whether you’re writing Java or assembly language, targeting servers or embedded micro- controllers, or using agile or traditional approaches, the same basic bug-fixing principles apply.

You’ll learn an empirical approach that leverages your software’s unique ability to show you what’s really happening, the importance of finding a reliable and convenient means of reproducing a bug, and how to avoid common pitfalls. You’ll see how to use commonly available tools to automatically detect problems before they’re reported by customers. You’ll construct “self-debugging” software that automatically provides access to crucial internal information and identifies the broken assumptions that lead to bugs.

To all those wondering “Why?” and “How?” certain organizations are more productive than their peers, Logan, King and Fischer-Wright have some concrete answers. In their landmark book, “Tribal Leadership”, they explore the essence of organizational culture. What they have uncovered is a dynamic at least 15,000 years in the making, and at the heart of all human organizations: the tribe. We operate in a “tribe”-a group of 20 to 150 people- in which important decisions are made and productivity is determined. Larger organizations are “tribes of tribes”. Five stages describe the evolution of the tribe, from savage and dysfunctional to innovative and powerfully inspirational. What sets this work apart is its practical advice on both identifying the stage of the tribe and the means to advance to the next stage. Laced with real-life examples, the book is eminently readable. There is no doubt it will transform the reader, no matter where their own tribe finds itself. They will understand the difference between leading and commanding.

The visionary CEO of Zappos explains how an emphasis on corporate culture can lead to unprecedented success.

Pay new employees $2000 to quit. Make customer service the entire company, not just a department. Focus on company culture as the #1 priority. Apply research from the science of happiness to running a business. Help employees grow both personally and professionally. Seek to change the world. Oh, and make money too.

Sound crazy? It’s all standard operating procedure at Zappos.com, the online retailer that’s doing over $1 billion in gross merchandise sales every year.

In 1999, Tony Hsieh (pronounced Shay) sold LinkExchange, the company he co-founded, to Microsoft for $265 million. He then joined Zappos as an adviser and investor, and eventually became CEO.

In 2009, Zappos was listed as one of Fortune magazine’s top 25 companies to work for, and was acquired by Amazon later that year in a deal valued at over $1.2 billion on the day of closing.

In his first book, Tony shares the different business lessons he learned in life, from a lemonade stand and pizza business through LinkExchange, Zappos, and more. Ultimately, he shows how using happiness as a framework can produce profits, passion, and purpose both in business and in life. (edited by author)

The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology–from Smalltalk to CORBA to Java to .NET–the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book’s lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include:

Go to Amazon

NHibernate is an open source object-relational mapper, or simply put, a way to retrieve data from your database into standard .NET objects. Quite often we spend hours designing the database, only to go back and re-design a mechanism to access that data and then optimize that mechanism. This book will save you time on your project, providing all the information along with concrete examples about the use and optimization of NHibernate.

Connecting to a database to retrieve data is a major part of nearly every project, from websites to desktop applications to distributed applications. Using the techniques presented in this book, you can access data in your own database with little or no code.

This book covers the use of NHibernate from a first glance at retrieving data and developing access layers to more advanced topics such as optimization and Security and Membership providers. It will show you how to connect to multiple databases and speed up your web applications using strong caching tools. We also discuss the use of third-party tools for code generation and other tricks to make your development smoother, quicker, and more effective.

This easy-to-follow guide will show you how to connect the NHibernate object-relational mapper to your projects to create a rich, efficient, object-oriented data access layer with little or no additional work

What you will learn from this book

• Use NHibernate to retrieve and store data in your database
• Develop an efficient, robust data access layer with little or no code
• Design or modify your database for high performance
• Connect to multiple databases or database backends with simple code
• Implement base classes to provide basic functionality for all database objects
• Improve the performance of your data retrieval methods with proven open source technology
• Make web applications faster using strong caching strategies such as memcached
• Simplify data storage and display using built-in .NET data controls with NHibernate
• Using NHibernate to control application security using Membership and Role providers and .NET security controls

Go to Amazon

XP is a discipline of the business of software development that focuses the whole team on common, reachable goals. XP teams develop and produce quality software at a sustainable pace.

XP brings accountability and transparency to software development.

XP provides different practices to software development team to improve their performance and quality, following are some of the practices introduced by XP:

- Testing early, often and automated: Unit testing
- Incremental design: design everyday
- Daily deployment
- Customer involvement: immediate feedback
- Refactoring
- Continuous integration
- Short development cycles
- Incremental planning

Using above practices day-to-day help us to reduce our development stress and improve our development quality.

Practices are evidence of values, values such as communication, simplicity, feedback, courage, respect, as well as other values like quality-of-life, safety, security and predictability. XP embrace these values.

There are principles that guide XP. It follows principles to build a bridge between values and practices. Principles based on humanity, economics, mutual benefits, self-similarity, improvement, diversity, reflection, flow, opportunity, redundancy, failure, quality, baby steps, and responsibility.

We use the principles to understand the practices better and to improvise complementary practices. Understanding the principles gives you the opportunity to create practices that work in harmony with your existing practices and your overall goals.

XP became to make life better for programmers.

Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,it advocates frequent “releases” in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.

Other elements of extreme programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customer’s requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers. The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to “extreme” levels, on the theory that if some is good, more is better. It is unrelated to “cowboy coding”, which is more free-form and unplanned. It does not advocate “death march” work schedules, but instead working at a sustainable pace.

Critics have noted several potential drawbacks, including problems with unstable requirements, no documented compromises of user conflicts, and lack of an overall design specification or document.

Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.

Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.

Fundamentals of XP include:

• Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders.
• Writing unit tests before programming and keeping all of the tests running at all times.
• Integrating and testing the whole system–several times a day.
• Producing all software in pairs, two programmers at one screen.
• Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity.
• Putting a minimal system into production quickly and growing it in whatever directions prove most valuable.

Why is XP so controversial? Some sacred cows don’t make the cut in XP:

• Don’t force team members to specialize and become analysts, architects, programmers, testers, and integrators–every XP programmer participates in all of these critical activities every day.
• Don’t conduct complete up-front analysis and design–an XP project starts with a quick analysis of the entire system, and XP programmers continue to make analysis and design decisions throughout development.
• Develop infrastructure and frameworks as you develop your application, not up-front–delivering business value is the heartbeat that drives XP projects.
• Don’t write and maintain implementation documentation–communication in XP projects occurs face-to-face, or through efficient tests and carefully written code.

You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.

Go to Amazon