WCSTombs · HackerTrans

7 gün öncediscuss

To make both addition and multiplication O(n), you can store numbers as their residues modulo a bunch of different primes and appeal to the Chinese Remainder Theorem. However, then size comparison becomes difficult.

WCSTombs

8 gün öncediscuss

I don't see it as a brag. I think they're saying that the specialness of the notebook starts becoming an obligation and a burden, and then the notebook loses its original purpose, because "messy" notes and "neat" notes are for different things.

WCSTombs

8 gün öncediscuss

I think you're completely missing the point. The "messy" notebook isn't supposed to have any aesthetic value or qualities, it's just a tool for the user to record stuff in the moment. It also has nothing to do having a messy phase in life. It literally is just there for you to write stuff down whenever you need or want to.

WCSTombs

8 gün öncediscuss

There's nothing wrong with having a tidy notebook, but many of us also need messy notebooks.

WCSTombs

8 gün öncediscuss

Or simply:

"While I may use AI for work, my website and all the content on it is entirely written by hand."

I don't think the original syntax is incorrect exactly, but too many commas in a sentence can make it harder to parse, which is why style guides often warn about it and advise thinking of certain commas as "optional."

WCSTombs

9 gün öncediscuss

If you hire someone to create something for you (video, images, audio, text, etc.), and you then claim you made it yourself without crediting them, I think almost everyone would agree that it's plagiarism and deeply unethical. It doesn't matter if you also had some creative input, since the other party was still an author of the work. If the "someone" was actually a generative AI model, I don't think that changes anything. You still relied on a third party to have creative input, and passing it off as your own work is tantamount to plagiarism. So in summary, yes, IMO AI usage must be disclosed in creative works.

WCSTombs

10 gün öncediscuss

But the thing is, in this analogy, we are the chef, surgeon, or builder. We're the ones other people look for when they can't do the thing by themselves (in this case, writing software).

Neither my analogy or yours is exact, but it's really worth thinking about.

WCSTombs

10 gün öncediscuss

The problem with this analogy is an LLM isn't very much like a "tool" at all.

- In cases of practical relevance, you pay a recurring fee to keep using it - not very tool-like.

- Rather than doing a predictable action in response to user inputs, you give it imprecise instructions and it does something unpredictable but vaguely correct in response, which then must be thoroughly inspected.

- In cases of practical relevance, its actual operation (not just design) is entirely handled by a third party, not by the user.

These things describe a subcontractor, not a tool. We don't insist that a chef at a restaurant use this tool or that tool, but if the restaurant was actually just outsourcing all its cooking to some other company...yeah, that would absolutely factor into my decision to go there or not.

WCSTombs

10 gün öncediscuss

> I believe that writing something yourself helps you learn it better, but at the same time, if you did all the thinking and now just prompting for a fancy auto-complete, we could argue that the hardest part (the design) was already done, and you skip the writing for the sake of writing. On the other hand, I am afraid that if I will stop writing code in environments where I can still do it, I will lose the ability to think about code and understand code.

Merely completing the "design" is by far not "doing all the thinking," and this is really the core of the problem. When people code with LLMs, the LLMs are making nontrivial decisions and thus are replacing part of the programmer's intelligence. That's why calling LLMs "fancy autocomplete" is so misleading, because autocompletion isn't supposed to make decisions, just to facilitate typing out the code you already have in your head.

So yeah, I agree with the last sentence about losing the ability to understand code, and that's a sufficient reason to avoid AI assistance whenever possible. Since I prioritize education and learning above almost everything else, it's not a close call. Where the line gets blurry for me is when people say "I would never have learned the tech stack needed to make this tool myself, but I vibe-coded it and now it's mine." It's really difficult for me to argue with that, to tell someone simply to live without something that's potentially improving their day-to-day life. To be clear, there are many good reasons not to do that thing, but it's also not my place to judge people for doing it, since I don't live my own life perfectly either.

WCSTombs

14 gün öncediscuss

The C++20 version is still clearly inferior to the Python and Lua examples because you still have to manually increment the counter in the loop body. IMO the sibling comment by HarHarVeryFunny has a much better C++ equivalent for this idiom, even if it's slightly more verbose.

WCSTombs

18 gün öncediscuss

> The goal is to provide a public manifest and build log with every release. Using an open-source toolkit, a user should be able to independently compile the source code and generate a hash that matches the binary on their physical media bit-for-bit.

But the vast majority of games are never published as source code?

WCSTombs

23 gün öncediscuss

As far as I know, EFF has always championed privacy.

WCSTombs

26 gün öncediscuss

In general old good stuff is easier to find than new good stuff, since over time the bad stuff becomes more irrelevant, but I feel there's also some truth to the over-optimization as you put it.

However, while I mostly agree with the sentiment, in my opinion there is some new good stuff (books, music, movies, etc.) still being created, even if it's harder to find in the sea of mediocrity.

WCSTombs

28 gün öncediscuss

[dead]

WCSTombs

28 gün öncediscuss

I think Cider9986's comment [1] on the OP covers it pretty well.

[1]: https://news.ycombinator.com/item?id=48700061

WCSTombs

28 gün öncediscuss

A small camera can easily be covered up. You can't cover something that's embedded into the screen itself.

WCSTombs

28 gün öncediscuss

I don't know how a "complete" guide can completely fail to mention NVIDIA. It doesn't seem straightforward to support older NVIDIA cards (on any OS, to be fair, not just on Linux). That's currently one of the issues with my 2013 Dell laptop that has a Quadro K1100M.

WCSTombs

geçen aydiscuss

The question is slightly vague (since I could be going there not to wash my car), but I'm pretty sure in the intended interpretation, the actual distance is irrelevant. :)

WCSTombs

geçen aydiscuss

Every time I've requested changes to a pull request because the reviewee didn't know the difference between .gitignore and .config/git/ignore, the reviewee appreciated learning about the feature. The person you're replying to also clearly said their reviewees are pleasantly surprised, so it hardly seems like a waste of time. Also consider that it takes almost no effort on our part to point out this feature, no effort for them to learn it because we tell them directly, and it happens at most once per new contributor or hire.

WCSTombs

geçen aydiscuss

I like to use environment modules [1] (or lmod [2]) for that purpose. You can make each manually built software package available or not on a per-shell-session basis, just by running

    module load myapp

    module unload myapp

in the shell where you want it (or don't). The small downside is that it only works with software that actually uses the standard environment variables like PATH, CPATH, etc. for their intended purposes rather than hardcoding filesystem paths, but in my experience it's rare to find something that doesn't. Also, you have to write a modulefile for each package, but that's not a big deal.

[1]: https://modules.readthedocs.io/en/latest/ [2]: https://lmod.readthedocs.io/en/latest/

comments