Abstract
This page contains a soft introduction to Pyblish from a high-level perspective.
Hidden, underestimated yet always present, wreaking havoc on schedules and source of endless frustration, at the forefront of obstacles lie the human error™.
Let's assume we're about to start a new project.
In the centre, we have our goal and at the rim is our starting point. We're free to start at any point along the circumference and take any path we'd like in order to reach our goal, but ideally we'd head in as straight of a line as possible as it represents the quickest and most efficient way there.
However, as time goes by human error™ throws us off course.
As we struggle to find our way back to that perfect straight line, human error™ doesn't rest but comes back to wreak havoc again and again.
At the end of the day, we barely hit our mark, having taken a detour of great proportion.
There are 2 important factors at play here. One is the severity in which an error occurred. The more severe an error is, the greater the force at which it throws you off course. The other is how long it takes to discover an error. The longer it takes, the more difficult (expensive) the correction.
Simply reducing the time it takes between making an error and finding the error, corrections can be made swift and thus reduce our journey greatly.
And by reducing their severity, we're almost at an ideal length.
And that's what we're here to help you do.
- See also Prevention Versus Detection