sidenote: I'm scared of what's going to happen to those roles!
sidenote: I'm scared of what's going to happen to those roles!
Q: show me the top 5 customers by total sales
A: System.Data.Odbc.OdbcException (0x80131937): ERROR [57014] ERROR: canceling statement due to statement timeout;
Q: Why do I get this error
A: Looks like it needs an index, let me create that for you. Done. Rerunnign query.
could not close temporary statistics file "pg_stat_tmp/global.tmp": No space left on device
Q: Why this error
A: 429 Too Many Requests
Rub hands... great next 10 years to be a backend dev.
The question is do they still need 10? Or 2 would suffice? How about 5?
This does not need to be a debate about the absolutes.
I am hoping Jevon will keep employing me. He has been a great boss for the last 25 years TBH.
It doesn't work because the PHB doesn't have the domain knowledge and doesn't know which questions to ask. (No, it's never as simple as group-by and top-5.)
I suppose this could be useful in that it prevents everyone in the company having to learn even the basics of SQL which is some barrier, however minimal.
Also the LLM will presumably be able to see all the tables/fields and ‘understand’ them (with the big assumption that they are even remotely reasonably named) so English language queries will be much more feasible now. Basically what LLMs have over all those older attempts is REALLY good fuzziness.
I see this being useful for some subset of questions.
The project manager also won't learn behat and write tests.
Your client also won't use the CMS to update their website.
Do human reviewing and correcting of the updated documentation. Then ensure that the AI knows that the documentation might still contain errors and ask it to do the 'actual' work.
To give you an extreme example, I can ask 1000000 different models for a counterexample to the 3n + 1 problem, and all will get it wrong.
For reference: https://en.wikipedia.org/wiki/Collatz_conjecture
So no, sampling 1000000 LLMs will not get you a solution to it. I guarantee you that.
If you want to scale back, many programming problems are going to be like this, too. Failure points of different models are correlated as much as failure points during sampling are correlated. You only gain information from repeated trials when those trials are uncorrelated, and sampling multiple LLMs is still correlated.
Is that the correct answer to "write a lock-free MPMC queue"? That is a coding problem that literally every LLM gets wrong, but has several well-known solutions.
There's merit to "I don't know" as a solution, but a lot of the knowledge encoded in LLMs is correlated with other LLMs, so more sampling isn't going to get rid of all the "I don't knows."
Thats cute.
Nuanced BI analytics can have a lot of toggles and filters and drilldowns, like compare sales of product A in category B subcategory C, but only for stores in regions X,Y and that one city Z during time periods T1, T2. and out of these sales, look at sales of private brand vs national brand, and only retail customers, but exclude purchases via business credit card or invoiced.
with every feature in a DB (of which there could be thousands), the number of permutations and dimensions grows very quickly.
whats probably going to happen, is simple questions could be self-served by GenAI, but more advanced usage is still needed interention by specialist. So we would see some improvement in productivity, but people will not lose jobs. Perhaps number of jobs could even increase due to increased demand for analytics, as it often happens with increased efficiency/productivity (Jevon's paradox)
i suppose the desktop app can use it, but how good is it for this general purpose "chat with the database for lightweight analytics" use cases is it worth the trouble of dealing with some electron app to make it work?
Agents will become ubiquitous parts of the user interface that is currently the chat.
So if you bother with a website or an electron app now, MCP will just add more capabilities to what you can control using agents.
when i've read through documentation for mcp servers, it seems like the use cases they've mostly been focused on are improving effectiveness of programming assistants by letting them look at databases associated with codebases they're looking to modify.
i understand that these things are meant to be generic in nature, but you never really know if something is fit for purpose until it's been used for that purpose. (at least until agi, i suppose)