322 karma · joined December 1, 2024
This article is a huge nothing-burger that seems to hinge on the sentence "some would-be AI sleuths claim that the em dash is seldom seen outside of AI text," which is just plain nonsense.
Everyone does this; it's pretty standard. Using XDG directories (~/.local/bin) is most common nowadays, but hey, you do you.
It does annoy me that cargo has its own bin directory in ~/.cargo, but I'm too lazy to set the env vars to move it.
Coding is the act of writing code. Prompting an AI until it poops out a half-working product is not writing code.
Having the editor/copilot generate some boilerplate or copying shit from Stack Overflow isn't coding either, but once you've done that you go back to coding, so there's a difference there. (Using SO is part of the job, yes, but so is attending meetings and I sure don't feel like I'm "coding" whilst sitting in standup. Any engineer who spends 100% of their time coding is lucky indeed. The point is, just because you're making software doesn't mean you're "coding".)
Is there an advantage to that over combining layers and using cache mounts to avoid those redundant downloads?
A side-by-side comparison of dive's output would be helpful (https://github.com/wagoodman/dive).
Also can you clarify what you mean by "requiring full rebuilds of all previous steps"?
It's been proposed since 2015: https://github.com/microsoft/TypeScript/issues/5228
Currently, you can use `@internal` in jsdoc, which with the `stripInternal` option in tsconfig will cause it to be omitted from the type declarations for a similar effect.
https://www.typescriptlang.org/tsconfig/#stripInternal
Edit: I've also seen libraries abuse `@deprecated` to inform users not to use an internal API:
https://www.typescriptlang.org/play/?#example/jsdoc-deprecat...
Anyone who got the update (I keep mine paused as long as humanly possible, security be damned), did it actually install IIS?
Also, a bit of advice: separate your business logic (file searching) from your UI logic (rendering the GUI). That'll make refactoring (and unit testing) much easier and helps to avoid tangled spaghetti code as you start building larger applications.
Btw, the SQL import doesn't seem to work for an sqlite `.schema` dump; it breaks on the PRIMARY KEY here:
CREATE TABLE IF NOT EXISTS "__EFMigrationsHistory" (
"MigrationId" TEXT NOT NULL CONSTRAINT "PK___EFMigrationsHistory" PRIMARY KEY,
"ProductVersion" TEXT NOT NULL
);
(This is the standard migrations table that Entity Framework creates.)W/r/t monetization, you should know there's a really powerful flowchart tool called draw.io that's already free. It's not tailored specifically towards databases the way yours is, but it can make similar graphs, so if you go too hard on monetizing you might cause people to just use that instead. Maybe there are some more B2B-oriented extensions or db integrations, or maybe a team collaboration feature you could add without compromising the core tool.
If I download a sketchy binary, I'll run it through VirusTotal, but there's no reason to have any of that junk running on my PC all the time.
Please, I'm begging you, go read some papers and watch some videos about machine learning and how LLMs actually work. It is not "thinking."
I fully realize neural networks can approximate human thought -- but we are not there yet, and when we do get there, it will be something that is not an LLM, because an LLM is not capable of that -- it's not designed to be.
Too many people these days are forgetting this key point and putting a dangerous amount of faith in ChatGPT etc. as a result. I've seen DOCTORS using ChatGPT for diagnosis. Ignorance is scary.
Any comparison to the human brain is missing the point that an LLM only simulates one small part, and that's notably not the frontal lobe. That's required for intelligence, reasoning, self-awareness, etc.
So, no, it's not a question of philosophy. For an AI to enter that realm, it would need to be more than just an LLM with some bells and whistles; an LLM plus something else, perhaps, something fundamentally different which does not yet currently exist.
Going to need to back up this statement somehow, because the only time I've seen TLS pose a barrier to anyone is YouTubers showcasing retro hardware and trying to access the modern Internet on an ancient version of IE or Netscape Navigator.
Edit: Ah, nevermind. They did mention older hardware but I was thinking that, if you're going to support browsers so old they don't even support TLS, you may as well support Gopher too. Then I looked at the rest of their site and saw that they do, in fact, support Gopher: gopher://box.matto.nl
That's kind of up to you as the developer though. I generally avoid writing functions that can panic -- I'd even argue any non-test code that panics is simply poorly written, because you can't "catch" a panic like you can in a high-level language. Better to return an error result and let the calling code decide how to handle it. Which often means showing an error to the user, but that's better than an unexpected crash.
Edit: To be clear, this is specifically a React hooks problem, not the old React with classes.
This. I've worked at companies where the infra/devops teams were openly hostile to the dev teams. It's incredible that companies like that function, and that management doesn't seem to care, when teams that are supposed to be working together are pointing guns at each other instead.
You might want to open it up (if you can) and make sure the motherboard is dry to prevent corrosion.