valicord

rg/fd respect gitignore automatically which solves this problem

I hate ads as much as anyone, but the OP article would be more convincing if it didn't itself include 6MB worth of screenshots.

> It shouldn't matter as long as it addresses your ask

But it doesn't? I'm more than capable of using Google and chatgpt myself. If I was looking for a machine generated answer to my question I would have already found it myself and never made the post in the first place. If I went to the effort of posting the question, it means that either the slop answer is not sufficient for some reason or that I want to hear from actual humans that have subjective experiences that an LLM cannot.

Posting an AI response verbatim basically says "I think you're too stupid to click a couple of buttons, so let me show you how it's done". I think it's very reasonable to get upset at the implication.

> I do find it interesting that people don't mind AI content, as long it's "their AI." The moment someone thinks it's someone else's AI output, the reaction is visceral.

Isn't it obvious? If I'd wanted to see AI response to my question, I'd ask it myself (maybe I already did). If I'm asking humans, I want to see human responses. I eat fast-food sometimes, but if I was served a Big Mac at a sit down restaurant I'd be properly upset.

"You can determine any country as long as that county is USA"

> Those acceptance criteria are guardrails for the change that comes after, and getting those out of your head into English is more important over the long haul than your undocumented short-term solution to the criteria.

I have a lot of context about the system/codebase inside my head. 99.9% of it is not relevant to the specific task I need to do this week. The 0.1% that is relevant to this task is not relevant to other tasks that I or my teammates will need to do next week.

You're suggesting that I write down this particular 0.1% in some markdown file so that LLM can write the code for me, instead of writing the code myself (which would have been faster). Chances are, nobody is going to touch that particular piece of code again for a long time. By the time they do, whatever I have written down is likely out of date, so the long term benefit of writing everything down disappears.

> after the countless little iterations you made since your head-spec wasn't as concrete as you imagined before you started iterating.

That's exactly the point. If I need to iterate on the spec anyway, why would I use an intermediary (LLM) instead of just writing the code myself?

I agree with your first paragraph but not the second one. In many cases it's easier for me to directly write the code that satisfies the unwritten acceptance criteria I have in my head than to write those criteria down in English, have an LLM turn them into code, and then have to carefully review that code to see if I forgot some detail that changes everything.

Only some models

Roborock q revo

I'm sure you're being sincere here but this really reads like that famous HN comment about "who needs Dropbox when ftp exists". The reason vscode is popular is not because it does something impossible to do otherwise, but because it does those things out of the box with a friendly UI.

How much time did it take to write this rather than Google "join zoom in browser"?

It doesn't need to, it's just much more convenient when you can do everything in a single commit.

The point is atomic code changes, not atomic deployments. If I want to rename some common library function, it's just a single search and replace operation in a monorepo. How do you do this with multiple repos?

You can grant access to a few specific sites (in chrome at least), it's just hidden in settings and you need to configure it manually.

If you can sue shark fins, why not a website? https://en.wikipedia.org/wiki/United_States_v._Approximately...

if it's an open source project, why is it using a cask anyway? it should be a formula that builds from source directly

The satellite feed removed from internet in 3, 2, ...

The parent comment was "The author of that site assumes that scrapers will keep track of the access tokens for a week, but most internet-wide scrapers don't do so.". There's no technical reason why they wouldn't reuse those tokens, they don't do that today because they don't care. If anubis gets enough adoption to cause meaningful inconvenience, the scrapers would just start caching the tokens to amortize the cost.

The point of the article is that if the scraper is sufficiently motivated, Anubis is not going to do much anyway, and if the scraper doesn't care, same result can be achieved without annoying your actual users.

The point is that the scrapers can easily bypass this if they cared to do so

That's mainly for visitors. If you're a US resident, you can't just buy medicines abroad, unless of course we are talking about the "they won’t get caught" scenario.

Did they proofread this at all?

> the Department of Housing and Urban Development announced that non-permanent residents ... would no longer be eligible for mortgages insured by the Federal Housing Administration (FHA)

> The reason why the number of FHA loans going to non-permanent residents has dropped in recent months, according to Thomas, is mostly that they are not buying anymore.

What? No, the reason why the number of FHA loans going to non-permanent residents has dropped is that they are not eligible for them. It literally says so at the beginning of the article.

I don't get it. How would switching to bigint break the existing integrations?

That's already how it works unless you happen to be from a couple unlucky countries

Ecobee thermostats do have local control through the homekit api

If you don't want to put the basic amount of effort to follow the repository bug reporting guidelines, why should the developers put any effort into responding?

FYI, the number listed in the visa application is only the lower bound on the actual amount paid to the employee. There's no benefit to entering an amount higher than legally required, so you can't draw conclusions about how much people are really paid from this data.

No, it's always "per unit that you use". Units that you buy and not use are wasted, so that's would be the wrong way to compare.

Dressing up an obvious idea with fancy-sounding math formulas and pages of text is exactly how you get trapped by someone good at selling stuff.

So buy in bulk if it's cheaper then per unit and buy per unit if it's cheaper than in bulk? Truly a brilliant advice. What's next? "Get multiple quotes and pick the best one"?

How would the compiler have caught this bug in rust?

4. Golden handcuffs