Anyway, I'm very happy to see someone with Michell's talent entering this space. We can use more options with sane defaults and great performance.
1,744 karma · joined March 29, 2015
Anyway, I'm very happy to see someone with Michell's talent entering this space. We can use more options with sane defaults and great performance.
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
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.
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.
Presumably the issue here is that you have customers with >10k records, but can't show them. Why not take their data and anonymize it, then put it under a fake customer?
> "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.
I recently had a five month period where I took a plane ride every single week for work. A “frequent traveler” so to speak.
To me, the big difference between basic economy and regular is the ability to cancel (for a credit) up until the flight takes off. When you travel once in a while, this isn’t worth that much. When you travel every week, it’s huge. For example, when I travel (round trip) 3-5 times a year (which is my normal cadence), I’m not gonna really care if I booked an 8pm flight but last minute decided that I have time to get on a 6pm. An extra two hours not-at-home is no big deal, maybe even a good thing. When you travel every week, the ability to change later minute is huge (and contrary to popular belief, I found that it is often the case that last minute flights are the same price or cheaper, depending on the route, though it can also be wildly more expensive).
In addition to changing my mind about when to leave, don’t get me started on delays. If I saw my flight was delayed two hours (which often means that it’ll end up cancelling or taking off 6 hours late), I’d immediately book an alternative (if I could find one at a decent price) and then cancel one of them right before departure.
Aside from this, seat selection is important, especially if you travel a lot (the lifestyle is hard enough to begin with). You can usually buy seats in basic economy and the whole thing will be cheaper, but assuming you are going to do that, then the difference is gonna be $25-30 which is basically the “right to cancel” fee.
Source: I work at an early stage startup.
Far cheaper these days. More like $2-3 for a consumer to do this. For bulk deals, pricing is often < $2.
How many times have I thought, maybe i should get 2tb just in case, and then end up using 500gb. With framework, I'll buy the 1TB and the cost to upgrade is very low if I ever need to.
Same thing with memory. Maybe i need 16, maybe 32, maybe 64. I tend to buy more than i need out of fear. I just don't have that fear with framework.
Oh, and don't even get me started with repairs. If my screen breaks, i know the time to fix is however long their shipping lead time is, since the repair itself will take me 15 minutes.
In general, i think that value depends on how you see a computer. $1000-2000 is a lot to spend on something you use for fun. It's really not much to spend on something you use every day for work. And it's even less if your company is paying.
$200 is a really nice entry-price point. If I'm being honest, I'm marginally interested in this, but doubt that I'd actually use it too much. But the price point is justifiable for someone who is just interested in it from a learning point of view (if I bought this, used it a few times and learned a bit more about AI as it relates to robotics, it'd have paid itself off easily).
Rooting for you to succeed.
If you make changes, you just upload a new template and you’re all set.
Amazon makes it quite easy to publish books that get printed on demand, and they accept pdf files as inputs.