Collaboration is a fact of life in software development.
Therefore we must choose tools based not on a single developer’s preference, but by what their colleagues can use effectively.
All of these should be fixed or shunned in favor of languages that are easier to hire, easier to learn, and easier to debug.
It’s an attempt at market segmentation. Those who really want to play will pay full price. Less ardent fans wait for a sale.
Did your friend make you want it enough to pay full price?
No, this is a problem of bad error handling for queries it cannot answer.
A search engine would give empty results instead of hallucinating.
If it doesn’t know how to answer a shitty question, it shouldn’t try to BS the answer.
No answer is better than a wrong answer delivered confidently.
I pooh-poohed ChatGPT when it first came out so I gave it another crack at a technical issue I’ve been avoiding.
Gave me an outdated answer.
Gave me another outdated answer to a URL that doesn’t exist.
Gave me the answer I told it won’t work in the initial prompt.
Scolded me for swearing at it.
This is what’s supposed to replace search engines?
You are that guy in the comic about a modern person blaming serfs for the persistence of feudalism.
Technically correct, the best kind of correct!
It’s frustrating that the article deals treats the problem like the mistake was including Martin’s name in the data set, and muses that that part isn’t fixable.
Martin’s name is a natural feature of the data set, but when they should be taking about fixing the AI model to stop hallucinations or allow humans to correct them, it seems the only fix is to censor the incorrect AI response, which gives the implication that it was saying something true but salacious.
Most of these problems would go away if AI vendors exposed the reasoning chain instead of treating their bugs as trade secrets.
I’m laughing at your little meltdown.
Don’t post about crypto if you can’t tolerate mild mockery.
LOL cry harder
I was just going to laugh but yours works too.
Sorry, that’s not Kosher.
But compared to plastic from virgin fossil fuels?
We as a society are going to need memory cards.
What do you think they should be made out of?
But most steel is recycled and most plastic is not.
Looping single inserts over an open connection is far far slower than a bulk insert because every row is another transaction.
Only thing it’s faster than is if you opened and closed a connection for each row.
Inserting 15k rows of 50 columns into a 50M table is something we do every day.
2100 params on a query sounds like spaghetti code.
I suspect OP is using single row insert statements when they need a bulk insert to be performant.
It’s only hard to tell indentation in Python when the code block gets longer than about a screen, which is usually a sign the code should be refactored into smaller methods.
I started in C before moving on to C++, Java, Ruby and Python.
I’ve had more bugs from missing braces than from misaligned whitespace because the latter is far more obvious when looking at a block of code.
Personal projects vs everything else:
Did you want to collaborate with other people? Use something other people like.