4 ms·
People make tutorials for economic reasons, those reasons are not always 100% aligned with the need to help you learn. Making the tutorial increases their prof
by bryanrasmussen 8y ago
People make tutorials for economic reasons, those reasons are not always 100% aligned with the need to help you learn.
Making the tutorial increases their profile, leading to more profitable opportunities elsewhere (because making the tutorial is not as financially remunerative as actually being employed/consulting somewhere).
Furthermore if you make a tutorial as an advertisement for your skills you want to make it as quickly as possible and show off skills that an employer will appreciate. Probably the quickest way to do something, or to decrease the cost of doing it is to work on something you want to make anyway or to adapt something you already made for a client/project. OF course the easiest way is for people to just go ahead and take the official documentation examples and tweak them a bit and now we have a new tutorial showing you how it is done and we have also managed to improve our profile! Everybody wins, only you don't win as much as the tutorial writer.
Because you want to show off skills to the employer you might also have to consider what the skills you think make you bankable - especially if you have a plan as to where you're going. So even though your GraphQl tutorial might not need much on the frontend you may want to throw React/Redux in there because
1. you're good at React/Redux so gotta show that off
2. more code looks more impressive to a lot of people.
Finally, When you make a tutorial on GraphQl you will need to have some sort of backend, frontend etc. so you have to choose something, probably you decide to put those together based on what your skills are, based on what you have that you've worked on that can be adapted to tutorial purposes, and a number of other factors.
At any rate there is not much economic incentive for most people who make tutorials to make the best tutorial for educational purposes that they can make, unless it is their plan to be educators in the future.
- CyberFonic 8y agoGreat response! I always suspected that the motivation for writing tutorials was to showcase the skillset and, of course, the more ... the better. Hence the cramming in of as many technologies as possible into a single solution.
- watwut 8y agoDoes it really work this way? I suspect that tutorial writer who expect basic tutorial to be treated as major showcase is deluding himself. No employer is impressed by basic tutorial on something nor by express being mentioned in it in basic setup.
- bryanrasmussen 8y agoBut the whole complaint of the Ask is the tutorials aren't basic, and nobody is writing the basic tutorials because it doesn't benefit them. It benefits them to throw a bunch of stuff in there to show they follow best practices (like putting a complete test suite into your tutorial). Throwing a bunch of stuff in the mix and showing basic competence also causes people to think they have more than basic competence, because who really performs at their highest for a tutorial? It's not something that you expect an employer to be impressed by in itself, it is part of the whole package - imagine Cuba Gooding Jr. saying 'The Kwan' - a resume of interesting things or maybe just reasonable things, a github profile that has something reasonable in it, writing on subjects that show the keywords we look for that helps them stand out in the crowd. I'm pretty sure I remember reading to write on technology as a recommendation to young developers who want to build 'Great Careers!!! SQUEE!!' (the squee is my cynical, sarcastic side reacting against the pumped up excitement of building great careers) But writing a tutorial that is a little bit more than basic also does other things that employers, HR, and recruiters might take as being important. 1. it shows communication skills, someone who can communicate in writing will hopefully be able to communicate verbally with our team, customers, whoever. 2. If they can write a tutorial maybe they won't be like all these other developers we hire that don't document anything and then the next batch of developers come in and say damn nothing has been documented. 3. They at least feel comfortable enough with this technology to write something down and publish and I looked at the comments and nobody complained they were a hack or sucked, and some people said thanks so I think they should go into our pile of maybes.
- watwut 8y agoI think I know which article you mean, but I really don't think it works that way - on either end. Companies just don't care about your writing. And had they cared about documentation, they would reward writing documentation and people would be more likely to write that. I mentioned express in tutorial about graphql does not seem to me proof of anything much less about such person being comfortable with express. It usually shows that you know that it exists, you can do basic coding and that is pretty much it. People who write tutorials gain very little from it. The structure is more often determined by mimicking other tutorials, writing for himself (e.g. people exactly like me because that is easiest) and writing in a way that is easy and quick to write. Or even more directly, writing literally for yourself so that next time you are wiring the same thing, step by step is available. That is not laziness, before somebody throws it, they are already doing more then those who don't write at all. It is really often written while that person is learning new technology where writing helps you to learn and allows you to keep log. Writing in depth is harder and takes way more time then people who never tried assume.
- tokyodude 8y agoI don't think I'm the exception but I don't write tutorials for money or fame. My name isn't even on them directly. The only way to see I made them is to click the GitHub link which I doubt one out of 20 people click. I think it's just fun to teach. The only other motivation I can think of is it's also frustrating to see people follow bad tutorials full of bad practices. The only way to combat that is to make my own.