The Grand Unified Theory of Documentation
– David Laing

There is a secret that needs to be understood in order to write good software documentation: there isn’t one thing called documentation, there are four.

They are: tutorials, how-to guides, technical reference and explanation. They represent four different purposes or functions, and require four different approaches to their creation. Understanding the implications of this will help improve most documentation - often immensely.

• Tutorials - Learning oriented
• How-to guides - Problem oriented
• Explanation - Understanding oriented
• Reference - Information oriented

It’s truly amazing how little we can achieve in a day, and how much we can achieve in a year. But discipline and patience have always been my Achilles heel, and none of the habit self-help mumbo jumbo seemed to help.

Turns out, I’ve been framing my workouts, learning, and work stuff completely wrong. The goal is not to push yourself to the redline every day — that simply never lasts. The goal is to work so little you have to ask yourself, is that it? And then realize that “if this is so simple, I’ll definitely do this again tomorrow.”

Here’s the concept explained by some of the world’s leading coaches, teachers, and researchers.

Whether you’re brand new to the world of computer vision and deep learning or you’re already a seasoned practitioner, you’ll find tutorials for both beginners and experts alike. Here are some of the most popular categories and tutorials on the PyImageSearch blog.

BigBlueButton enables you to share your audio, slides, chat, video, and desktop with students. Built-in polling makes it easy to engage students and recording your lectures means that you can make them available for later review.