Typos

[skatterwe]

I found a few typos.

Introduction

• A professional software developer is actively interested into
• Putting it that short this may sound
• software development" a lowest common factor
• Tough it is neither a perfect
• Considering code being the lowest common factor [of] any software developer

Values

• In production plans parts are replace on

Correctness

• Sufficient to pass software though a test department
• unclear requirements rather that

production efficiency

• Naturally _ finally_ development time

Grade 1 - Red:

Principles

• Beware of Optimizations -> It should ring an alarm if you won't understand you own code
• Beware of Optimizations -> Understandability of code hast always priority
• FCoI -> With composition on class uses a different
• IOSP -> The decrease understandability and hamper both

Practises

• Pathfinder Rule
  • on the webpage it's called: boy scout rule. which one is the actual name you would like to use?
  • the why block is wrong it's the copied block from IOSP
  • A CCD in read grade

Grade 2 - Orange

Principles

• SLA -> Evolvability 3 stars on website 2 stars
• SRP -> Evolvability 3 stars on website 2 stars
• SoC -> Evolvability 3 stars on website 2 stars
• Source Code Conventions -> Code itself should be clear so that in gets along

Grade 3 - Yellow

Practises

• Code Coverage Analysis -> two simple metrics called C0 and C

Grade 4 - Green

Principles

• Open Closed -> Thereby [it] is feasible to add

Practises

• Static Code Analysis:
  • Fore legacy code, tools can retrieve
  • They [will] always -will- keep an eye

Grade 5 - Blue

Principles

• Implementation reflects Design -> Responsibility Single Developer in German its Team

Practises

• Design for implementation -> not translated
• Incremental Development -> not translated
• Component Orientation -> Up to know the principles

If it's ok, I'll raise a PR.

[slieser]

Hi Stephanie, thanks very much! I will correct the texts in the next days. We appreciate your help! Viele Grüße Stefan Lieser Am Steinernen Kreuz 27 53343 Wachtberg Gimmersdorf Mobile: +49 1525 6806877 -- Am 15. Mai 2024, 08:51 -0700 schrieb Stephanie Katterwe ***@***.***>:

…

I found a few typos. Grade 1 - Red: Principles • Beware of Optimizations -> It should ring an alarm if you won't understand you own code • Beware of Optimizations -> Understandability of code hast always priority • FCoI -> With composition on class uses a different • IOSP -> The decrease understandability and hamper both Practises • Pathfinder Rule ** on the webpage it's called: boy scout rule. which one is the actual name you would like to use? ** the why block is wrong it's the copied block from IOSP ** A CCD in read grade Grade 2 - Orange Principles • SLA -> Evolvability 3 stars on website 2 stars • SRP -> Evolvability 3 stars on website 2 stars • SoC -> Evolvability 3 stars on website 2 stars • Source Code Conventions -> Code itself should be clear so that in gets along Grade 3 - Yellow Practises • Code Coverage Analysis -> two simple metrics called C0 and C Grade 4 - Green Principles • Open Closed -> Thereby [it] is feasible to add Practises • Static Code Analysis: ** Fore legacy code, tools can retrieve ** They [will] always -will- keep an eye Grade 5 - Blue Principles • Implementation reflects Design -> Responsibility Single Developer in German its Team Practises • Design for implementation -> not translated • Incremental Development -> not translated • Component Orientation -> Up to know the principles If it's ok, I'll raise a PR. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[skatterwe]

If you want I can raise a PR. I've already translated the missing blocks and have the corrections ready. I wanted to have everything in a PDF and created a LaTex transcript as the link to the online github book doesn't work.

If you like I can also share the .tex file with you in case you want to use it.

[skatterwe]

Ah I just realised I can't create a branch.