Zagreus2142
Joined 1 year ago
Joined 1 year ago
But also, imo, Chrome is way more entrenched that LLM agents. I'm sure people will be happy with chromium being containerized this way.
Indeed shows an active listing in SF for Greyhound for the same amount as Seattle. Greyhound appears to have a single national salary scrolling through different cities. https://www.indeed.com/m/viewjob?jk=ad2e68b167688669
> Since our landing page is isolated from core product code, the risk was minimal.
The real question to ask is why your landing page so complex, it is a very standard landing page with sign-ups, pretty graphics, and links to the main bits of the website and not anything connected to a demo instance of your product or anything truly interactable.
Also, you claim this avoided you having to hire another engineer but you then reference human feedback catching the LLM garbage being generated in the repo. Sounds like the appropriate credit is shared between yourself, the LLM, and especially the developer who shepherded this behind the scenes.
Also the median weekly wage in the US is currently $1196 a week (https://www.bls.gov/news.release/pdf/wkyeng.pdf)
Seattle is currently paying bus drivers $31.39 an hour, 40x = $1256 (https://kingcounty.gov/en/dept/metro/about/careers/drive-for...). And I'm sure the pay is less in less affluent/dense US cities.
It's not exactly apples to apples because the bls figure is nationwide and doesn't include healthcare benefits, and king county metro may have better than average healthcare, but at least ballparking this: No, public bus drivers are not paid "well above" the median wage
Edit: I found this listing on indeed for greyhound bus drivers (the closest comparison I could think of in the private sector) and starting rate is $28-$31 in Seattle (https://www.indeed.com/m/viewjob?jk=2516c81006044ec8).
Well your perfectionism needs to be pointed towards this line. If you get truly large numbers of users this will either slow down token checking directly or your process for removing ancient expired tokens (I'm assuming there is such a process...) much slower and more problematic.
Applying all of this to LLMs has felt similar.
Saying "Near lossless" to mean 90% accurate retrieval of saved vectors is simply a lie. Lossy-ness is binary, not something you can paper over with getting close enough. And 90% is not close. Sure, LLMs are all about gradient descent on noisy data sets so I guess this is acceptable in this field but that terminology usage still bothered me