nemothekid
Joined 14 years ago
Joined 14 years ago
>A self-hosted runner for the heavy builds. This was by far the biggest win, 90 minutes down to 40. It also means I now maintain a build server.
WarpBuild (https://www.warpbuild.com/)[1] solved this for me.
1. You can cache into your own s3 bucket, so you manage eviction policy
2. They manage the infrastructure, or you can link in your AWS account. I have builds that run on spot instances that are requested when a build starts.
Then for the caching issue, I just have a scheduled job that reruns a build at midnight on the master branch.
[1] Not affiliated, found them through Google several months ago
Frameworks in the past didn't always have custom designed web pages, but at least one could understand if the author spent time actually building documentation.
If Claude is writing all the documentation, that has freed up "resource constraints" that you can use to actually make sure your site is legible. If you can't pass that bar, I don't know why anyone should seriously consider your framework - just like if someone had created a framework without documentation in the pre-ai days.
* Unnecessary badges
* text-uppercase section headers
* Randomly italicized words
The number one gain I see with passkeys is that they are phishing resistant. The biggest issue I've had with TOTP keys is they aren't phishing resistant.
Forcing people to use passkeys gives the authentication layer a stronger means to ensure that people are logging into the correct domain. A password manager accomplishes this, but it's very difficult to enforce. (I've heard a number of variants of "John Smith sent me an important document and when I went to open it, the password manager didn't work so I just copied password")
This + Function URL + Cloudfront, and you end up with an API entirely hosted in lambda. I have a backend that does is hosted like this that does pretty complex work (image/video uploads, image conversions, on top of the standard auth, database connections, etc). It even renders a frontend with HTMX/Alpine.
Even with all the bot traffic I receive, at almost 15 million requests per month the cost is under $10/mo (median latency is roughly 90ms). Cold starts are a non-issue with the Rust runtime.
That's interesting. Maybe to decrease latency the LLM could "cache" it's build of it's database and reuse in between instances. It could host this artifact on a "hub" of git trees and then any new use cases that come up, can be added to this git tree. Then it can possibly be reused in different use cases.
There are plenty of companies (successful ones) that I’d argue don’t have PMF, but have plenty of customers (ex Palantir)
This is akin to telling parents that if they want to their children to clean their rooms, you should make it easy and convenient to do. Obviously this is non-sensical: if you make a mess it might be hard and inconvenient work. Thats why kids don't do it!
I find some tech criticisms to be simply inane; the tech companies are not going to absorb the costs of educating users or fixing unworkable strategies. Not because Bezos needs to buy another yacht, but because the companies that try to do that all die before they get big. There is a giant graveyard of startups who have tried to be the "responsible and patient parent", and they have all died. Users don't want to put up with it, and if given the option will run to the company that just handles everything for them with a subscription fee or reselling their data.