Good code, bad code think like a software engineer
Code quality -- Layers of abstraction -- Other engineers and code contracts -- Errors -- Make code readable -- Avoid surprises -- Make code hard to misuse -- Make code modular -- Make code reusable and generalizable -- Unit testing principles -- Unit testing practices.
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | UnknownFormat |
| Sprache: | eng |
| Veröffentlicht: |
Shelter Island, NY
Manning
2021
|
| Schlagworte: | |
| Online Zugang: | Inhaltsverzeichnis |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Tag hinzufügen | Zusammenfassung: | Code quality -- Layers of abstraction -- Other engineers and code contracts -- Errors -- Make code readable -- Avoid surprises -- Make code hard to misuse -- Make code modular -- Make code reusable and generalizable -- Unit testing principles -- Unit testing practices. "Software development is a team sport. For an application to succeed, your code needs to be robust and easy for others to understand, maintain, and adapt. Whether you're working on an enterprise team, contributing to an open source project, or bootstrapping a startup, it pays to know the difference between good code and bad code. Good Code, Bad Code is a clear, practical introduction to writing code that's a snap to read, apply, and remember"--Page 4 of cover |
|---|---|
| Beschreibung: | "For coders early in their careers who are familiar with an object-oriented language, such as Java or C#"--Page 4 of cover |
| Beschreibung: | xx, 353 Seiten Illustrationen 24 cm |
| ISBN: | 9781617298936 978-1-61729-893-6 161729893X 1-61729-893-X |