I think this is a great question, and I'm interested myself in seeing some of the responses.
I personally have a doc that I edit and add things to that I find interesting. I have tags around what it's related to that I search by. Desktop, Server, Dashboard hack, etc..
Recently our company launched slack across our company. If someone posts something in a channel of interest, someone has the ability to add a reaction to it that is "knowledge-repository" and we are working to automate a pull down of the things posted into a wiki of sorts I guess you could say.
We also have a public slack channel that anyone can join and have a conversation with other tableau users as well. See the blog below for more information.
Hope to see other ideas of how to compile All the stuff
Joining that Slack channel is a great idea. Another tool is to start your own blog. Everytime you learn something neat, write a post about it. You'll learn more by doing this, solidify that knowledge and you'll be helping others too.
For the forum stuff, I just post with enough details and a working example for the harder stuff (or a modified version of the twbx supplied from the forum).
For the really tricky stuff, my personal blog, but I've only posted 1 "super-cool" thing there so far but I have quite a few in the pipeline to be added.
So, for those of you who are posting items publicly - this is the repository that you go back to when you need to reference something when you're working on something professionally? You don't keep anything in a regular Tableau workbook on your hard drive?
So, for those of you who are posting items publicly - this is the repository that you go back to when you need to reference something when you're working on something professionally?
A major reason why I wrote The Cross Join Collection was to be able to easily find these techniques when potentially in need of them myself.
You don't keep anything in a regular Tableau workbook on your hard drive?
The benefits of sharing our notes in a blog or on a forum such as this community are:
- good backup (laptops crash, are stolen, fall on the ground; files are mistakenly deleted and misplaced; ...)
- easy to re-find
- feedback (also a disadvantage because it takes our time)
- it pushes us to make it much better than otherwise knowing it will be seen (and judged) by others
- it is enjoyable to make a good product (write a good articles) that is also valuable to others
- it motivates to write
- appreciation, recognition, etc
- it is easy to share
- better job opportunities (if what is shared is good)
That said, I did keep a copy of The Cross Join Collection on my own computer, but not sure where I stored it
Oooh. Thanks for the link to the Cross Join Collection kettan I'll be sure to check that out. It sounds like that's more the type of thing that I was thinking about for my own collection of cool things.
Heh, I was thinking something similar to Toby's response. I really need to do a brain dump at some point myself, but outside of that I do have several "Here's the way to do this thing" workbooks, which I share with colleagues. In cases where I can make things generic, I see Tableau Public as a good place to bookmark stuff. Also, great tip on the Slack channel, although not sure how many EMEA people are on there regularly.
I started with a Word document (because it was local to each machine I'm using Tableau on via Dropbox, fast, formattable, and editable), eventually I moved it to a wiki at http://drawingwithnumbers.artisart.org/wiki/tableau. And ever since I haven't updated it as much as I'd thought because it's just more of a pain to edit & add content. Since the links and notes are text with the occasional screenshot I do not have that in Tableau because for me Tableau is a terrible tool for that kind of information: it's slow(er than a simple HTML page), requires extra steps to update, and the content in Tableau vizzes is not searchable on the web. Putting my wiki online lets me search it and the rest of the web available via smartphone, tablet, and/or computer. My blog is also a reference source for me, and I've also contributed to the TabWiki.
We have an internal SharePoint site for our small data team. when I come across something really cool, I post it there so that others can learn too. That said, no one else ever posts anything nor looks at the site.
I also started a user group for the folks here that use Tableau. We meet monthly and mostly I help them troubleshoot their problems. If I've come across something cool, I use it as a time to teach them as well. Most are super newbies, so I have to be careful about what I share. They get overwhelmed quickly.
Finally, I keep a tableau learning folder where I stick sample workbooks as others have suggested. It is also where I put workbooks with my own data that I'm dabbling with trying to use something new and cool. right now it is mostly filled with 9.0 stuff as we are still officially on 8.1!
We have a site where I post all the cool stuff I have seen...
Thought I'd throw my hat into the ring on this one...Also to point you to this amazing resource from Ramon (this, I think, is the curated information that Jonathan referred to)
I just wish I was this organised!! (and/or had the time to be!).
My collection of Tableau learning is a little more pragmatic! (...read 'rough and ready').
For any posts I answer, I save the workbook (with a sensible title on what it's achieving) just in a folder, where I use the 'search' to find stuff
For any cool tricks I find I just keep then in another folder (again names by the trick/technique). I then use these as kind of template when I need that trick (and tend to find after I've used it a few times, the method sticks, and I no longer need the original workbook)
For Blogs/Cool-Vizes...etc, a bit old-skool!, but I just favorite them. I have several favorite folders, so they are broadly by theme (for example I have a mapping folder, which is links to things as diverse as ONS Base Maps to Distance Calculations)
A bit of memory is required, as I have to remember I've seen something (but once I get over that hurdle!!) it's generally quite easy for me to find the required information.