Ironically it was only yesterday that someone asked "Ask HN: Why do tutorial writers combine 10 technologies when 1 or 2 would do?"[1]
I think this is a perfect example of how not to write a tutorial. It doesn't actually teach anything - instead it is effectively a set of commands that someone should type in exactly and it will work.. hopefully.
I think this point in the introduction sums up this approach:
I’d like to point out that the broken branch wasn’t working for some (still) unknown reason related to versioning between when we set up the system and when we upgraded some of the components including nodejs.
and later:
Note for the app we created we used nodejs v8.10.0 and npm v6.4.0, although installing newer versions shouldn’t be an issue.
So.. they don't know why it broke, but any newer version should be fine.
Yeah, that's why in the 'Lessons from Docker' section in point #3 I mentioned that docker might be better off for larger projects, since it seems excessive, especially for small projects. The point of this exercise was to learn more about the technology itself, this clearly isn't a viable way of doing things in production though :) Thanks for the feedback!
Comments
Ironically it was only yesterday that someone asked "Ask HN: Why do tutorial writers combine 10 technologies when 1 or 2 would do?"[1]
I think this is a perfect example of how not to write a tutorial. It doesn't actually teach anything - instead it is effectively a set of commands that someone should type in exactly and it will work.. hopefully.
I think this point in the introduction sums up this approach:
I’d like to point out that the broken branch wasn’t working for some (still) unknown reason related to versioning between when we set up the system and when we upgraded some of the components including nodejs.
and later:
Note for the app we created we used nodejs v8.10.0 and npm v6.4.0, although installing newer versions shouldn’t be an issue.
So.. they don't know why it broke, but any newer version should be fine.
[1] https://news.ycombinator.com/item?id=18950679
Yeah, that's why in the 'Lessons from Docker' section in point #3 I mentioned that docker might be better off for larger projects, since it seems excessive, especially for small projects. The point of this exercise was to learn more about the technology itself, this clearly isn't a viable way of doing things in production though :) Thanks for the feedback!
Also thought about that other thread.