The SQL Saturday Foundation Vision

A few things to start. First, this is about SQL Saturday events. Only.

This is NOT about the future of the Summit. Redgate is working on that separately from this project.

This is NOT about user groups, which Microsoft and DCAC are helping, each in their own way. If you are interested in those efforts, or want to help, please contact others that are supporting or managing those events.

Second, this is NOT about replacing PASS or taking over their mission. There is no intention from me, or Redgate, to replace the PASS organization.

Third, this is my vision. This is what I think now, and this is completely subject to change when a board of directors gets together in the SQL Saturday Foundation and starts to vote. I’ll have one of nine votes, and everything I think now could be changed. I may start something in the next few weeks to get SQL Saturdays moving that will get abandoned over time.

That’s fine. The important thing for me is to start moving. With that in mind…

The Vision

I have come to love and appreciate all the different ways that SQL Saturday events have run in the last 14 years. With that in mind, my goal in working to get this foundation set up is to continue to facilitate and promote local, free events organized by individuals in some area.

I see a foundation doing this in a few ways:

  • Hosting a landing page for events
  • Provide a non profit umbrella
  • Tooling that integrates services needed (payment, speakers, registration, etc.)
  • Connecting organizers with mentors or volunteers
  • Collaborating with other events
  • Assisting with fundraising

The first item is easy, and with credits from Azure or AWS as a non-profit, I envision a site like the Data Saturday project to host landing pages for the site. In fact, my first attempt really duplicated a lot of the style from that project.

Likewise, having a non-profit entity is something that needs to get completed. This is likely a US 501(c)(6), allows many organizations to donate to the event and take a tax deduction. Redgate is donating some resources and has engaged lawyers to get this set up.

Tooling

Tooling is more complex. While I think a lot of the tooling from the old SQL Saturday site was useful, some needed work. I don’t anticipate anyone funding this, but I do think their either an OSS project under this foundation, or under Data Saturdays, can help here with the tools needed.

I don’t anticipate tools being an issue in 2021, as most events a likely to be virtual, but 2022 will need some things. What, I’m not sure. The board will need to prioritize and help here, likely with some committees weighing in.

Mentoring

When we started SQL Saturday, a lot of the time and effort in the first few years were mentoring other organizers. No one really knew how to run an event in 2008. Now we have hundreds, maybe thousands of organizers worldwide that can help. Now I don’t anticipate the foundation being more than a repository for knowledge, and a way for inexperienced organizers to connect with and ask questions of others.

That being said, the board will need to disclose their experiences and help us mentor future board members.

Collaborating

I knew last year that SQL Saturday would be in trouble. Part of my concern led me to join the Data Saturdays project. I’ve helped SQL Saturday events that were scheduled move over and supported them. I think it’s a great project, and I hope that I can work with them as part of SQL Saturday.

There may be other projects or event umbrellas, like Sharepoint Saturday, that we can work with, share tooling, help each other with marketing, and more. My goal is to work together to get more events (and more types) rather than compete.

I want more people to experience a one day conference and get inspired by others. I want more speakers sharing in person. And these days, I really want to get back to in person events at some point.

Fundraising

One of the best things I saw from the previous management of SQL Saturdays was the global partner program, which allowed a sponsor to provide a pool of money that would be allocated to events. This reduced the burden on sponsors, which certainly can be a resource issue. It also provided a base for some events to get started in funding their effort.

In order to provide this program, a legal entity is needed. Unlike the former program, this one will look to send 100% of the sponsor funds to events. I would anticipate fees being minimal here, and those ought to be covered under the annual operating expenses of the foundation.

To me, this is the big work of the foundation. Raising money, deciding how to allocate to events, and publicly accounting for every penny.

Overall

We built SQL Saturday to ensure that a lot of people would have the conference experience. They’d get the chance to attend an event, with lots of speakers, with vendors and swag, and get to meet other professionals.

It succeeded beyond any of our expectations thanks to the amazing volunteer efforts of organizers and speakers. SQL Saturday become quite a phenomenon. I want that to continue into the future, with lots of events, lots of volunteers, and lots of collaboration with others.

As I mentioned, this is my vision for now, but subject to the opinions and views of the foundation board of directors.

Posted in Blog | Tagged , , | Comments Off on The SQL Saturday Foundation Vision

Poor Software Testing

I am a big advocate of testing your code, including your database code. I like repeatable testing, especially unit testing. I think this has contributed to the increase in quality over the last ten years as more developers have incorporated unit testing into their work. That, along with the increase in standard frameworks, seems to have resulted in less crashes and instability in much of the software I used today.

That being said, the client ultimately decides if software works as expected. Certainly there can be logic errors, but there also could be errors in how specifications and requests are interpreted. This is one reason we need humans to do some QA testing and clients to ensure there is some user acceptance review.

Apparently that didn’t happen with one election machine. There is a hash that is supposed to be used to verify that the correct version of software is installed. However, if that reference hash isn’t there, the machine still reports things are fine. Certainly an issue that is a problem, though not necessarily one that users would detect. We would expect someone that purchases, updates, or administers these machines to check for the correct version.

That isn’t an issue here because the acceptance testing was done by the vendor. While I am a big advocate of developers checking their work, there needs to be independent evaluation by a CI process, and there ought to be some QA review by another group. Certainly a client ought to be able to double check the software as well, and some client should have done acceptance testing here.

As the world moves more towards DevOps type software development, we need better testing, and that likely needs to include some independent testing outside of the developers and testers. I certainly could see the need for clients to submit some tests and get some verification that those tests passed. Automated CI/CD systems can do this, and provide detailed logs of what happened.

Ultimately we may still have bugs, either because we don’t have enough testing, or we don’t quite write the code that does what client expects. We may also have performance issues, but that’s another testing issue.

We can get better, but we have to work to do so, learning from our mistakes, ensuring we are always improving testing, and listening to feedback.

Steve Jones

Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

Posted in Editorial | Tagged | Comments Off on Poor Software Testing

Daily Coping 24 Mar 2021

I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag. 

Today’s tip is to stop, breathe, and sit quietly for a minute. Repeat a few times.

I breathe often in yoga. It’s helped me to think about my breath at other times in life. However, I often find the workday hectic, with lots of different tasks for me to deal with. I like to power though the day, taking breaks exercise, cook, or maybe play guitar. Often these are “working” breaks.

My task today, and really more days, is to find a way to take a short break multiple times and be. Sit outside, do nothing, just appreciate life.

Posted in Blog | Tagged , , | Comments Off on Daily Coping 24 Mar 2021

The Data Saturday Logo Contest

I’ve been helping with the Data Saturdays project, in addition to trying to get SQL Saturday to grow again. Data Saturdays is looking for a logo, as the site has been a little plain so far.

The admins have set up a design contest, and you can read about this at Monica’s blog. She really did a ton of work to review submissions, ask for our feedback, and deal with designers. Everyone that supports this project owes her a huge debt of gratitude. Please thank her when you see her next.

The design contest is at 99designs, and I think there are some good choices. We picked 4, and you can vote until Friday, 26 March 2021. I grabbed the four designs here, without the extra stuff that might be included. Leave comments and you vote, and let others know.

2021-03-22 16_55_35-Help me choose my new design!2021-03-22 16_55_26-Help me choose my new design!2021-03-22 16_55_13-Help me choose my new design!2021-03-22 16_55_09-Help me choose my new design!

I won’t talk about my favorite, but I like all of these to some extent.

Posted in Blog | Tagged , | 1 Comment