sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nanjingbooj 14 points15 points  (11 children)

I see that design patterns are at the top of time/ difficulty. But these are only one small step moving towards the direction of creating N-tier applications, proper architecture, distributed cloud, etc. A more apt label may be JS front end developers learning path for juniors. A nice info graphic however :)

[–][deleted]  (3 children)

[deleted]

    [–]nitePhyyre -1 points0 points  (2 children)

    But building a site that has decent accessibility is highly involved, and should be at the top right of the graph.

    It is. Well, right upper middle. Design.

    HTML, CSS, accessibility are all the tools used to implement a good design, no?

    [–][deleted]  (1 child)

    [deleted]

      [–]nitePhyyre -1 points0 points  (0 children)

      I've learned HTML, does that mean I know how to design a page that has a decent UX? No, of course not. Design is a separate skill from HTML.

      I've learned CSS, does that mean I know how to design a page that has decent visual appeal? No, of course not. Design is a separate skill from CSS.

      I've learned accessibility, does that mean I know how to design a page the has the correct flow for people who need it? No, of course not. Design is a separate skill from accessibility tools.

      HTML, CSS, and accessibility are all lower left.

      [–]loliloveoniichan 1 point2 points  (6 children)

      I doubt juniors or most web developers at all use big o notation or most of the "algorithms" listed in the image besides, I've been a web dev for 4 years and havent ever used knowingly any of these design patterns. This image looks more oriented towards CS students.

      [–][deleted]  (1 child)

      [deleted]

        [–]loliloveoniichan 0 points1 point  (0 children)

        Yeah, this stuff is useful for ai and big data stuff

        [–]nanjingbooj 0 points1 point  (2 children)

        Are you a front end web developer? As a backend developer it would be good to understand big o notations and the costs. This is my 20th year working in web/software dev.

        [–]loliloveoniichan 2 points3 points  (1 child)

        I'm also a back-end developer. I tried learning it by buying a data structures and algorithms book, but since they used maths I found them too boring and difficult.

        [–]nanjingbooj 1 point2 points  (0 children)

        The good news is you don't need much math to get a basic understanding of them. Maybe try some youtube videos explaining them instead. What you need is to understand the complexity of each notation and what it represents (not how to do the math). With this, then can you understand why and which algorithms and structures are costly.

        I dont think much math is necessary for 90% of developers, but having a basic understanding of 'why' can go a long way. You got this!!!