more-coffee
more-coffee on Hacker News
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.
I always have been and always will be against the walrus operator. I don't care how much anyone tries me to sell it on its elegance. There's just no _need_. It's already the #1 example of wtfpython
https://github.com/satwikkansal/wtfpython#-first-things-firs.../rant. Those kind of features are going to keep coming anyway, I'm afraid.
Borg is supposedly a bit faster, restic supports a ton of backends
https://github.com/restic/restic/issues/1875
Also restic does not allow to backup unencrypted.
I haven't used borg. Only done some maintenance on restic backup jobs at work. Restic's command design is intuitive and the documentation is good. But Borg looks just fine in that regard as well.
Yeah, I don't think the internet can be fundamentally altered to the extent that it could be regulated. Unless it somehow becomes a major priority for the world leaders - in which case I'll bet we can say goodbye to any privacy we still had.
It's been said before plenty of times, but I think the solution has to be sought in increasing awareness of the dangers of the internet. Compare it to the electrical grid. 99% of people would not mess with it without consulting/hiring an expert. Not just because it's illegal, but because of the obvious danger. But for the informational grid, "nobody" (exaggerating) cares because they cannot oversee the consequences.
Problem then is, how do you educate people about this... I don't know.
You say you're human, but how can we know for sure?
This entire thread is surrealistic and giving me Blade Runner vibes.. I love it.
That's a good one. I do the same in code documentation. One line to very briefly summarize what that function/module does, <enter><enter>, followed by a more detailed description.
By packaging situation do you mean the user-side of things, i.e. how to install stuff separately of each other? For that I've had good experience using
https://pypi.org/project/pipx to install several cli tools without conflicts. Uninstalling them has also been a breeze.
Depending on the platform, virtualenv defaults to creating a symlink to the Python executable. You can override it with --copies, but then you have a new problem: updating the interpreter in all virtualenvs when a new Python release comes out.
- adapt a time management technique (i.e. pomodoro) to ensure frequent breaks from typing. Listen to it. Your code can wait. Grab some other objects during the breaks (lacrosse ball)
- get light dumbbells, ranging from 2 to 6 kg, and start doing wrist flexor exercises every day. Slow pace, good form, not too heavy weight, stop when it really hurts.
Yes, there are more use cases I didn't knew of at the time. For example, optimizing revenue by calculating the optimal routing strategy for outbound calls. But data analysis wasn't a prority. Nor was scaling storage or computations.
I know this is circumstantial, but on average there were 2 developers. The company needed something to just get the bills out. It also needed to be correct, stable, easily expandable for new datasets (requiring all kinds of conversions), testable from unit to e2e, integrate with other APIs to retrieve metadata, and .. I forgot a few, probably.
About 5 years ago I worked at a small, business oriented telco. The biggest ETL was processing external CDRs, applying call tariffs, and creating bills and reports. A previous developer had been adamant about using a Hadoop cluster to process this, storing all of it in Cassandra NoSQL.
The idea was interesting, but it didn't quite work out. At some point he left the company and we had to do something about the pipeline, as it was crashing most of the time. We did some calculations, and figured that with the right approach, a good old MySQL+PHP solution would do the trick. And it did.
Having switched jobs myself in the meantime, I'm happy knowing the system is still running, and finding people to maintain it is relatively easy.
Upvoting because it's wednesday.