exceedego的专栏

Alavoor Vasudevan - Linux C++ Programming- Howto.pdf

O'reilly - Practical C Programming. 3rd Ed.pdf

Addison Wesley - Design Patterns Explained.chm

Addison Wesley - UNIX Network Programming Volume 1.3rd Ed The Sockets Networking API-LiB.chm

MASM32 VERSION 9.0 安装时直接将压缩文件解压到任意一个盘区的根目录下;将此文件夹命名为MASM32;然后设置环境变量,相信对你们来说是没有什么问题啦!!! 不过还是唠叨一下吧: 右击"我的电脑"-"属性"-"高级"-"环境变量" 将以下内容加入到对应的项目里面就OK啦! D:\masm32\bin对应"PATH" D:\masm32\lib对应"LIB" D:\masm32\include对应"INCLUDE"

O'reilly - C++ Cookbook.chm

Addison Wesley Professional - Beyond The C++ Standard Library - An Introduction To Boost (2005).chm

Addison Wesley - The C++ Programming Language 3Rd Ed Bjarne Stroustrup.pdf

Addison Wesley - The C++ Programming Language (3rd) SPECIAL EDITION , B Stroustrup.pdf

Addison Wesley - C++ Templates - The Complete Guide.chm

Addison Wesley - Effective C++ Third Edition 55 Specific Ways to Improve Your Programs and Designs.chm

Mcgraw Hill - The Art of C++.chm

No Starch Press - How Not to Program in C++.pdf

O'reilly - C++ In A Nutshell.chm

Addison Wesley - C++ Network Programming Vol 2.chm

Addison Wesley - C++ Standard Library. A Tutorial And Reference.chm

Addison-Wesley - Exceptional C++ Style 40 New Engineering Puzzles, Programming Problems and Solutions - Herb Sutter.chm

Addison Wesley - Designing Components with the C++ STL.pdf

Addison Wesley - Inside the C++ Object Model (1996).chm

O'reilly - Programming Embedded Systems in C and C++ (1999).pdf

Que - C++ Professional Programmer's Handbook.pdf

Scott Meyers - Effective STL.pdf

The Professional ScrumMaster's Handbook A collection of tips, tricks, and war stories to help the professional ScrumMaster break the chains of traditional organization and management

In the internet age, delivery speed is the theme of the day in software development. A decade ago, projects lasted several years and project phases were measured in months. Today, most teams’ projects are measured in months and project phases are reduced to weeks or even days. Anything that requires long-term planning is dropped, including big up-front software designs and detailed requirements analysis. Tasks that require more time than an average project phase are no longer viable. Goodbye code freezes and weeks of manual regression testing! With such a high frequency of change, documentation quickly gets outdated. Detailed specifications and test plans require too much effort to keep current and are considered wasteful. People who relied on them for their day-to-day work, such as business analysts or testers, often become confused about what to do in this new world of weekly iterations. Software developers who thought they weren’t affected by the lack of paper documents waste time on rework and maintaining functionality that’s not required. Instead of spending time building big plans, they waste weeks polishing the wrong product. In the last decade, the software development community has strived to build software the “right” way, focusing on technical practices and ideas to ensure high-quality results. But building the product right and building the right product are two different things. We need to do both in order to succeed.

The authors have created this book in the hope of providing more information on what it takes to move to a more agile process. We have taken all of our migration experiences and rolled them into this book to help you with your own agile adoption. To make the adoption steps even more tangible, we have created a case study that is an amalgamation of our experiences. As you follow the case study, you will be reviewing actual situations that we encountered during migrations and how the companies we worked with dealt with constraints and cultural change. Real company names are not used, but the events are real.

Git is a tool for tracking changes made to a set of files over time, a task traditionally known as “version control.” Although it is most often used by programmers to coordinate changes to software source code, and it is especially good at that, you can use Git to track any kind of content at all. Any body of related files evolving over time, which we’ll call a “project,” is a candidate for using Git. With Git, you can: • Examine the state of your project at earlier points in time • Show the differences among various states of the project • Split the project development into multiple independent lines, called “branches,” which can evolve separately • Periodically recombine branches in a process called “merging,” reconciling the changes made in two or more branches • Allow many people to work on a project simultaneously, sharing and combining their work as needed

Git Extensions is a toolkit aimed at making working with Git under Windows more intuitive. The shell extension will integrate in Windows Explorer and presents a context menu on files and directories. There is also a Visual Studio extension to use Git from the Visual Studio IDE.

The Nexus platform, with Nexus Repository Manager Pro, Nexus Repository Manager OSS and Nexus IQ Server, is all about working with components and repositories. Components A component is a resource like a library or a framework that is used as part of your software application at run-time, integration or unit test execution time, or required as part of your build process. It could be an entire application or a static resource like an image.

Metrics are a necessary evil. Measurement is easily the least interesting aspect of software development, and yet without it we have little chance of delivering anything useful. But nearly everyone I meet in the software field is at a loss to know what to measure or how to use the measurements. The standard metrics we all learn in school often fail to help us in the real world. Whenever I give a talk about metrics, the room is filled beyond capacity and people stay beyond the allotted time. I’m always surprised, because this isn’t an inherently interesting subject. People need practical metrics that are a fit for their situations. I can’t claim this book will be a fun read, but I do think it fills a gap that sorely needs to be filled. This book approaches the topic differently than others. It’s neither an academic study of metrics nor a survey of existing literature nor a sales pitch for metrics intended to accompany a published software-delivery framework. Rather, it’s processagnostic and offers advice to help you recognize how the work flows in your organization, regardless of labels and buzzwords, so you can choose or create metrics that can help you steer development work toward a goal or quantify the effects of improvement efforts. The book doesn’t ask you to change your organization; it’s meant to help you survive in the organization as it currently exists. It doesn’t suggest what you should measure, but rather what you can measure in light of present organizational realities.

This section will introduce you to monitoring in general, and Prometheus more specifically.

The journey to complete The DevOps Handbook has been a long one—it started with weekly working Skype calls between the co-authors in February of 2011, with the vision of creating a prescriptive guide that would serve as a companion to the as-yet unfinished book The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.

If you are familiar with the origin of the DevOps term, and can’t wait to start facilitating the game, feel free to skip this chapter. Otherwise, read on to learn about people and ideas that brought the DevOps movement to life. Find out about the role Twitter played in coining the term “DevOps” and read about the book that inspired the creation of the Chocolate, Lego and Scrum game.

Markdown is a markup language. The name is a pun, but where the humor might be atrocious, the language is not. The Markdown language lets you write plain text documents with a few lightweight annotations that specify how you want the document formatted. Such annotations are the defining characteristics of a markup language. Markup languages separate the semantic or content part of a document from the formatting of said document. The content of a document is the text, what should be headers, what should be emphasized, and so on. The formatting specifies the font and font size, whether headers should be numbered, and so on.

Prentice Hall - C++ How to Program, Fifth Edition.chm

Sams - Tricks of the Windows Game Programming Gurus (1999).pdf

Prentice Hall - Thinking in C++ Volume 1, 2nd Edition.pdf

Prentice Hall - C++ GUI Programming with Qt4 (2006).chm

Sams - C++ Unleashed.pdf

Osborn - C++ --Complete Reference (3rd Ed.).pdf

O'reilly - Secure Programming Cookbook For C And C++.chm