July 27, 2015 at 12:18 pm
So now that I've survived my very first SQL Saturday presentation, I'm already having thoughts about the next one. I think I have an idea, and wanted to run it past you folks.
I'm thinking about doing something to the effect of presenting data, maybe something along the lines of UX/UI for data professionals. We talk on this forum about what happens under the SQL Server hood, but I rarely (if ever) see any discussion as to what happens above it.
Right now, my idea is in its infancy. I'm thinking about hitting topics such as HTML/web development, AJAX, charts and graphs, and what tools are available.
What sayeth thou, SQL folks? Does this sound like something that would make for good presentation fodder? If so, what should I talk about?
+--------------------------------------------------------------------------------------+
Check out my blog at https://pianorayk.wordpress.com/
July 28, 2015 at 4:27 am
I really don't sweat what happens after I spit the data out. That's the work of developers, UI experts and report writers. But yeah, those people need presentations too. Go for it. Not sure how I'd focus it though.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 26, 2016 at 10:15 am
I'd really love to see 2 classes.
The first would be on deciding on how to consume the data. Should it be an application, a dashboard, a table dump to excel, a report, an alert? What is most appropriate and what should drive the decision to consume the data in various ways. From what I've seen mostly in the wild there isn't much though put into that from end users.
The second would be on how to build a quick gui (hopefully dynamic, a powershell cmdlet would be even better) to do simple data display and crud.
February 26, 2016 at 10:28 am
benjamin.reyes (2/26/2016)
I'd really love to see 2 classes.The first would be on deciding on how to consume the data. Should it be an application, a dashboard, a table dump to excel, a report, an alert? What is most appropriate and what should drive the decision to consume the data in various ways. From what I've seen mostly in the wild there isn't much though put into that from end users.
The second would be on how to build a quick gui (hopefully dynamic, a powershell cmdlet would be even better) to do simple data display and crud.
Hmmm, I'll have to think about this. I do like the idea of decision-making processes when determining how to consume and present data. I'd also have to do some homework before getting into a quick/dynamic GUI; I suspect there'd be a little more that's involved.
I'm running with another idea I have right now; maybe I can revisit this idea once I've finalized the other one.
+--------------------------------------------------------------------------------------+
Check out my blog at https://pianorayk.wordpress.com/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply