Technical English: Modals and Engineering Judgment

Classifications / Humanities And Philosophy / Technical English: Modals and Engineering Judgment

TRACK

Use modal and auxiliary verbs to express ability, uncertainty, obligation, recommendation, permission, risk, inference, and retrospective judgment in technical work.

How do I use Technical English: Modals and Engineering Judgment to make short engineering communication more precise?

24 lessons

LESSONS

1. 001
   Can for Capability and Technical Possibility
   [TODO]
2. 002
   Could for Suggestions and Softer Possibility
   [TODO]
3. 003
   Be Able To for Specific Achievements
   [TODO]
4. 004
   Cannot and Could Not for Hard Limits
   [TODO]
5. 005
   Review: Capability vs Possibility REVIEW
   [TODO]
6. 006
   May and Might for Uncertainty
   [TODO]
7. 007
   Must for Strong Requirements
   [TODO]
8. 008
   Have To for External Requirements
   [TODO]
9. 009
   Should for Recommendations and Expected Behavior
   [TODO]
10. 010
    Ought To and Had Better in Technical Advice
    [TODO]
11. 011
    Review: Requirement, Advice, and Risk REVIEW
    [TODO]
12. 012
    Need To and Need Not in Engineering Plans
    [TODO]
13. 013
    Must Not and Do Not Have To
    [TODO]
14. 014
    Can, May, and Permission in APIs
    [TODO]
15. 015
    Would for Polite Requests and Hypothetical Designs
    [TODO]
16. 016
    Shall, Will, and API Contract Language
    [TODO]
17. 017
    Review: Polite Technical Collaboration REVIEW
    [TODO]
18. 018
    Must Have, Might Have, and Could Have for Inference
    [TODO]
19. 019
    Should Have and Could Have in Postmortems
    [TODO]
20. 020
    Would Have for Counterfactual Design
    [TODO]
21. 021
    Modal Chains in Risk Reviews
    [TODO]
22. 022
    Practice: Write a Design Review Comment
    [TODO]
23. 023
    Review: Certainty and Commitment REVIEW
    [TODO]
24. 024
    Capstone: Give Precise Advice on a Risky Change CAPSTONE
    [TODO]

← Back to Humanities And Philosophy