You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussion for a pull request I would want to open.
Addition of a new item
Removal of some existing item
Changing in arrangement
General suggestion
[Y] Sharing an Idea
Something else
Please acknowledge the below listed
[Y] This is not a duplicate issue. I have searched and there is no existing issue for this.
[Y] I understand that these roadmaps are highly opinionated. The purpose is to not to include everything out there in these roadmaps but to have everything that is most relevant today comparing to the other options listed.
I am a junior developer looking at this roadmap, and it does feel a bit overwhelming. So, I suggest there could be a list of suggested projects at each stage to help junior developers measure their progress, and articulate their skills better (sort of like gamifying it). This also helps bring juniors to build more momentum as they would feel that they completed milestones along the way, rather looking at it as a long tough road. Plus, pointing the purpose of concepts can also help make juniors really understand why concepts/techniques could help make their workflow better.
These are just some suggestions. Hopefully, it can help.
I appreciate Mr.Ahmed and everyone for helping to build this wonderful project.
The text was updated successfully, but these errors were encountered:
Hey, thanks Ken. That's a good idea and we have been actively working on the next release of these roadmaps which is going to make them interactive and we will have the resources and more details to each of the nodes.
What roadmap is this issue about?
What is this issue about?
Please acknowledge the below listed
Enter the details about the issue here
I am a junior developer looking at this roadmap, and it does feel a bit overwhelming. So, I suggest there could be a list of suggested projects at each stage to help junior developers measure their progress, and articulate their skills better (sort of like gamifying it). This also helps bring juniors to build more momentum as they would feel that they completed milestones along the way, rather looking at it as a long tough road. Plus, pointing the purpose of concepts can also help make juniors really understand why concepts/techniques could help make their workflow better.
These are just some suggestions. Hopefully, it can help.
I appreciate Mr.Ahmed and everyone for helping to build this wonderful project.
The text was updated successfully, but these errors were encountered: