-
-
Save joelhooks/dac33be2b21a983af46b8578dd6e9588 to your computer and use it in GitHub Desktop.
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
{ | |
"solid-foundation": [ | |
"doing-everything-wrong", | |
"overwhelmed-by-choices", | |
"too-much-choice", | |
"learning-plateau", | |
"time-to-study", | |
"lack-of-time-to-prepare-for-the-future", | |
"choice-is-difficult", | |
"what-to-do-now", | |
"building-a-code-portfolio", | |
"forgetting-what-has-been-learned", | |
"learning-is-slow", | |
"constant-change", | |
"lack-of-confidence-in-output", | |
"get-experience-and-knowledge", | |
"find-first-job", | |
"hard-to-decide", | |
"worried-about-hireability", | |
"confidence-in-knowledge", | |
"lack-of-core-understanding", | |
"hard-to-switch-later", | |
"wasting-time", | |
"no-confidence", | |
"looking-smart", | |
"doing-things-wrong", | |
"finding-where-to-start", | |
"making-the-right-tech-choice", | |
"not-specializing", | |
"choosing-a-specialty", | |
"choosing-what-to-learn", | |
"learn-new-things", | |
"writing-good-maintainable-code", | |
"good-code-under-pressure", | |
"clean-code", | |
"code-quality", | |
"creating-amazing-experiences", | |
"becoming-more-experimental", | |
"keep-it-simple", | |
"learning-new-languages", | |
"lack-of-challenge-at-work", | |
"work-focused-on-bugs", | |
"coding-is-all-work", | |
"finding-a-project-to-work-on", | |
"prioritizing-what-to-learn", | |
"coding-for-fun", | |
"finding-a-project", | |
"understanding-why", | |
"practical-experience", | |
"hard-to-decide-what-to-learn", | |
"understand-the-big-picture", | |
"real-world-examples", | |
"applying-learned-concepts", | |
"how-to-use-the-latest-and-greatest", | |
"too-much-assumed-knowledge", | |
"lack-core-knowledge", | |
"deciding-when-to-use-technologies", | |
"learning-path", | |
"learning-paths", | |
"finding-the-correct-path", | |
"uncertain-about-choices", | |
"avoiding-turds", | |
"understanding-areas-of-weakness", | |
"everything-feels-off", | |
"too-much-to-learn", | |
"choosing-priorities", | |
"uncertain-about-choices", | |
"too-much-choice", | |
"parsing-industry-jargon", | |
"filtering-the-best-content", | |
"too-much-beginner-content", | |
"real-world-application-of-learning", | |
"picking-a-new-language-to-learn", | |
"real-world-examples", | |
"trusted-learning-resources", | |
"project-based-learning", | |
"no-comprehensive-path-to-learn", | |
"putting-new-knowledge-to-use", | |
"path-to-goal", | |
"out-of-date-tutorials", | |
"difficult-to-understand-materials", | |
"rememebering-what-is-learned-is-hard", | |
"interactive-lessons", | |
"concise-lessons", | |
"understanding-practical-use-cases", | |
"more-why-alongside-how", | |
"getting-better", | |
"diagrams-and-explainers", | |
"premade-templates", | |
"more-complex-practice-projects", | |
"sample-projects", | |
"complete-application-examples", | |
"production-like-examples", | |
"practicing-what-is-learned", | |
"production-level-exercises", | |
"demonstation-of-production-problems", | |
"real-world-examples", | |
"real-world-examples", | |
"small-practical-examples", | |
"real-world-web-apps", | |
"real-world-practice-projects", | |
"just-enough-real-world-examples", | |
"practice-projects", | |
"practical-applying-fundamentals", | |
"real-life-problems-explained", | |
"learning-best-practices", | |
"choosing-best-practices", | |
"understanding-patterns-and-practices", | |
"learning-patterns-in-depth", | |
"understanding-best-practices", | |
"staying-current-with-industry-trends", | |
"best-practices-for-javascript", | |
"best-practices", | |
"understanding-industry-best-practices", | |
"understanding-the-latest-patterns", | |
"learning-best-practices", | |
"best-practices-patterns-arcitechture", | |
"current-best-practices", | |
"best-practices", | |
"deciding-on-best-practice", | |
"production-infrastructure", | |
"building-production-apps", | |
"application-arcitechture", | |
"large-scale-javascript", | |
"architecting-flexible-apps-business", | |
"scaling-applications", | |
"structuring-applications", | |
"application-arcitechture", | |
"application-arcitechture-and-structure", | |
"understanding-stack-architecture", | |
"application-architecture", | |
"solid-application-arcitechture", | |
"make-money", | |
"architecture-choices", | |
"understanding-the-stack-architecture", | |
"application-arcitechture-at-scale", | |
"scaling-applications", | |
"focusing-on-the-best-new-tools", | |
"no-confidence-in-code-decisions", | |
"dealing-with-poor-docs", | |
"forced-to-work-sloppy", | |
"quick-and-cheap-solutions", | |
"clean-code-under-pressure", | |
"staying-competitive", | |
"choosing-a-specialization", | |
"forced-into-specialization", | |
"fear-of-job-security", | |
"not-feeling-qualified", | |
"finding-the-right-job", | |
"foot-in-the-door" | |
], | |
"go-deep": [ | |
"dealing-with-complexity", | |
"dealing-with-complexity", | |
"handling-ecosystem-complexity", | |
"starting-at-complex", | |
"naming-things", | |
"managing-state", | |
"building-complex-apps", | |
"dealing-with-side-effects", | |
"managing-application-state", | |
"real-world-complexity", | |
"computer-science", | |
"whiteboard-prep", | |
"understanding-graphql", | |
"data-structures-and-algorithms", | |
"core-computer-science", | |
"understanding-webpack", | |
"configuring-webpack", | |
"distributed-computing", | |
"real-world-devops", | |
"learning-css", | |
"large-scale-css", | |
"using-vanillajs-to-build-pwas", | |
"getting-the-most-out-of-plain-javascript", | |
"automated-testing", | |
"testing-javascript", | |
"application-browser-performance", | |
"application-security", | |
"integrating-technology", | |
"hidden-costs-of-new-technology", | |
"debugging-broken-code", | |
"challenges-with-deployment", | |
"visual-design", | |
"common-issues-with-apps", | |
"debugging-applications", | |
"whiteboard-interviews", | |
"learning-functional-programming", | |
"functional-and-reactive-programming", | |
"functional-programming-concepts", | |
"artificial-intelligence", | |
"computer-science-basics", | |
"algorithms-and-data-structures", | |
"phd-wall-for-machine-learning", | |
"core-understanding-of-tools", | |
"understanding-core-knowledge", | |
"understanding-core-language-skills", | |
"understanding-tradeoffs", | |
"understanding-tradeoffs", | |
"understanding-ideas-and-concepts", | |
"understanding-difficulty-of-prod-deploy", | |
"understanding-internals", | |
"understanding-internals", | |
"understanding-internals", | |
"understanding-code-internals", | |
"framework-internals", | |
"understanding-code-internals", | |
"understanding-internals", | |
"understanding-internals" | |
], | |
"stay-current": [ | |
"asking-good-questions", | |
"finding-community", | |
"building-open-source-community", | |
"industry-standard-coaching", | |
"meeting-other-developers", | |
"finding-users", | |
"finding-experts-to-trust", | |
"contributing-to-open-source", | |
"peer-collaboration", | |
"contributing-meaningfully", | |
"finding-clients", | |
"finding-community", | |
"lack-of-coach-or-mentor", | |
"mentorship-and-coaching", | |
"picking-the-best-stack", | |
"picking-a-language-or-stack", | |
"picking-a-stack", | |
"application-arcitechture-for-stack", | |
"stack-creep-hard-to-manage", | |
"choosing-a-stack", | |
"understanding-the-full-stack", | |
"picking-a-stack", | |
"choosing-a-stack", | |
"choosing-a-good-stack", | |
"choosing-a-slice-of-the-stack-to-focus-on", | |
"learning-a-full-stack", | |
"choosing-a-stack", | |
"choosing-the-right-stack", | |
"learning-a-full-stack", | |
"stack-specialization", | |
"right-stack-for-the-problem", | |
"pick-stack-for-community", | |
"efficient-stack", | |
"scaling-monitoring-alerts-full-stack", | |
"understanding-the-full-stack", | |
"picking-a-stack-for-focus", | |
"picking-a-stack-with-confidence", | |
"choosing-a-stack-for-native-dev", | |
"picking-the-right-stack", | |
"keeping-pace-with-stack-changes", | |
"understanding-the-react-stack", | |
"choose-a-stack", | |
"understanding-how-to-pick-a-stack", | |
"full-stack-development", | |
"choosing-a-stack", | |
"understanding-the-full-stack", | |
"full-stack", | |
"learning-the-full-stack", | |
"picking-a-stack-to-focus-on", | |
"learning-a-full-stack", | |
"mastering-a-specific-stack", | |
"picking-a-stack-of-tools", | |
"drop-wordpress-for-jamstack", | |
"learning-a-full-stack", | |
"learning-all-the-stacks", | |
"learning-full-stack-react", | |
"keeping-pace-with-change", | |
"understanding-hype-cycle", | |
"comparing-new-and-old-technology", | |
"rapid-change-of-technology", | |
"churn-of-tooling", | |
"keeping-pace-with-changes-in-javascript", | |
"keeping-pace-with-change", | |
"keeping-up-with-change", | |
"understanding-what-is-going-to-change", | |
"staying-current-with-industry-trends", | |
"picking-up-advanced-new-skills", | |
"keeping-up-with-change", | |
"keeping-pace-with-change" | |
], | |
"shine-at-work": [ | |
"no-time-to-dig-deeper", | |
"no-learning-time-on-the-the-job", | |
"building-learning-habits", | |
"learning-habits", | |
"staying-current", | |
"find-time-to-learn", | |
"learning-everything", | |
"learning-habits", | |
"keeping-up-with-change", | |
"keeping-current", | |
"keeping-pace-with-change", | |
"keeping-pace-with-change", | |
"keeping-pace-with-change", | |
"learning-habits", | |
"focused-learning", | |
"learning-habits", | |
"no-consistent-practice-and-learning", | |
"staying-focused", | |
"making-learning-a-habit", | |
"keeping-pace-with-change", | |
"no-time-for-going-in-depth", | |
"no-time-to-play", | |
"learning-habits", | |
"finding-time-to-learn", | |
"no-motivation-to-learn", | |
"keeping-pace-with-change", | |
"keeping-pace-with-change", | |
"staying-current", | |
"keeping-pace-with-change-in-front-end", | |
"keeping-pace-with-change", | |
"learning-habits", | |
"learning-habits", | |
"not-enough-time-in-the-day", | |
"finding-time-to-study", | |
"learning-habits", | |
"learning-habits", | |
"understanding-legacy-code", | |
"maintaining-legacy-node-apps", | |
"stuck-using-old-tools", | |
"dealing-with-legacy-apps", | |
"dealing-with-legacy", | |
"esoteric-technology", | |
"growing-while-stuck-with-legacy-code", | |
"no-buy-in-for-quality", | |
"lack-of-buy-in", | |
"getting-team-buy-in", | |
"coworker-buy-in", | |
"sharing-knowledge-with-team", | |
"knowledge-sharing-with-team", | |
"communication" | |
] | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment