Cargando…

Clean code in C# : refactor your legacy C# code base and improve application performance by applying best practices /

Questions -- Further reading -- Chapter 3: Classes, Objects, and Data Structures -- Technical requirements -- Organizing classes -- A class should have only one responsibility -- Commenting for documentation generation -- Cohesion and coupling -- An example of tight coupling -- An example of low cou...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Alls, Jason (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Birmingham, UK : Packt Publishing, Limited, 2020.
Temas:
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)

MARC

LEADER 00000cam a2200000 i 4500
001 OR_on1201697302
003 OCoLC
005 20231017213018.0
006 m o d
007 cr unu||||||||
008 201027s2020 enk o 000 0 eng d
040 |a UMI  |b eng  |e rda  |e pn  |c UMI  |d UMI  |d EBLCP  |d YDX  |d N$T  |d OCLCF  |d OCLCO  |d OCLCQ  |d OCLCO  |d KSU  |d OCLCQ  |d OCLCO 
019 |a 1176511677  |a 1178641392 
020 |a 9781838985691 
020 |a 1838985697 
020 |z 9781838982973 
029 1 |a AU@  |b 000067556082 
035 |a (OCoLC)1201697302  |z (OCoLC)1176511677  |z (OCoLC)1178641392 
037 |a CL0501000160  |b Safari Books Online 
050 4 |a QA76.73.C154 
082 0 4 |a 005.133  |2 23 
049 |a UAMI 
100 1 |a Alls, Jason,  |e author. 
245 1 0 |a Clean code in C# :  |b refactor your legacy C# code base and improve application performance by applying best practices /  |c Jason Alls. 
246 3 |a Clean code in C sharp 
264 1 |a Birmingham, UK :  |b Packt Publishing, Limited,  |c 2020. 
300 |a 1 online resource (1 volume) 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
588 0 |a Online resource; title from title page (viewed October 23, 2020). 
505 0 |a Cover -- Title Page -- Copyright and Credits -- Dedication -- About Packt -- Contributors -- Table of Contents -- Preface -- Chapter 1: Coding Standards and Principles in C# -- Technical requirements -- Good code versus bad code -- Bad code -- Improper indentation -- Comments that state the obvious -- Comments that excuse bad code -- Commented-out lines of code -- Improper organization of namespaces -- Bad naming conventions -- Classes that do multiple jobs -- Methods that do many things -- Methods with more than 10 lines of code -- Methods with more than two parameters 
505 8 |a Using exceptions to control program flow -- Code that is difficult to read -- Code that is tightly coupled -- Low cohesion -- Objects left hanging around -- Use of the Finalize() method -- Over-engineering -- Learn to Keep It Simple, Stupid -- Lack of regions in large classes -- Lost-intention code -- Directly exposing information -- Good code -- Proper indentation -- Meaningful comments -- API documentation comments -- Proper organization using namespaces -- Good naming conventions -- Classes that only do one job -- Methods that do one thing 
505 8 |a Methods with less than 10 lines, and preferably no more than 4 -- Methods with no more than two parameters -- Proper use of exceptions -- Code that is readable -- Code that is loosely coupled -- High cohesion -- Objects are cleanly disposed of -- Avoiding the Finalize() method -- The right level of abstraction -- Using regions in large classes -- The need for coding standards, principles, and methodologies -- Coding standards -- Coding principles -- Coding methodologies -- Coding conventions -- Modularity -- KISS -- YAGNI -- DRY -- SOLID -- Occam's Razor -- Summary -- Questions -- Further reading 
505 8 |a Chapter 2: Code Review -- Process and Importance -- The code review process -- Preparing code for review -- Leading a code review -- Issuing a pull request -- Responding to a pull request -- Effects of feedback on reviewees -- Knowing what to review -- Company's coding guidelines and business requirement(s) -- Naming conventions -- Formatting -- Testing -- Architectural guidelines and design patterns -- Performance and security -- Knowing when to send code for review -- Providing and responding to review feedback -- Providing feedback as a reviewer -- Responding to feedback as a reviewee 
520 |a Questions -- Further reading -- Chapter 3: Classes, Objects, and Data Structures -- Technical requirements -- Organizing classes -- A class should have only one responsibility -- Commenting for documentation generation -- Cohesion and coupling -- An example of tight coupling -- An example of low coupling -- An example of low cohesion -- An example of high cohesion -- Design for change -- Interface-oriented programming -- Dependency injection and inversion of control -- An example of DI -- An example of IoC -- The Law of Demeter 
520 |a Clean Code in C# addresses the modern-age software development concerns across the various domains such as Windows desktop applications, web applications, cloud applications, and so on. You will be able to understand how to correct the problems such as code inefficiency, redundancy, duplication as a result of bad code. 
590 |a O'Reilly  |b O'Reilly Online Learning: Academic/Public Library Edition 
650 0 |a C# (Computer program language) 
650 0 |a Computer programming. 
650 6 |a C# (Langage de programmation) 
650 6 |a Programmation (Informatique) 
650 7 |a computer programming.  |2 aat 
650 7 |a C# (Computer program language)  |2 fast 
650 7 |a Computer programming  |2 fast 
776 0 8 |i Print version:  |a Alls, Jason.  |t Clean Code in C# : Refactor Your Legacy C# Code Base and Improve Application Performance by Applying Best Practices.  |d Birmingham : Packt Publishing, Limited, ©2020 
856 4 0 |u https://learning.oreilly.com/library/view/~/9781838982973/?ar  |z Texto completo (Requiere registro previo con correo institucional) 
938 |a ProQuest Ebook Central  |b EBLB  |n EBL6267445 
938 |a EBSCOhost  |b EBSC  |n 2527747 
938 |a YBP Library Services  |b YANK  |n 301388223 
994 |a 92  |b IZTAP