6 ms·

I got quite excited by that entry. My immediate reaction was 'oh, that's really cool'. But after thinking a little further, I can't think of an audience that bo

I got quite excited by that entry. My immediate reaction was 'oh, that's really cool'. But after thinking a little further, I can't think of an audience that both uses SQL frequently and also couldn't use a git repo. What kind of user demographic did you have in mind?

brainless 7y ago
My target audience was basically every non-programmer in a team who wants to see/track any kind of data for their own product. The SQL building would be for programmers to setup say a few initial queries. But anyone can change (there would be a changelog) and share new things to track.
- mjfisher 7y ago
  Thanks; I've yet to meet any sql-wielding non-programmers in the wild. Perhaps it's worth releasing after all?
  - vharuck 7y ago
    Just an anecdote, but my dad learned SQL 10 years before retirement. It helped him do his work, which was not software development, without burdening the professional programmers. Of course, there are plenty of free and slick GUIs offering the basics of Git. I'd like to see how this is better. Maybe customer service?
- cetico 7y ago
  Reportedly you have a lot of customers. How did you find them? Any tips to share? Thanks :-)
quickthrower2 7y ago
SQL queries for non production uses feel more like “quick documents” and having to interact with git every time you want to share would be a pain. (Imagine telling people to share google docs via a git repo). And I say this as a coder who loves git. So many companies will have sql in their wiki docs eg in one note or even in slack for ease of sharing.
dalbasal 7y ago
> an audience that both uses SQL frequently and also couldn't use a git repo. I think you might be surprised. SQL is used a lot in businesses by non-programmers. It's embedded in all sorts of enterprise software, including SME stuff like Salesforce. "Can't" is a strong word. Maybe they could use git, but most don't.
the-dude 7y ago
The Dropbox kind of demographic?

brainless 7y ago

My target audience was basically every non-programmer in a team who wants to see/track any kind of data for their own product. The SQL building would be for programmers to setup say a few initial queries. But anyone can change (there would be a changelog) and share new things to track.

mjfisher 7y ago
Thanks; I've yet to meet any sql-wielding non-programmers in the wild. Perhaps it's worth releasing after all?
- vharuck 7y ago
  Just an anecdote, but my dad learned SQL 10 years before retirement. It helped him do his work, which was not software development, without burdening the professional programmers. Of course, there are plenty of free and slick GUIs offering the basics of Git. I'd like to see how this is better. Maybe customer service?
cetico 7y ago
Reportedly you have a lot of customers. How did you find them? Any tips to share? Thanks :-)

quickthrower2 7y ago

SQL queries for non production uses feel more like “quick documents” and having to interact with git every time you want to share would be a pain. (Imagine telling people to share google docs via a git repo). And I say this as a coder who loves git. So many companies will have sql in their wiki docs eg in one note or even in slack for ease of sharing.

dalbasal 7y ago

> an audience that both uses SQL frequently and also couldn't use a git repo. I think you might be surprised. SQL is used a lot in businesses by non-programmers. It's embedded in all sorts of enterprise software, including SME stuff like Salesforce. "Can't" is a strong word. Maybe they could use git, but most don't.

the-dude 7y ago

The Dropbox kind of demographic?