Skip to content

docs: Add practical research workflow to Research and Learning #43023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lavanitha wants to merge 4 commits into from
+14 −2
Closed

docs: Add practical research workflow to Research and Learning #43023

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f5220c2
docs: add practical research workflow to Research and Learning
lavanitha Feb 5, 2026
35055ea
Update files/en-us/learn_web_development/getting_started/soft_skills/…
lavanitha Feb 5, 2026
7935cec
Update files/en-us/learn_web_development/getting_started/soft_skills/…
lavanitha Feb 5, 2026
330e89d
docs: fix curriculum link to satisfy MDN lint rules
lavanitha Feb 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions ...earn_web_development/getting_started/soft_skills/research_and_learning/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ There is a lot to know as a web developer, and you are constantly learning. But
<li>Effective research methodologies.</li>
<li>Making a learning plan.</li>
<li>Staying motivated.</li>
<li>Rubber ducking</li>
<li><strong>Rubber ducking</strong>: explaining a problem out loud to clarify your own understanding and uncover gaps in logic.</li>
Copy link
Contributor

@chrisdavidmills chrisdavidmills Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a list of the learning outcomes of the chapter; it doesn't need a definition of what the concept is; that comes later. The edit is also written in a style that doesn't match the other bullets, leading me to believe this is AI generated.

<li>Effective problem solving.</li>
<li>Getting into the mindset of constant learning.</li>
</ul>
Expand All @@ -39,6 +39,18 @@ As a web developer, you will spend a lot of time searching for solutions to prob

To facilitate this and become more self-sufficient, you should learn effective strategies for finding answers — as discussed in the sections below — and when to use which strategy. For example, look up information online first, and only ask your mentor, classmates, or senior dev for help when you are truly stuck.

### A practical workflow for researching problems
Copy link
Contributor

@chrisdavidmills chrisdavidmills Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This conflates research and debugging, doesn't fit in the place it is placed, repeats some of the stuff covered in later sections, and doesn't use the same style as other lists in the article. More AI content, I think.


When you encounter a problem or an unfamiliar concept, it can be helpful to follow a consistent research workflow:

1. **Define the problem clearly** — write down what you are trying to achieve and what is not working.
2. **Consult official documentation first** — for web platform features, MDN Web Docs should usually be your first stop.
3. **Search for examples** — look for small, focused examples that demonstrate the concept in isolation.
4. **Experiment locally** — try the solution in a minimal test project or sandbox to confirm your understanding.
5. **Reflect and document** — note what worked, what didn't, and why, so future problems are easier to solve.

Using a structured approach like this helps reduce frustration and prevents unproductive searching.

### Choose high-quality resources

You should make sure that the resources you choose for research are high quality and reputable. To find out which resources are reputable, ask your teacher or more experienced colleagues what they'd recommend, and do some web searches to find out what other folks around the web recommend. MDN of course comes recommended; other good examples include:
Expand Down Expand Up @@ -167,7 +179,7 @@ It is a good idea to write down some sub-goals below your main goal, to allow yo
- Example website project built by next April
- etc.

If you are not sure what items to put on your goals list, our [curriculum](/en-US/curriculum/) can help.
If you are not sure what items to put on your goals list, our [curriculum](/en-US/curriculum) can help.

When you have worked out a weekly schedule then you should keep a record of what you manage to do each week in a simple spreadsheet or even in a notebook! Keep thinking about how much progress you are making, and adjust your plan if required.

Expand Down