Consistent ____________ documentation applied without fail tends to beat out inconsistently
executed, but occasionally _______________ docs correct answers mediocre, brilliant
Agile user stories correct answers "I use <think> because it helps me to accomplish <outcome>"
Why is determining requirements difficult correct answers - Need to translate from people often
unskilled in software
- People will speak imprecisely
System Model correct answers Focuses on data and feature thinking; helpful in organizing code,
unhelpful to users to accomplist their "jobs to be done"
- Focuses on how the system will respond to certian inputs
User Model correct answers How the user thinks of a task/product and is more function based
and less feature or software based
Focuses on the navigaiton of the model as a user
Performance examples correct answers Clean code, limited features, global variables, plan
ahead, remove redundant code in JSS, clean simple CSS code
Accessiblity examples correct answers CSS for easy viewing in desktop, mobile, etc. Alt image
tags, dark mode
Maintainabilty examples correct answers Documentation, good github practices, testing,
comments, encapsulation, less dependencies (decoupling)
, Test pyramid correct answers Top layer: UI tests
Middle: Service Tests
Bottom: Unit tests
- More integration as you go up
- Slower as you go up
Team Test pyramid:
Top: PR Review
Middle: Puppeteer
Bottom: Jest
Software architecture correct answers Theory or design for how a specific software system will
be implemented, focuses on HOW not WHAT
Technical debt correct answers A concept taht reflects the implied cost of additional rework
caused by choosing a fast or easy solution now instead of using a better appreach that might take
longer
perfect decision now might not be one later
YAGNI correct answers You Ain't Gonna Need It
Simplification Mantra
KISS correct answers Keep It Simple Stupid
Simplification Mantra