Uh oh!
There was an error while loading. Please reload this page.
guide: add user journey memory tutorial - #4728
Conversation
tony-go
commented
Jul 18, 2022
Hey @RafaelGSS 👋 Neat! What is the strategy here? Should we take time to review the whole content, or should we merge it quickly and then improve it incrementally? |
RafaelGSS
commented
Jul 18, 2022
The idea is to review the whole content, so we make sure we aren't delivering an out-of-date content to end users |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
mhdawson
left a comment
There was a problem hiding this comment.
LGTM with a few small suggestions.
b846b21 to
7168854Compare7168854 to
2efaaf6Compare
Reference: nodejs/diagnostics#502
The Node.js Diagnostics Working Group has been creating a collection of tutorials for the past 3 years (?).
The goal is to track the user journey across various issues and provide a good reference that users can use as a baseline when diagnosing a codebase.
Those tutorials were created some time ago. We did a review, but things move fast and it might be out-of-date at some point.
cc: @nodejs/diagnostics