Explaining the work

View this thread on: d.buzz | hive.blog | peakd.com | ecency.com
·@lloyddavis·
0.000 HBD
Explaining the work
<a data-flickr-embed="true"  href="https://www.flickr.com/photos/lloyd-davis/15649379877/" title="There are lions in #workshop34"><img src="https://farm8.staticflickr.com/7524/15649379877_033dd3855e.jpg" width="500" height="500" alt="There are lions in #workshop34"></a>

Too much "what does it all mean?" of late.  That's not my question to answer.  Or at least, it will get answered, or not, in the fullness of time - answers will come to me, they may come to me via you, maybe.  The work is not to interpret the work for myself or anyone else.  The work is to do the work.

When the work has been done, I've (almost by definition) put a lot into making it as good and right as I possibly could.  Tweaking and trial and error along the way.  But when it's done it stands on its own.  It doesn't need any more from me, I let it go and let it fly. 

That means I will also have a circumspect approach to answering questions about the work.  I'll happily hear from you about what you see in the work, because I am interested in what effects it has on you, as long as we can keep away from what effect it's had on me.  

Because what I think about the work is none of your business.

Overall, what it means doesn't matter.  

What it is, is what counts.
👍 , , , , , , , , , , , , , , , , , , , , , , , , ,