This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
generated from alchemycodelab/web-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
kb
committed
Jan 12, 2022
1 parent
7890183
commit 28c3fcb
Showing
1 changed file
with
17 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,26 @@ | ||
## The Golden Rule: | ||
## The Golden Rule: | ||
|
||
🦸 🦸♂️ `Stop starting and start finishing.` 🏁 | ||
|
||
If you work on more than one feature at a time, you are guaranteed to multiply your bugs and your anxiety. | ||
|
||
## Making a plan | ||
|
||
1) **Make a drawing of your app. Simple "wireframes"** | ||
1) **Once you have a drawing, name the HTML elements you'll need to realize your vision** | ||
1) **For each HTML element ask: Why do I need this?** | ||
1) **Once we know _why_ we need each element, think about how to implement the "Why" as a "How"** | ||
1) **Find all the 'events' (user clicks, form submit, on load etc) in your app. Ask one by one, "What happens when" for each of these events. Does any state change?** | ||
1) **Think about how to validate each of your features according to a Definition of Done** | ||
1) **Consider what features _depend_ on what other features. Use this dependency logic to figure out what order to complete tasks.** | ||
1. **Make a drawing of your app. Simple "wireframes"** | ||
1. **Once you have a drawing, name the HTML elements you'll need to realize your vision** | ||
1. **For each HTML element ask: Why do I need this?** | ||
1. **Once we know _why_ we need each element, think about how to implement the "Why" as a "How"** | ||
1. **Find all the 'events' (user clicks, form submit, on load etc) in your app. Ask one by one, "What happens when" for each of these events. Does any state change?** | ||
1. **Think about how to validate each of your features according to a Definition of Done** | ||
1. **Consider what features _depend_ on what other features. Use this dependency logic to figure out what order to complete tasks.** | ||
|
||
Additional considerations: | ||
- Ask: which of your HTML elements need to be hard coded, and which need to be dynamically generated? | ||
- Consider your data model. | ||
- What kinds of objects (i.e., Dogs, Friends, Todos, etc) will you need? | ||
- What are the key/value pairs? | ||
- What arrays might you need? | ||
- What needs to live in a persistence layer? | ||
- Is there some state we need to initialize? | ||
- Ask: should any of this work be abstracted into functions? (i.e., is the work complicated? can it be resused?) | ||
|
||
- Ask: which of your HTML elements need to be hard coded, and which need to be dynamically generated? | ||
- Consider your data model. | ||
- What kinds of objects (i.e., Dogs, Friends, Todos, etc) will you need? | ||
- What are the key/value pairs? | ||
- What arrays might you need? | ||
- What needs to live in a persistence layer? | ||
- Is there some state we need to initialize? | ||
- Ask: should any of this work be abstracted into functions? (i.e., is the work complicated? can it be reused?) |