more-coffee

Something not being allowed to learn from hasn't stopped them before

That blog post smells like Opus.

Do you mean that LLMs are unable to use metaphors effectively? (Just clarifying because English is not my first language)

Seems to me like the last thing you want to do is worry whether the LLM has a large enough context window to keep an eye on all duplicates. So I'd argue to deduplicate directly, where possible.

"karate chop flashlight" love this description! That's exactly why I've stayed with Motorola after my G5 just got too slow. I'm now on a Moto G Pro from 09/2020, it's getting fairly slow but all in all it gets the job done.

This. I have argued with plenty of developers on why comments are useful, and the counter arguments are always the same.

I believe it boils down to a lack of foresight. At some point in time, someone is going to revisit your code, and even just a small `// Sorry this is awful, we have to X but this was difficult because of Y` will go a long way.

While I (try to) have very fluid opinions in all aspects of programming, the usefulness of comments is not something I (think!) I'll ever budge on. :)

And in a few million years, the next intelligent life form will examine remains of human texts, and wonder: with all the tools and knowledge they possessed, how could they not have prevented their demise?

(Sorry for pessimism and offtopicism)

I'm trying difft for git now and I also really like it. One reason why I think it shouldn't be the default is that it hides whitespace differences. Maybe that's configurable though, haven't looked into that

It's a tad silly that they made this the default

That is so obvious.. yet I've never thought to try this in 10 years of using git.

And that's why I never trust/use x.0.0 releases because they must have missed something :)

Depending on how much that equality check is deciding the application's performance, jsonifying to compare stuff is fairly ok.

Just beware of any lists which you'll need to sort manually (on both sides) to prevent false negatives :)

I bet they also pulled out the "but the code will change and then the comments become invalid, or even gasp misleading"?

I have done this too for familiarizing with large/complex codebases (i.e. for a C++ game engine). Afterwards I usually felt like it was a waste of time (and paper) as I didn't reach back to those notes often. But that's because they had already served their purpose.