21 ms·
Web Development for Beginners – A Curriculum
- mattlondon 5y agoSuperb to see accessibility being there right at the start. Also really nice to see that this is not just a "how to use React" tutorial - kudos to MS for avoiding that. Looks like a great course.
- vga805 5y agoIt's nice to see accessibility discussed right away in the introduction lectures.
- deleted 5y ago[deleted]
- polalavik 5y agoLooks like a great resource for absolute beginners. I have dabbled in full stack open [1] and I Think that is a great resource for people who have a little cs knowledge under their belt already. [1] https://fullstackopen.com/en/ https://fullstackopen.com/en/
- reducesuffering 5y agoYes, I'd strongly second this.
- dgritsko 5y agoI recently had a conversation with an "absolute beginner" and it was a stark reminder just how much knowledge I take for granted. It really is extremely challenging to try and build up a base of knowledge starting with no prior experience, and it's great to see examples of this done right.
- bigDinosaur 5y agoI find most of what I do in web dev to be trivial to the point of mind-numbing. People smarter than me from different fields try to do what I do and often have far more difficulty than I'd expect. Job security for me until the ML engineers work out I can probably be mostly replaced by a smarter templating engine!
- jb3689 5y agoModern web development is dumbed down by shared APIs abstracting most of the hard problems into patterns (arguably a good thing as there is way more consistency in web dev than infrastructure), but the concepts are still quite complex. Heck, React alone is a fairly complex piece of software that 90% of its users take completely foregranted let alone understand why it became a popular choice. Low-level front end is no joke
- spoils19 5y agoIt's no surprise that low level frontend is infinitely more performant, accessible and easier to maintain than framework obscured nonsense of this generation.
- tmpz22 5y agoIt devolves into “here’s this really dumb thing that we deal with, oh and this stupid thing is to deal with Y” - it’s really hard to be cynical with trying to break down the layers of abstraction and how they came to be.
- exodust 5y agoSlightly cynical but lesson 2 is already into GitHub and a bunch of terminal commands. Great way to put beginners off web development. I guess it's no surprise Microsoft wants beginners to sign up at lesson 2 of 24. Also I'm not sure if these info graphic styles help or hinder understanding at a glance. I find it more effort to read the flow when it's a comic, but could be just me: https://raw.githubusercontent.com/microsoft/Web-Dev-For-Beginners/main/sketchnotes/webdev101-github.png https://raw.githubusercontent.com/microsoft/Web-Dev-For-Begi...
- jlooper 5y agoOur sketchnotes are very popular, and help visual learners. We have others in a different style: https://aka.ms/iot-beginners https://aka.ms/iot-beginners
- exodust 5y agoThat example introduces a lot of visual clutter and inconsistency. I doubt anyone can make it from 1 to 24 and not feel exhausted. Panel 4, "Deep dive into IOT" has an illustration of stick figure diving under water. I'm not sure the concept of "deep dive" requires the explanation. https://raw.githubusercontent.com/microsoft/IoT-For-Beginners/main/sketchnotes/Roadmap.jpg https://raw.githubusercontent.com/microsoft/IoT-For-Beginner... I thought the learning potential was more for the person who makes the sketchnote, rather than people reading docs.
- jlooper 5y agoJust want to thank you for your kind comments, it's making me happy :) - cheers from Jen, maintainer of these repos and curriculum designer / author at Microsoft
- khingebjerg 5y agoIt looks great, thank you. I think it’s great to introduce accessibility early, but wouldn’t it be a good idea to have a brief introduction to HTML before the accessibility section? Or are you supposed to read about HTML on MDN as part of section 01?
- rgrs 5y agoThanks for making this. Are there beginner courses for other technologies as well?
- jlooper 5y agooh yes! https://aka.ms/ml-beginners https://aka.ms/ml-beginners https://aka.ms/datascience-beginners https://aka.ms/datascience-beginners https://aka.ms/iot-beginners https://aka.ms/iot-beginners and - this is a sneak peek, https://aka.ms/ai-beginners https://aka.ms/ai-beginners, we're just finishing it up :)
- atotic 5y agoThank you! I've scanned over web development, looks like a well thought out modern curiculum. In 2022, it is tough to pick a good path for a beginner, and I like your choices.
- devnulll 5y agoOne of my kids - 10yrs old - has been wanting to learn basic HTML and "programming". We've been going through the W3C with no trouble, and he's learning at an amazing rate. This tutorial is way beyond anything he could approach. For example "Pedagogy" - I don't know what that means, and neither does he. Another example, from the beginning "In this section of the curriculum, you will be introduced to non project-based concepts important to becoming a professional developer." I suspect most of this is translation issues, but given the audience (kids, newbies), this language is super intimidating.
- jlooper 5y agoIt's not really geared towards 10 year olds, although we had a 9 year old contributor, actually! I'd recommend MakeCode for that age group
- AlchemistCamp 5y ago> "Pedagogy" - I don't know what that means It means “teaching methods”.
- devnulll 5y agoThe meta-point is that the usage of complex words is off-putting to those trying to learn something for the first time. There's always an element of "I don't know what this is, so I can skip it" but better to keep topics simple and approachable.
- 0des 5y agowe love our stupid fucking acronyms and pompous terms though, they are right.
- bigDinosaur 5y agoWhat is a 'complex word'? I'm serious. If you google 'pedagogy definition' you get an easy to understand definition. If you're not willing to google things, you aren't ready to be a web developer. Method names alone will drop you way out of the simple english, top 1k words simplification paradigm.
- AndyJado 5y ago
- pdevr 5y agoArguably the best web development curriculum for children that I have seen from any of the top technology companies. Congratulations. One question: Did you consider splitting up these pictures into smaller pictures? As an example, look at this page[1]. The picture seems to have a lot of things in there. Did you consider using multiple smaller pictures? [1] https://microsoft.github.io/Web-Dev-For-Beginners/#/2-js-basics/2-functions-methods/README https://microsoft.github.io/Web-Dev-For-Beginners/#/2-js-bas...
- jlooper 5y agoThank you! It's a particular style of sketchnotes that Tomomi, the artist, has perfected. They images all kind of fit together to give a holistic picture of the topic. One thing, I did a lot of the smaller non-sketchnote art on https://aka.ms/ml-beginners https://aka.ms/ml-beginners, embedded as infographics. So that was a different art strategy.
- dajonker 5y agoI'm not sure I would recommend this for kids. It seems quite abstract and children often have a hard time with abstract thinking. The course starts off with seven lessons on tooling and JavaScript fundamentals before you actually do something in lesson 8. That's a lot of theory to process.
- strangelove026 5y agoI think this is by the CTO of reddit? It's an Udemy course on web development Anyways, here's a slightly dated but really great source of information on web development. I saw the playlist posted in a comment on HN in a similar thread https://www.youtube.com/playlist?list=PLAwxTw4SYaPlLXUhUNt1wINWrrH9axjcI https://www.youtube.com/playlist?list=PLAwxTw4SYaPlLXUhUNt1w...
- acemarke 5y agoOn a related note: I've had to help train a bunch of Java/C++ devs about web dev over the years. I've also talked to a lot of new devs. One thing I noted is that there wasn't a good resource that tried to explain the key pieces of web dev concepts, terms, and technologies, and how they fit together. So, I ended up writing a "How Web Apps Work" blog series to try to fill that gap: https://blog.isquaredsoftware.com/series/how-web-apps-work/ https://blog.isquaredsoftware.com/series/how-web-apps-work/ The series provides an overview of HTTP and servers, client dev, browsers / HTML / CSS, JS / DOM, and AJAX. A number of folks have told me they found the series particularly helpful.
- aastronaut 5y agoI just read through your post on servers[1], as I'm currently in a similar boat (webdev working with C++ devs). I think the biggest hurdle for such developers are things like: - statelessness of the server (REST) - the lifecycle of a single request - the lifecycle of a single (server-)app (microframweworks) OOP devs unfamiliar with server development tend to pollute the app lifecycle with hidden state in some singletons that are swirling around globally. The requirement that servers should be able to parallelize request-processing is mostly an afterthought and hidden app state makes it impossible to parallelize anything. A sequence diagram of a single request would help there a lot IMHO and a short explanation of how to keep the response times short, by doing long-running tasks in the background with message queues. [1]: https://blog.isquaredsoftware.com/2020/11/how-web-apps-work-http-server/ https://blog.isquaredsoftware.com/2020/11/how-web-apps-work-...
- deleted 5y ago[deleted]
- oxff 5y agoThis is better: https://developer.mozilla.org/en-US/docs/Learn https://developer.mozilla.org/en-US/docs/Learn
- winwiz 5y agoOutstanding effort. However, and as usual, some improvements can be suggested. For example, users are asked to execute npm and webpack commands as a part of some lessons. What is npm is explained (by supplying a link), any clarification related to webpack is missing. Those topics could have been expanded upon, perhaps taking the whole space of the lesson devoted to building a browser extension. This subject feels to be more marginal whereas knowing what bundlers do and why is more fundamental.
- pkdpic 5y agoIts probably just me but I guess I teach web dev professionally so I might as well say that I was really excited to see something like this for free from Microsoft but confused to see so much time spent on a canvas app and backend functionality seemingly crammed into the last few sections somehow. I guess it's fine to just have a frontend curriculum but just confused at why this is noteworthy maybe. Im sure this is a big deal for some reason and Im just too dumb to realize why. I honestly wish I had time to go through all of this just to get inside their heads in terms of education strategy etc. Also I kinda hate React but shouldn't they be introducing React or Vue or something? Who's the target audience here? Job seekers? Bored tweens? Time traveling developers from 2005? Me?
- zelphirkalt 5y agoTeaching React would introduce people to something out of FB, but teaching Vue they might. Although it is an Open Source project. If they had an MS clone of it, it would have been in this course for sure. I guess they wanted to have something fun and thought making games is a nice idea, for which they needed a canvas, so they put it in there. The whole course structure does not necessarily seem to be aiming at the most solid teaching principles.
- DeathArrow 5y agoIt's for folks wanting to learn the basics of frontend development. And that means HTML, CSS and JS. Frameworks are optional since web does not mean only single page apps. And even you want a single page app, you can do it without a framework. So learning a framework comes after learning the basics.
- gigatexal 5y agoMy sister in law is doing the web dev freecodecamp courses and loving them. She doesn’t have a background in tech but it’s really heartwarming to see her light up when something she envisions in her head can be made to appear on the screen with some HTML and CSS.
- userbinator 5y agoabout JavaScript, CSS, and HTML basics ...and this is where it goes off the rails; teaching JS before HTML is how we will continue to have the ridiculous proliferation of app-sites that shouldn't require a single line of JS instead needing the latest version of $browser (you have a choice of browser - pick one ...) to even show any content at all. Forms don't need any JS to work, yet the impression this gives to beginners is that they do. https://news.ycombinator.com/item?id=25915313 https://news.ycombinator.com/item?id=25915313 But then again, this is Microsoft, which is now firmly in bed with Google in contributing to the Big Browser monopoly, so I suppose I shouldn't have expected anything else. The agenda is obvious to anyone who cares to look.
- davidelettieri 5y agoLooks like the first few lessons use Javascript to give an introduction to programming and not to web development in general. I don't see any agenda. Just teach programming on the language a web developer will happen to use later.
- KronisLV 5y ago> The agenda is obvious to anyone who cares to look. Alternatively: it's just teaching whatever is popular in the industry, for better or worse (similarly to how DevOps people would be taught Kubernetes, even if it can be horrible in certain cases and for smaller projects). Many sites out there don't need JS. Server side rendering would suffice. And many other sites out there would be well served with minimal JS for enriching a few forms. Yet, that's not the reality that we live in. The reality is that the majority of the developers out there will simply have to deal with lots of JavaScript, TypeScript and frameworks like Vue, React, Angular (i'm using the term "framework" here because they change the entire direction of the development of your front end, not that it matters at all). So, that's what curriculums will focus on, since clearly people want to have good employment prospects. It doesn't seem like the linked one gets too caught up with the frameworks, though.
- dgb23 5y agoBut to master JS tools you want rock solid fundamentals and know about default behavior, writing clean HTML and CSS. I even teach more about networking and HTTP than JS. They actually want to know: what happens when I type an url into the browser?
- nlnn 5y agoI'm an experienced backend developer but always struggled with learning modern web development. I understand all the core well (html, CSS, JavaScript, etc.), but struggle with choosing the right high level abstraction/framework/technology for ideas I want to implement. E.g. should I make it a single page app or not? Should I be using ES6 imports? Which build tool? Would I want React or Vue or something simpler here? Should I use SSR? NPM vs. Yarn? Do I need a CSS compiler? Maybe I should be using TypeScript? Wepback? Basically I'm overwhelmed with choices, but struggle to find useful docs on why a lot of these tools came about, what problems they solve, tradeoffs for using them, etc. Asking the web devs I know in person doesn't help much (“just use React for everything, it's fine").
- dgb23 5y agoIf you’re a backend dev, with solid HTML/CSS and HTTP/REST fundamentals then I recommend you default to using htmx plus server side templates for HTML rendering and interactivity, plus a well documented, simple CSS framework that gives you out of the box components like bootstrap/bulma/semantic. React/web components etc. is when you need advanced/bespoke UI widgets. If you can afford KISS then they only introduce complexity and cost.
- Heyso 5y agoFullstack dev here with more experience in front-end. I struggle too. I'll tried a lot of different things (ex : puppeteer vs cypress, react vs angular2), and I end up having my own preference. I'll try to answer some of your questions : - Should I use SPA ? Slower initial page loading time, but faster to load more pages. Good if typical user stay long on website and navigate multiple pages. - Es6 import ? Use them when you can, better IDE support than require. - Build tool ? Start with webpack, oldest tool, with more chance to find answer to your questions on stackoverflow. Although I have little experience on the others (Rollup, etc), so maybe there is one that is simpler to start with. - React or Vue ? Idk, haven't used view, both are popular and similar, take one you prefer the syntax ? - Something simpler ? Well, there is too much choice... Vanilla js, another cool library, low code or no code like wordpress... - SSR ? Less API to build. Faster initial page loading. Roughly. There is quite a lot of library out there with SSR, and it is elvolving quite fast. The future is probably a mix of server and client side rendering. - npm vs yarn ? I recently played with npm workspaces, and yarn had a feature I needed, otherwise I think sticking to npm is fine. Historically yarn became popular because it introduced .lock file before npm. Npm has since catch up. - Css compiler ? Minifying, or compiling sass ? You can start without it. Also starter like "create react app" already do these optimizations for you. - Typescript ? Use it ! Only exception would be your code is too simple to take advantage of typing.
- defanor 5y agoA bit of bikeshedding (and I'm not an educator, so take that with a grain of salt), and I guess different views on a good curriculum are to be expected, but a few things I noticed upon a skimming: - No basic HTML "hello, world" in the beginning to hook the reader and show that they can easily make web pages. It seems that they should wade through quite a few lessons, including JS ones, before composing the most basic page (assuming no prior knowledge of that). - The first lesson is somewhat thorough, touching an assembly language (which is nice), yet mixes together shells and terminal emulators (which seems okay for a gentle introduction, but potentially confusing). - No historical context (at least in the first two lessons), which is common to omit, but I think it helps to learn the motivation and basic ideas behind the subject you are studying, to better understand it all. - Accessibility is explained before HTML itself, with an HTML-based quiz. I agree it's important, and the lesson looks good, but I imagine it'd be confusing/boring/seemingly unnecessary to read before even the basics of HTML (I'd probably keep thinking of learning how to make actual pages myself). Better understanding of accessibility issues may also come with demonstrations, showing why it's important (otherwise it's probably also easy to dismiss as silly or unnecessary). The lesson also mentions the "Lighthouse" tool, I don't think it's present in Firefox by default (looks like there is an extension). - Then there's a bunch of JS lessons, before learning to make even basic static pages. - Then there's finally HTML introduction, but only introducing 'html' and 'body' tags, and with a lot of--likely confusing to an absolute beginner--attributes in the examples, including classes. - CSS follows those, at which point classes are likely to make more sense. - Then there are JS-based games and web browser extensions, while we've barely learned to make basic HTML pages (though I don't think we really did). - Only towards the end there are HTML forms, after all the interactive JS bits.
- DeathArrow 5y agoThe purpose of Web browsers is to render HTML. Javascript was an afterthought, to make pages dynamic and allow DOM manipulation. It could be Lua, it could be Python. As such I would start learning frontend web development with HTML. You can have web development without JS, but you can't have web development without HTML.
- k__ 5y agoIt's good that they jump in with JavaScript right from the start. This way people learn right away that HTML/CSS are just helper technologies in the whole process of creating Web apps.
- lsbehe 5y agohello sir, how do I create webapp without html/css, thank you
- k__ 5y agoYou don't, but they don't carry any business logic.
- DeathArrow 5y agoIt's the other way around. JS is just a helper and optional technology when creating web frontends.
- devd00d 5y agoA lot of people complaining about a free course from Microsoft? I scanned through it and covers a decent amount of what one wants and needs to know. Plus, it's free. Guess it's impossible to please people nowadays.
- jwsteigerwalt 5y agoThere’s a clear agenda when accessibility is the 3rd course.
- DeathArrow 5y agoIt's ok if you have observations, considerations, criticism and questions about both the curriculum and the method. But if you consider it outright bad for teaching someone web development, like some commeners did, then why don't you consider it a provocation and build your own web development course and show how it can be done better? Anyway, it's free and you are not forced to follow the course. You can extract bits you think might be useful.
- Hardik_Shah 5y ago