I reached out to them a couple years ago with this exact question and was told flat-out no. You might be able to sneak around it with an LLC but I think they also require you to have a public website for a plausibly banking-related business, which altogether seemed like too much effort to fake for what I wanted out of it.
So you don't have to be a business to use Plaid, but you do have to be a business to buy Plaid via the Sales channel rather than via the self-serve channel. Admittedly, when folks reach out to Sales and ask to buy Plaid and are told they're not eligible because they're not a business, this nuance is sometimes not communicated very well (or at all). We're working on it. :-)
In fact, we actually just this week launched a new sign-up flow to make it waaaay easier for non-businesses to use Plaid, so try checking it out -- after you go to dashboard.plaid.com and create an account, you should see a "Free trial" button show up on the homepage with a link to use the hobbyist onboarding flow.
Correct, sales encourages you to sign their minimum contract, which basically gets you better support and an account manager. Pay as you go is an option, but Plaid indicated you basically wouldn't have any guaranteed support SLA post-launch if you were on PAYG.
Thank you for the info! Is this a somewhat recent change or has it always been this way? "A couple years ago" in my comment was doing some heavy lifting, I probably reached out around 2017ish.
The last job I got (couple months ago), the main technical interview was a bring-your-own-tools pair programming style interview, AI included, where they gave me a repo and a README detailing some desired features to add and bugs to fix. I didn't write a single line of code myself; I talked through my thought process and asked questions about what to consider from a technical and product perspective, while steering Claude through breaking the tasks into independent plans, reviewing the plans, coaching it to add specific tests, reviewing and iterating the tests, and steering it while it wrote the code. I got an offer the next morning.
Apparently at least one of the other candidates just tried to get Claude to 1-shot the whole thing, which went off the rails, and left him unable to make progress.
Based on my sample size of 1, the expectation right now is absolutely that you can leverage these tools to speed up your workflow, but if you try to offload the entire thing to a single hands-off prompt it leaves them justifiably wondering why they should hire you to do something they can do themselves.
Are you using any tools specifically for controlling this behavior that you can recommend? I want to tear my hair out every time Claude cleanly 1-shots weeks of work to 99% accuracy, one or a couple of tests fail, and it calmly resolves it with a declaration that it was a "pre-existing failure" or "flaky". It can usually resolve it if I then explicitly tell it to stash the changes and compare against the test results from the prior state, but it happens constantly.
I've bought two Apple products in my life, both Macbook Pros, one in 2014 and one in 2021. I have a Pixel phone, zero transactions in the App Store all-time, pay $0 to Apple on any kind of subscription basis. Not disagreeing with the nature of their incentive structure, but if they're intentionally crippling their hardware division somehow to squeeze me for money, they're really bad at it.
They were accused of that by people who didn't understand that batteries degrade over time, and the resulting legal suits were entirely about disclosing the throttling, not the throttling itself. Newer iPhone models still do the exact same thing, they just provide more information about it, and let you toggle it off.
The idea that they were doing this maliciously never made sense anyway, customers who haven't upgraded in a while might be the least lucrative audience to target.
This has never happened. Batterygate was about stopping individual handsets from rebooting by triggering throttling after a brownout. If you are trying to drive up sales you would just let these out of warranty devices reboot. Literally doing nothing would have been easier for Apple.
Depends on your threshold for credentials and desired pay range. If you've got speed, a stream, and a dream, you can coke up as many fish as you want. It's science as long as you write it down.
The huge strike-out they made with the Vision Pro still blows my mind. I'm in the camp of people who would have possibly shifted my entire working setup to that thing if they'd made just a few less dumb choices with it, and it might have been worth it even at the high price. I still occasionally waste my time checking out the latest to see if they've made any headway towards making it useful, because I'm still recovering from the shock that they haven't. The only way I can see the current state making any sense is if they just wanted to squeeze as much field usage data as possible from early adopters of an overpriced prototype, but that seems so far outside of how Apple normally positions its products that it's hard to believe.
> I'm in the camp of people who would have possibly shifted my entire working setup to that thing if they'd made just a few less dumb choices
That describes me too. I even did for a while. But it just made the incomprehensible lack of any software ambition more painful.
The software is the only reason the Vision isn't worth the price. A real Pro OS, paired with an Studio M5-Ultra, or with its own M5-Ultra, would be an amazing work environment.
(The only hardware they would need to upgrade for the latter, i.e. its own Ultra, would be making live-battery swapping convenient. Which they should have already done.)
Browsers generally only allow a fixed number of WebGL contexts per page. So a generic element effect library has the issue that too many elements some will start losing contexts. The workaround is to just make one large screen size canvas and then figure out where the elements are you need to draw an effect for. now you only have one context drawing all the elements. But, you can’t know where to draw until the browser scrolls and renders so you’re always one frame behind.
It's been a while so I might be a little off, but the problem was that the effect would lag behind slightly (one frame?) because I used an observer to match where the element moved to because the overlay element was logged to the viewport. I think I did that to avoid having a canvas that was the size of the entire page. Where a canvas could just be abs positioned it was ok but for reasons I can't remember that didn't work for everything.
reply