2) A lot of comments here talking about turbotax. Remember that intuit also has quickbooks. Personally, i think the uses for AI in doing my taxes are limited. I don't want AI making judgement calls. However, for something like quickbooks, I can imagine many uses for AI. For example, categorizing expenses, organizing receipts, noticing odd patterns, etc.

Well I guess you also thing that getting a job promotion is a silly idea? /s

Show HN here: https://news.ycombinator.com/item?id=48151287

(If you are a VP at Amazon, yes, I'll consider acquisition offers. I'm also working on an enterprise version of this with additional features.)

Show HN here: https://news.ycombinator.com/item?id=48151287

- Show HN: https://news.ycombinator.com/item?id=48151287

- github: https://github.com/dtnewman/burn-baby-burn

Are you a startup looking to show investors your hefty AI budget? Are you an engineer trying to top the AI token leaderboard? Wanna show your friends how "AI Native" you are? Look no further, I created this for you.

Comments URL: https://news.ycombinator.com/item?id=48151287

Points: 135

# Comments: 30

Comments URL: https://news.ycombinator.com/item?id=47852313

Points: 6

# Comments: 0

What I found in the following week is a pattern of:

1) People reaching out with feature requests (useful) 2) People submitting minor patches that take up a few lines of code (useful) 3) People submitting larger PRs, that were mostly garbage

#1 above isn't going anywhere. #2 is helpful, especially since these are easy to check over. For #3, MOST of what people submitted wasn't AI slop per se, but just wasn't well thought out, or of poor quality. Or a feature that I just didn't want in the product. In most cases, I'd rather have a #1 and just implement it myself in the way that I want to code organized, rather than someone submitting a PR with poorly written code. What I found is that when I engaged with people in this group, I'd see them post on LinkedIn or X the next day bragging about how they contributed to a cool new open-source project. For me, the maintainer, it was just annoying, and I wasn't putting this project out there to gain the opportunity to mentor junior devs.

In general, I like the SQLite philosophy of we are open source, not open contribution. They are very explicit about this, but it's important for anyone putting out an open source project that you have ZERO obligation to accept any code or feature requests. None.

> "what does error handling look like with real load?"*

I find it hard to believe that anyone is making an investment decision off of this question, but how would you demo this with a real customer anyway? Intentionally introduce a bug so that you can show them how errors are handled? Wouldn't the best course of action here be to just describe the error handling?

The difference is that the execution resonates with people + great marketing

I don't doubt that the leading labs are lighting money on fire. Undoubtedly, it costs crazy amounts of cash to train these models. But hardware development takes time and it's only been a few years at this point. Even TODAY, one can run Kimi K2.5, a 1T param open-source model on two mac studios. It runs at 24 tokens/sec. Yes, it'll cost you $20k for the specs needed, but that's hobbyist and small business territory... we're not talking mainframe computer costs here. And certainly this price will come down? And it's hard to imagine that the hardware won't get faster/better?

Yes... training the models can really only be done with NVIDIA and costs insane amounts of money. But it seems like even if we see just moderate improvement going forward, this is still a monumental shift for coding if you compare where we are at to 2022 (or even 2024).

[1] https://x.com/alexocheema/status/2016487974876164562?s=20

I think that it's bad manners for someone to submit a big PR without prior experience with the project. Someone needs to earn trust over time. They might start out with a few small PRs and gradually build up to the point where you might trust them with a larger change. But even so, a 4k-line PR is very unreasonable.

```

# main.py

if __name__=="__main__": print("This code is not useful")

```

/s

As an example, if you go to the ER and get a strep test, you might be billed $500, and insurance will pay $7 (as ridiculous as this sounds). If you go at this on your own, they'll probably bill you $100 and tell you they are giving you an 80% discount. With lots of phone calls, you can maybe get them down to $50.

This is all obviously crazy. But it makes it such that you really do want insurance if you can afford it. More so, even if you are a billionaire and can afford to self insure, it still makes sense to have health insurance (whereas property or life insurance probably don't make sense for you).

Also, don't forget that insurance premiums are often tax deductible for wealthy people, so the actual amount paid is less.