Scribd
Upload
4 views

CIT Introduction To Computer Programming

Uploaded by

r12819911
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

CIT Introduction To Computer Programming

Uploaded by

r12819911
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Readability and Documentation

Key Points on Readability (With Real-World Examples

- Readable Code: Code should be easy for humans


to read and understand.
Example: Like writing an email in simple language
so everyone understands.

- Future-Proof Code: Code should still make sense


after a long time.
Example: Writing a diary entry today you can
understand next year.

- Team Collaboration: Clear code lets everyone in


the team understand and work together.
Example: Sharing a group project where everyone
knows their part.

- Good Formatting: Neat, clean code helps people


read and understand faster.
Example: A neatly written recipe is easier to follow.

- Meaningful Names: Giving clear names to


variables makes code easier to follow.
Example: Labeling storage boxes so you know
what's inside.
- Use of Comments: Adding comments explains how
things work.
Example: Like adding notes in a cookbook to
explain a step.

- Self-explanatory Code: Code should be


understandable without looking elsewhere.
Example: A recipe that explains each step clearly.

Key Points on Documentation

- Programmer Documentation: Detailed guides for


tools and libraries.
Example: A car manual explaining features for
mechanics.

- User Documentation: Guides for users on how to


use the app.
Example: A TV manual explaining setup steps.

- Reliable Documentation: Makes maintaining and


updating software easier.
Example: A maintenance book for a car that tells
when to check parts.

- Knowledge Transfer: Documentation helps new


team members understand the software.
Example: A guidebook that helps new employees
learn fast.

Storytelling - Company Use Case

TechCorp is developing a health app. As the project


grows, more developers join the team. After a year,
some original developers leave. New members need
to understand the code quickly. Thanks to readable
code and clear documentation, new developers
easily take over. Comments like 'calculates daily
calories' help explain how the app works. Clear
variable names and good formatting keep everything
easy to follow. User manuals help customers, and
programmer documentation helps maintain the
software.

You might also like