Readit NewsI have not worked for a FAANG, so maybe things are different there, but I don't suspect so. People are people no matter where you put them.
Increasing compensation is not the solution. It can be a factor in a larger solution, but just increasing compensation increases employee entitlement which makes this problem worse, not better.
The best solution I have seen is risk/reward. Put people in charge of their assigned effort with real adult danger of liabilities. Likewise, award them for their successes. This is called ownership, and it works because it modifies people's behavior. The rewards and liabilities do not have to be tied to compensation. Actually, associating these rewards/liabilities to social credibility within the team/organization appears more effective because it reinforces the targeted behaviors.
I have seen this missing in all of my software career until my current employment. Conversely people in the military are pushed into this liability/reward scenario from the very beginning and its very effective. It has always been striking to see the difference in my dual career progression.
What is the purpose of such loop? Bots can simply switch to another residential proxy when the captcha success rate gets low. For normal humans, it is literally "computer says no".
Local, in my experience, can’t even pull data from an image without hallucinating (Qwen 2.5 VI in that example). Hopefully local/small models keep getting better and devices get better at running bigger ones
It feels like we do it because we can more than because it makes sense- which I am all for! I just wonder if i’m missing some kind of major use case all around me that justifies chaining together a bunch of mac studios or buying a really great graphics card. Tools like exo are cool and the idea of distributed compute is neat but what edge cases truly need it so badly that it’s worth all the effort?
People complain about billboards next to a countryside highway because it is entirely irrelevant to driving through the countryside. Actual complaints may be about how the billboards block a scenic view but that also seems like another way of complaining about the irrelevance. Similarly, if I am watching a Youtube video, I am never thinking that a disruptive message from a commercial business is relevant to my current activities (uh, passivities?). No advertisement is relevant, not even in-video direct sponsorships, hence SponsorBlock.
If I go to Costco and see an advertisement for tires... well, I’m at Costco, where I buy stuff. Things are sold at Costco and people go there to have things sold to them. I might need tires and realize I can get that taken care of while I’m at Costco. Nearly every advertisement I see at Costco is relevant because it’s selling something I can buy in the same building, indeed usually something juxtaposed close to the advertisement.
I don’t complain about advertisements at Costco because that would be insane. I complain about the advertisements on Youtube because they’re irrelevant and weird but somehow normalized.
More broadly, I have concerns about introducing a middleware layer over AWS infrastructure. A misinterpreted command or bug could lead to serious consequences. The risk feels different from something like k9s, since AWS resources frequently include stateful databases, production workloads, and infrastructure that's far more difficult to restore.
I appreciate the effort that went into this project and can see the appeal of a better CLI experience. But personally, I'd be hesitant to use this even for read-only operations. The direct AWS cli/console at least eliminates a potential failure point.
Curious if others have thoughts on the risk/benefit tradeoff here.