Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Since "standard" users are not going to learn SQL your market is narrowed to developers only.

Power users aren't _that_ narrow a user base. There are an enormous number of data miners (analysts, integrators, etc.) out there who work in Excel because they must, or because they're used to it, or because that's the format that their data arrives in, or because it's a nice visual tool that allows them to easily inspect intermediate results---but who ultimately need to run reports across multiple large spreadsheets. SQL is astonishingly easy for such people, and I've watched dozens of data experts learn it from scratch (with help).

I'd beg you not to add wizards to your product, and instead focus on treating power users rather than being all things to all people. (Your syntax highlighting is good, and little red underlines on unparseable SQL would be good.) Trying to train users to use (or avoid using) SQL with wizards is a dangerous business for a piece of software to be in.

This looks incredibly useful. I'll check it out more thoroughly on Monday.



I agree 100%, I don't think it is wise (at least initially) to water down your product with wizards, etc. Focus on that niche and focus hard.


Thanks for these opinions all.

I can see the arguments both for and against wizards and gui query tools.

On the one hand I personally agree with the jcdreads and viggity. These sorts of interfaces are very difficult to get right and dilute the SQL focus.

On the other hand a number of people have suggested going this way, so people do think it would be useful.

I have no immediate plans to go this way but I intend to be responsive to what customers request.

Cheers


Read up on Joel Spolsky's days at Microsoft trying to build a GUI code-builder for VBScript. Ultimate fail. Too complicated for basic users, too simple for power users.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: