And I need to write the Stuff and About pages.
The 2015 Tableau Conference is next month!
Tableau is usually great about publishing the raw data for the conference sessions, and they did it for this year's conference. I just noticed the web connector data source--that might be fun to play with.
I've been to two previous conferences--Seattle in 2010 and San Diego in 2012. The Tableau conferences are always a mess of sessions. There are many sessions in a few time slots. Many are interesting. Some are done by Tableau community celebrities. Some apply directly to the day job, and you have to go, since the boss is paying the bill.
The tough part about the schedule is picking the sessions and time slots that best fit with my priorities. The viz below lets the user browse the offerings, prioritize, then do some further organization.
The viz is also available here.
My version control usage at my current job is, um, unconventional. And by "unconventional", I mean I get email approvals, I back changed code up, and then I modify production manually. My boss is okay with this because the numbers still match the other numbers, the CEO still gets his daily alerts, and the business keeps humming along.
Just because "it works", it doesn't mean it's "good".
But I want this site to be at least marginally source-controlled, and that means using GitHub (which also provides a cheap and easy web publishing platform). I haven't used GitHub much since I took some Data Science classes on Coursera. I need to brush up on some things.
I need to read these more in-depth, but these two sources helped me get moving:
And here's what I did to get rolling:
git initto get everything levelset. Remember when levelset was a nasty project manager word that we all mocked. Now we all use it? We're sheep.
git config --global user.name "joedonahoe"and
git config --global email.address "email@example.com". That's not my real email address.
git remote add origin https://github.com/joedonahoe/joedonahoe.github.io.
git status. Git said I had one new file (the CSS file) and one modified file (the index.html file).
git add style.cssto add the new file to the local repo.
git commit -m "2015.09.14"because I'm being lazy at writing check-in comments. However, that only picked up the new file. I had to do
git commit -a -m "2015.09.14"to also pick up the changed file.
git push origin masterand my changes were visible on this site in about 90 seconds due to the magic of github.io.
I decided the other day that I needed a place where I can put the kind-of-useful stuff I build as I'm learning new things and practicing things I think I know. I tried WordPress, but I didn't really want a blog. I just wanted a chronological list (this page) and a portfolio (the Stuff page).
So this is that. More to come.
Some design notes:
On that last point, I am writing with the expectation that I am 95% of my own audience. And 2% of the audience is seeing how I work. The other 3% is probably my mother.