How to Code .NET: Tips and Tricks for Coding .NET 1.1 and .NET 2.0 Applications Effectively
The title of this book may seem odd; you probably already know how to write code in .NET. But you can always benefit from knowing more. Coders, architects, and developers always strive to do their best, and if given the choice to do something correctly or incorrectly they will do it correctly. So...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31437 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| Tóm tắt: | The title of this book may seem odd; you probably already know how to write code in .NET.
But you can always benefit from knowing more. Coders, architects, and developers always
strive to do their best, and if given the choice to do something correctly or incorrectly they will
do it correctly. So why do we have so many bugs in our code? I could say, “Heck, it’s all the
managers making bonehead decisions.” It would be a popular answer, but it would not be
fair. We have bugs because humans and the communication between humans are imperfect.
The other major reason why code has bugs is that people do not have the time or energy
to pour resources into specific problems. When you are working on an application, you are
confronted with thousands of specific problems, and you have to assign a priority. This is
where this book is aimed. I take the time to investigate the specific problems and figure
out how to solve them. Your responsibility is to read the solutions and implement them as
appropriate.
This is not a patterns book, even though I reference patterns. It is not a book meant to solve
all problems, because like you I have to assign priority to the problems I want to solve. This book
is the first of a series, and subsequent volumes will solve more problems. This book aims to
look at a problem, feature, or fact and then figure out what that problem, feature, or fact implies.
As a quick example .NET 2.0 introduced the yield keyword. Cool use of technology, but
what does yield really imply? Is yield buggy? Is yield the future of all iterators? After reading
this book you’ll know all of yield’s implications and ramifications |
|---|