julian37
Now, if the instructions were more explicit in forbidding (generic) tool use then perhaps we'd have something to talk about. I'm not surprised a handwavy "we're trying to evaluate you" isn't enough to stop it from trying to make up for its own shortcomings.
Then work on making sure the LLM has all the info it needs. In this example it sounds like perhaps your hypothetical data model would need to be better typed and/or documented.
But yeah as of today it won't pick up on smells as you do, at least not without extra skills/prompting. You'll find that comforting or annoying depending on where you stand...
Amazing how far they've got since, in just two years. As others have pointed out, it's already "boring" software in that it just works. And that's no small feat because this kind of tool requires all kinds of low-level hackery to make work, and make work fast. Hats off!
(Happy user here if you couldn't tell.)
I'd take this article with a grain of salt when it doesn't even mention it, or any of the other alternatives.
https://www.washingtonpost.com/opinions/2023/01/10/baby-form...
https://abcnews.go.com/Business/story?id=3944507&page=1 (2007)
Related: https://undark.org/2023/02/01/for-a-host-of-vital-lab-tests-...
It's something lots of apps need all the time.
https://github.com/google/closure-compiler/wiki/FAQ#closure-...
As for legal or policy reasons, those still aren't reasons to write boilerplate code. Your reimplementation can be tight and reuse other abstractions or include their own.
const Component = (props) => { funcA(props.a.deeply.nested.variable); funcB(); funcC(props.a.deeply.nested.variable); };
Depending on what the functions are doing, neither the VM nor tsc might be able to infer that variable's value stays the same or that props, props.a, props.a.deeply, or props.a.deeply.nested will stay the same for that matter.
The VM will likely have to generate code to dereference the chain all over for the second use, and the compiler might lose narrowing information. Both of these can easily be avoided with destructuring.
(You could use "const variable = props.a.deeply.nested.variable", but then you have many of the same issues the article complains about.)
(Also, in--say--Ruby and JavaScript 1.0/0.0 is Infinity and not NaN.)
Besides, the generated example seems to be missing code to gracefully handle the case where len(filtered) is zero. Maybe there's a precondition that prevents that from happening or maybe a division by zero is exactly what you'd want, but at face value it looks like the bot did a rush job.
Use emacsclient if you want to use it as $EDITOR.
> included are digital (online on desktop and laptop computers, mobile nonvoice and other connected devices), TV, radio, print (offline reading only), newspapers, magazines, radio, and television
Pretty big blunder in an article about media trustworthiness if you ask me.
Just because their other pupils didn't turn out to be legendary doesn't invalidate the teacher's contribution, which is to say, doesn't mean the joke was in good taste.
A random google search turned up this: https://www.birdwatchingdaily.com/news/science/five-bird-spe...
> Researchers have learned that digestive tracts of long-distance migrants work overtime prior to migration. Food intake is increased, and the food is metabolized and stored as fat, which serves as the birds’ flight fuel. Bar-tailed Godwits store fat until it makes up about one half their weight. Then the digestive system shuts down so metabolic energy can be maximized for muscle use.
Astounding.
Brecht wrote "Wer a sagt, der muß nicht b sagen. Er kann auch erkennen, daß a falsch war": he who says A, doesn't have to say B. He can also realize that A was wrong.
https://beruhmte-zitate.de/zitate/126572-bertolt-brecht-wer-...
- Dropping a column doesn't work (assuming the point of dropping it is actual deletion, rather than just hiding it)
- Adding a column doesn't work either
- Changing a column's nullability, default value, or data type doesn't work
- Doesn't help with adding or changing constraints or indexes
One little feature I like in particular is that if you're looking for an ASCII-7 character in a UTF-8 stream -- say, a LF or comma -- you don't have to decode the stream first because all bytes in the encoding of non-ASCII-7 characters have the high bit set. Or as Wikipedia puts it:
> Since ASCII bytes do not occur when encoding non-ASCII code points into UTF-8, UTF-8 is safe to use within most programming and document languages that interpret certain ASCII characters in a special way, such as / (slash) in filenames, \ (backslash) in escape sequences, and % in printf.
It's amazing to hear they put it together in one night at a diner! :-D
Not necessarily so: https://v8.dev/blog/code-caching