Remember how SQL (still called SEQUEL) was supposed to make non-techies able to talk to computers?
-
Remember how SQL (still called SEQUEL) was supposed to make non-techies able to talk to computers?
> there is also a large class of users who, while they are not computer specialists, would be willing to learn to interact with a computer in a reasonably high-level, non-procedural query language. Examples
of such users are accountants, engineers, architects, and urban planners
https://dl.acm.org/doi/epdf/10.1145/800296.811515How quaint!
Anyway, tell me again how LLMs are making non-techies able to talk to computers. 👀
It's not that unrealistic. I knew a couple of secretaries at a former employer who kept getting asked to do reports, bought themselves SQL books so they could generate reports directly.
As a software developer I'd sometimes ask their advice on quirks about the database.
Their skills got them promoted to "administrative assistant" positions.
But the problem has never been that computer languages are hard to learn. It is that knowing how to solve abstract problems by organising and manipulating information is a skill that people don't want to pay for.
-
@rysiek
Scotty: "Computer, write me a prompt for this other computer...."@spytfyre @rysiek Voice recognition and prompt engineering? This can only go well: https://www.youtube.com/watch?v=HbDnxzrbxn4
-
Remember how SQL (still called SEQUEL) was supposed to make non-techies able to talk to computers?
> there is also a large class of users who, while they are not computer specialists, would be willing to learn to interact with a computer in a reasonably high-level, non-procedural query language. Examples
of such users are accountants, engineers, architects, and urban planners
https://dl.acm.org/doi/epdf/10.1145/800296.811515How quaint!
Anyway, tell me again how LLMs are making non-techies able to talk to computers. 👀
@rysiek You need to go to SQL (school) and take a SQL (sequel) to not break your SQL (skull).
-
@rysiek Not only that, but I remember MS Access being sold as making databases so easy, your CEO can use them - and having to clean up the aftermath.
It used a query language similar to, but not quite the same as, SQL :headdesk:
-
@rysiek Not only that, but I remember MS Access being sold as making databases so easy, your CEO can use them - and having to clean up the aftermath.
It used a query language similar to, but not quite the same as, SQL :headdesk:
-
It's not that unrealistic. I knew a couple of secretaries at a former employer who kept getting asked to do reports, bought themselves SQL books so they could generate reports directly.
As a software developer I'd sometimes ask their advice on quirks about the database.
Their skills got them promoted to "administrative assistant" positions.
But the problem has never been that computer languages are hard to learn. It is that knowing how to solve abstract problems by organising and manipulating information is a skill that people don't want to pay for.
> But the problem has never been that computer languages are hard to learn. It is that knowing how to solve abstract problems by organising and manipulating information is a skill that people don't want to pay for.
Exactly this is my point. And that no technical solution will ever exist for this particular social problem.
-
-
@rysiek BASIC was my first programming language!
...wait, it's worse. I have forgotten the language, other than it having GOTO and GOSUB.
@KatS add IF, RETURN, FOR and NEXT and that was basically all of BASIC.
Really great for writing spaghetti code. Complicated almost like assembler, but much slower!
-
Remember how SQL (still called SEQUEL) was supposed to make non-techies able to talk to computers?
> there is also a large class of users who, while they are not computer specialists, would be willing to learn to interact with a computer in a reasonably high-level, non-procedural query language. Examples
of such users are accountants, engineers, architects, and urban planners
https://dl.acm.org/doi/epdf/10.1145/800296.811515How quaint!
Anyway, tell me again how LLMs are making non-techies able to talk to computers. 👀
@rysiek I had exactly the same idea: there was era, when databases, including SQL, were marketed as solution for everything and supposedly, no one will have to do programming any longer. And if we were about to do programming anyway, we would do it by clicking by mouse and drawing algorithms (which of course never happened...)
(except there was parallel rise in spreadsheets, which did almost the same thing, but differently...)
-
-
Remember how SQL (still called SEQUEL) was supposed to make non-techies able to talk to computers?
> there is also a large class of users who, while they are not computer specialists, would be willing to learn to interact with a computer in a reasonably high-level, non-procedural query language. Examples
of such users are accountants, engineers, architects, and urban planners
https://dl.acm.org/doi/epdf/10.1145/800296.811515How quaint!
Anyway, tell me again how LLMs are making non-techies able to talk to computers. 👀
@rysiek hahaha the ERP system the company I work for is using just switched their whole DB-system around to be able to give their customers an AI-supported drag and drop GUI "no-code" alternative to SQL.
It is limited in its abilities and soooo painful to use. Before SQL queries have been free. Now "code" queries cost as well as the "no code" alternative.
They promised their AI would transfer the old queries to their new DB structure.
IRL only the most simple ones have been transferred and I had to redo most queries.
Everyone in the "community" (aka customers who can't easily escape) is hating it while they are celebrating it as the new hot shit.