Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I'll add
11. Make a text version. Not everyone can watch YouTube videos at work. Some people are deaf. And some, like me, just prefer a format that has full text search, can be scrolled and reread in any desired speed. -
I really like the videos by CodingInFlow on youtube. He has a big german accent in his speech, but you can understand it. He always uses intelligent zooms and highlighting effects in the video editor to make, for example popup-windows more visible and readable and he always is on point pf his topic.
-
@ScaryException thanks for the recommendation! Accents don’t generally bother me (I’m happy the presenter chose to use a language I know despite it not being his or her native language!).
-
@BlackSparrow I can’t help but think of an Alan Perlis quote when I see a lollipop :P
-
@Codex404 I see it quite a bit on internally-recorded training for my employer
-
@BlackSparrow “When someone says ‘I want a programming language in which I need only say what I wish done,’ give him a lollipop.”
—Alan Perlis, retrieved from http://cs.yale.edu/homes/... -
@blockchaintacos is it me, my sleepyness or is that quote weirdly formed? I just can't undestand what they are trying to say.
-
@blockchaintacos interesting quote @Codex404 i guess the quote is trying to tell us that no programming language can do exactly what our mind wants from it.
Related Rants
Online tutorial pet peeves
————————————
My top 10 points of unsolicited ranting/advice to those making video tutorials:
1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)
2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)
3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)
4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull
5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video
6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time
7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)
8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed
9. Have a game plan (i.e., objectives) before hitting the record button
10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)
rant
videos
online course
pet peeve
tutorials