TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Learn new technology through writing a tutorial about it

173 点作者 nanxiao将近 7 年前

30 条评论

akerro将近 7 年前
That&#x27;s how we ended up with 1000s of garbage quality tutorials for android development. I was once looking how to save app specific data and all top 10 tutorials in google and DDG were saving data to userspace by creating new directory called something like &#x27;myapp&#x27;. Years later Google had to create a series of tutorials with Udemy (as I recall) to actually tell people how to do things in a not stupid way.<p>Please don&#x27;t write tutorials about things you do NOT know. Newcomers will visit your blog and think you&#x27;re an expert and do it this way.
评论 #17364062 未加载
评论 #17363789 未加载
评论 #17364878 未加载
评论 #17363897 未加载
评论 #17363739 未加载
评论 #17365140 未加载
评论 #17367267 未加载
评论 #17363710 未加载
评论 #17367138 未加载
评论 #17366366 未加载
评论 #17363726 未加载
评论 #17367380 未加载
评论 #17363861 未加载
amorphous将近 7 年前
Yes, please write your tutorial. The best way to learn something, by far, is to teach.<p>To those who say &quot;but we don&#x27;t want another crappy tutorial we only want to hear from experts&quot; I heartily disagree.<p>First, it is your responsibility as a learner to decide if something makes sense or not. You can not and should never just believe something on the internet. Even experts get things wrong. Keep asking &quot;why&quot; while learning.<p>Second, experts are far detached from the beginner&#x27;s mindset and often lack the ability to explain something in simple terms. Someone who is a few steps ahead of you will have a better chance to explain things in your language.<p>We need to spread more knowledge, not less. A beginner&#x27;s experience with learning a new technology is valuable knowledge, even if some details may not be correct. As long as the reader keeps his critical thinking hat on, we all win.
评论 #17364541 未加载
评论 #17365182 未加载
评论 #17363924 未加载
评论 #17366450 未加载
评论 #17368166 未加载
评论 #17366673 未加载
评论 #17363923 未加载
评论 #17369976 未加载
k1ns将近 7 年前
In my opinion, we have far too many &quot;Getting Started With [technology]: Part 1&quot; tutorials and not nearly enough lessons on advanced topics. I get it, creating these lessons takes time and dedication that often isn&#x27;t apparent until you&#x27;re nearly done. I&#x27;ve started work on combating this phenomenon myself by creating lessons that do cover advanced topics but even those fall short of where I&#x27;d like them to be.<p>When it comes to &quot;writing a tutorial&quot; for the benefit of your own knowledge, it&#x27;s been proven to work. This is very good advice when it comes to personal gain. However, for the sake of beginners and content creators that are active in the tutorial community, please consider throwing out these lessons when you&#x27;re done. It might help someone out there at some point but you have to take into account your initial motive: personal advancement. Lessons that are taught out of passion for teaching and advancing the knowledge of those around you are often the best because they come from a selfless place. Lessons created for the creator&#x27;s own advancement are often not as helpful. This is something I struggled with when creating my own tutorials. Was I creating it out of love for teaching others, or was there some hidden motive that even I might not be aware of?<p>This is simply my own opinion, take my comment with a grain of salt. I&#x27;d be interested to hear what others think about the prevalence of &quot;beginner&quot; tutorials juxtaposed with an apparent lack of those that would be considered &quot;advanced&quot;.
评论 #17367242 未加载
ggambetta将近 7 年前
Write all the tutorials you want -- teaching is a good way to verify and refine your own understanding -- but <i>please</i> don&#x27;t feel compelled to publish them! As other posters have said, this is how we end with thousands of low quality tutorials and bad StackOverflow answers.<p>Publish if you have something new to say, or a new way to say something. The (very very few) articles I&#x27;ve published fall mostly into the second category, and have been extremely well received.
评论 #17367417 未加载
评论 #17367022 未加载
dschuetz将近 7 年前
I&#x27;ve tried that, but I found that writing a tutorial consumes too much time when writing for a wide audience. So, I started writing tutorials for myself. It&#x27;s brief, covering the most important steps which do not explain much, but it gets the job done. That way I needn&#x27;t going through the research process all over again for the same thing I did some years ago. Later I might decide to share that knowledge, but again, editing it for a larger audience costs time.
评论 #17363974 未加载
评论 #17363716 未加载
thewhitetulip将近 7 年前
This is a touchy topic.<p>I learnt Go programming language &amp; writing webapps in it after reading loads of books and articles which suffered from the curse of knowledge.<p>I&#x27;d start with the first few chapters and then would be totally clueless.<p>I figured out that the curse of knowledge is huge. Once you learn how to write webapps they become trivial and that&#x27;s the reason why few books written by &quot;experts&quot; targetting newbies are utterly of no use.<p>But of course that doesn&#x27;t absolve the tutorial creator from her responsibility of writing a decent tutorial and with the advent of Github it has become a collaborative effort!<p>It is a sad thing that masters write books for beginners. No, a beginner shouldn&#x27;t be taught how to use the stdlib, they don&#x27;t understand half of the things (prose) mentioned in the book.<p>Lead by examples, show that it is not magic and that it is actually very easy to write a webapp in Go but it ia difficult to write a really good one.<p>Link to my tutorial:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;thewhitetulip&#x2F;web-dev-golang-anti-textbook" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;thewhitetulip&#x2F;web-dev-golang-anti-textboo...</a><p>I later did the same with Vue.js and Python but didn&#x27;t get time to finish&#x2F;update them.<p>I also run or used to run a youtube channel which also has got good positive feedback from new comers because they get to the point with practical examples
rcarmo将近 7 年前
The article is extremely short, but the three points it makes resonate with my experience--but not the title, since I usually end up writing tutorials about subjects I am already quite familiar with but written with a specific audience in mind (my own tech teams in the past, specific customers these days).<p>Regardless, the points are valid:<p>1) You will find that you need to clarify what for you are intuitive leaps or gaps in detail so that someone else understands them<p>2) Peer review and feedback often improves the quality (and reach) of your document<p>3) Language matters. Regardless of language skill improvements, reach is paramount, and I recall when it was somewhat unpopular to write technical documentation in English in my neck of the woods.<p>Today that&#x27;s mostly moot, but something to consider.
MetallicCloud将近 7 年前
As an anecdote, when my team was moving to c++11 I decided to give a presentation on the important features, and when they should be used\avoided. I thought it would take a couple of hours to make a presentation, however it ended up taking me a fair bit longer because once I decided I wanted to tell other people about features, I felt I needed to know them inside out to be able to explain the inevitable questions.<p>What ended up happening was I gave my presentation and (I hope) the team learned a bunch, but I probably got the most out of it I think. I understand a lot of those concepts at a deeper level than I did before, and it&#x27;s helped me a lot in my career.
LandR将近 7 年前
I do back-end C#, mostly.<p>If you try and find tutorials or examples on something in C# I would say that 90% of it&#x27;s pure garbage<p>Yet the bloggers of these pieces write in such a way that someone with little experience would look at it and think the blogger knows what he is doing. Often the code is so far removed from what would be deemed production ready that the trivial, and poorly implemented, example is absolutely worthless at best and at worst quite misleading.<p>I don&#x27;t understand the ego of wanting to have a blog and talk about something you clearly aren&#x27;t an expert in.
评论 #17367685 未加载
评论 #17365730 未加载
评论 #17364192 未加载
评论 #17364222 未加载
Rotdhizon将近 7 年前
This is good on paper, bad in practice. One of the best ways to retain and understand information is to explain it to yourself. As in talking, having a conversation with yourself(I do this very frequently). It makes sense that to show you understand something at least on a beginner level, to create a blog&#x2F;video&#x2F;tutorial to teach others about what you just learned. As many others have stated though, this leads to a mass of useless tutorials being created and pushing down the actual good information about that topic in search engines.<p>There are ways around it, disclaimers are a good start. I&#x27;d put in a very visible style, a note that says something like &quot;I by no means am an expert in the field, I only just learned about this topic and am creating this tutorial to try an re-enforce my own knowledge. This information is not assured to be valid in any way and it should not be cited or used as such.&quot;<p>Even after saying that, I&#x27;d still encourage this behavior on personal blogs. No one should be taking technical information from a personal blog without additional research on a topic anyways. Many people have blogs for themselves, not others. The action of some people stumbling upon a personal blog is just a coincidence&#x2F;bonus. Back when I was first getting into infosec, I&#x27;d write personal tutorials on exploit techniques(cross-site scripting, SQLi, LFI, RFI, etc). I never posted them, because I didn&#x27;t care for anyone to read them. They were just for me so that I could re-enforce what I already learned.
bryanrasmussen将近 7 年前
Is this what people are doing on all those little technology blogs where they talk about some particular technology and it&#x27;s always the same code with just slight alterations used as examples? Cause I noticed this yesterday when I wanted to find a particular example of Object destructuring.<p>on edit: changed object deconstruction to object destructuring, error came from hurried writing just as train came into station and I needed to run.
mosselman将近 7 年前
I&#x27;d rather read tutorials from experts to be honest.
mattlondon将近 7 年前
+1 - I find that this is a great way to learn new things.<p>I personally felt like I was falling behind on modern java (generally I only do golang + typescript at work) so I started building a website with some simple examples&#x2F;tutorials with small commentary partly to give me an excuse to write something using the new toys, and partly as a quick reference for myself. I was inspired by the gobyexample.com site.<p>If anyone has any comments on what I&#x27;ve done so far, I&#x27;d be keen to hear your thoughts:<p><a href="https:&#x2F;&#x2F;byexample.xyz&#x2F;" rel="nofollow">https:&#x2F;&#x2F;byexample.xyz&#x2F;</a><p>One thing that bothers me about this &quot;learn it yourself then tell others&quot; appriach is I am concerned that I might be missing best-practice and the general zeitgeist on what is &quot;the way it is done&quot;. E.g. years ago gradle was the &quot;way it was done&quot; in Java for config management, but what is it now? I&#x27;ve got no idea.<p>How do other people handle this? Apart from wildly searching around, how do you keep abreast of current trends and best-practice for development if you&#x27;re not living and breathing it in the day job&#x2F;open source?
tenaciousDaniel将近 7 年前
Yesterday I was learning React, and I wondered whether there was a React abstraction for http requests. So I found a tutorial for making a request in React, and it was spread over 3 different articles.<p>The first article was about how to install React. The second article was about how to set up a basic click event in React. The third article showed you how to use a 3rd party JS library for making an http request.<p>...
norswap将近 7 年前
From experience, this works.<p>But once you&#x27;re done, consider whether or not you should publish the tutorial. At a minimum, have it reviewed by people that are in the known, and will give you honest feedback (insist on that).
shekhargulati将近 7 年前
I did something similar in 2016 where I wrote tutorial on new technologies almost every week <a href="https:&#x2F;&#x2F;github.com&#x2F;shekhargulati&#x2F;52-technologies-in-2016" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;shekhargulati&#x2F;52-technologies-in-2016</a>. You learn a lot but as you don&#x27;t end up using them you forget them .
评论 #17364165 未加载
wordpressdev将近 7 年前
After procrastinating for quite some time, I finally picked up Python and fortunately got a web scraping assignment. Once I did the job, I thought to share the process online so that others may benefit from it. [0] and [1]<p>As I deep diver into the wonderful world of Python, I plan to document my Pythonic journey, noting that things of interest, the obstacles I come across and how I try to push my way through them.<p>[0]: Web scraping with BeautfiulSoup and Requests in 20 lines of code. <a href="http:&#x2F;&#x2F;www.kashifaziz.me&#x2F;web-scraping-python-beautifulsoup.html&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.kashifaziz.me&#x2F;web-scraping-python-beautifulsoup.h...</a><p>[1]: A proxy rotation script. <a href="http:&#x2F;&#x2F;www.kashifaziz.me&#x2F;proxy-server-rotation-python.html&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.kashifaziz.me&#x2F;proxy-server-rotation-python.html&#x2F;</a>
kaushalmodi将近 7 年前
I agree with the OP. Learning anything new is best done by noting down even small taken-for-granted things, things that you wouldn&#x27;t care much about once you have mastered that thing.<p>I have been using this technique to learn the Nim programming language.<p>I write notes (semi-tutorial) about this language as I learn more about it. I explicitly mark things as &quot;need to understand&quot; or &quot;todo&quot; so that anyone browsing these notes knows that it&#x27;s not written by a Nim expert but a Nim learner. And also the notes as strictly labelled &quot;Notes&quot; to make that explicit.<p>The notes: <a href="https:&#x2F;&#x2F;scripter.co&#x2F;notes&#x2F;nim&#x2F;" rel="nofollow">https:&#x2F;&#x2F;scripter.co&#x2F;notes&#x2F;nim&#x2F;</a> (continuously work in progress)<p>This is the best experience I&#x27;ve had of learning so many other programming languages in the past.
评论 #17364455 未加载
flaviocopes将近 7 年前
I think that trying to explain something, is the best way to learn things.<p>You can go through 10 tutorials and think you &quot;got&quot; something, until you need to articulate it and you realize maybe you missed some step. Of course I&#x27;m generalizing, but I also find this process helps &quot;stick&quot; things into my mind. I might completely forget something 1 week from now if I don&#x27;t put it into writing.<p>I also find a huge waste keeping things on my computer, so I publish them. I started doing this on my blog <a href="https:&#x2F;&#x2F;flaviocopes.com" rel="nofollow">https:&#x2F;&#x2F;flaviocopes.com</a> with the things I knew already, and of which I had already lots of notes spread around, and then when I got &quot;tired&quot; of this I turned this into learning new things as well. I mix and match these approaches.<p>Sometimes I go into &quot;series&quot; of posts to dive into a tech for many days in a row.<p>I might search something on Google and spend 1 hour looking for the correct answer on SO or other blogs, and when I finally get the &quot;canonical&quot; one buried somewhere, or some different but valid solutions, I write a blog post to make it my canonical in the future (I find I very often reference my posts and update them as I go).<p>Writing down things as a learning process is worth it even if you just target yourself. I don&#x27;t write to teach anyone. I write to learn, then if the result is good I think it&#x27;s a disservice not to share the work with others.<p>Then I agree that crappy tutorials are not worth sharing most of the times. If you target beginners it&#x27;s cool to write basic stuff, but it should be a nicely crafted content rather than rushing things and copy&#x2F;pasting examples taken from somewhere else.
moomin将近 7 年前
This is not a bad idea, but it’s not guaranteed that said tutorial will be worth reading.<p>Take a look at a Monad tutorial to see what I mean...
dalacv将近 7 年前
Or create a Udemy Course about it and make money while learning
评论 #17364184 未加载
oldcynic将近 7 年前
As a few other comments, and the well known adage, have noted the best way to learn something is to teach it.<p>But I do take issue with &quot;write a tutorial about it&quot;, quite strongly.<p>Why is teaching so helpful to learning?<p>It forces you to reuse those recently forged bits of memory by accessing it, along the way it shows up any gaps or misunderstandings. Like rubber duck debugging the mere act of talking through an explanation shows up the gap, and you&#x27;re missing the next sentence. Now you know what you need to read up on, or clarify.<p><i>Here&#x27;s the crucial bit that writing a tutorial will give you NONE of:</i> In teaching you will explain vaguely, you&#x27;ll encounter loads of people who thoroughly misunderstand your simple and obvious explanation of, let&#x27;s say, C pointers. Your explanation might even have been great but surprisingly they got distracted by their phone. Then ask all sorts of inconveniently difficult questions about why their pointer increment is doing strange things, or why the compiler is not happy. You&#x27;ll sometimes even become completely lost trying to debug someone else&#x27;s trivial example code.<p>I think the <i>whole point</i> of the advice to teach something to learn it is this second part. It&#x27;s the difficult and inconvenient questions that do wonders for your knowledge. Even someone asking &quot;but why?&quot; can have you realising something you just accepted isn&#x27;t actually that obvious. It takes you far off the few well worn paths in your memory of the subject. Writing a tutorial achieves none of this as you&#x27;ll mostly write tutorials on the few things you think you know. But don&#x27;t.<p>Thank you for making the internet worse.<p><i>Teach, then write a tutorial.</i><p>You don&#x27;t need to be years ahead, or subject expert, just weeks or months. Pair programming over skype is just fine. One of the most ridiculous things my second employer did was insist that anyone attending a course taught the others in the office what the course covered the week after. Remarkably useful policy looking back.
overcast将近 7 年前
Every time I read extensive tutorials, blog posts, what have you about something. I think to myself, damn, these guys have a lot of extra time on their hands. Generally I learn new things, by building something, and then building something that builds up upon that. I can&#x27;t see stopping to write about it too! I dig it though, I do, without you I wouldn&#x27;t have learned a lot of things. But it always amazes me the dedication to put all of that together, while working on other things.
评论 #17365841 未加载
DrinkWater将近 7 年前
Of course, writing a tutorial about something gives you a way more thorough learning experience, but it is way more time consuming.<p>For me personally it works best if i use a technology productively. You will face challenges very fast and solving these will give you a huge boost of enlightenment.<p>Writing a tutorial is similar, but it adds the complexity of explaining it to the reader.
评论 #17365131 未加载
评论 #17364100 未加载
sus_007将近 7 年前
I feel the effort I put onto writing tutorials might be well invested in furthering my knowledge on that topic instead. There are plenty of books &amp; YouTube videos, even the official documentation to go through if one desires to learn the fundamentals and beyond.
vorotato将近 7 年前
If there&#x27;s anything we can learn from the activity levels around this post it&#x27;s that you&#x27;re better off writing a blog post about writing a blog post about development than you are writing a blog post about development.
评论 #17368176 未加载
tjpnz将近 7 年前
Assuming you have some grasp of reality it&#x27;s a pretty good exercise for Dunning–Kruger self-diagnoses. If you can write on a nontrivial subject without encountering it you&#x27;ve basically mastered it.
melling将近 7 年前
this is saying is the old adage “if you want to master something, teach it”<p>Personally, when I wanted to learn Swift, I found it useful to create a Github repo of example programs demonstrating a concept. I can easily update them for new versions of Swift and iOS.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;melling&#x2F;ios_topics&#x2F;blob&#x2F;master&#x2F;README.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;melling&#x2F;ios_topics&#x2F;blob&#x2F;master&#x2F;README.md</a>
rutgar将近 7 年前
Great idea, similar to the feynman technique.
Tomte将近 7 年前
It worked extremely well for Mark Pilgrim.