Readit NewsSome ideas: - I would focus a lot of effort on making it incredibly easy and intuitive to list things. This is one of the primary barriers to me when using these types of apps. - maybe future idea would be to list things from Home Depot or other stores to expand the number of rentals that are available.
Strong type systems can give provably correct code. For trusted code (e.g. not third party code), sandboxing is a post-exploit mitigation. And such a post-exploit mitigation cannot necessarily guard against any class of bugs that (at least in some aspect) provably correct code can.
Yes, of course privilege separation as much as possible is still extremely valuable, but to say that sandboxing is a "better" solution, implying that one should not pursue provable correct code in favor of post-exploit mitigation, is a harsh liability. It's the same as the "oh, we don't need to use a type safe language, we have unit tests"-crowd, only worse.
Polygraphs are not detecting lies, they're used to assess your sensitivities; there are really talented interrogators in counterintelligence, whose full-time job is to fuck with you in subtle ways. To poly a person at will is very much a power move, and some guys fucking love it. But that's a different story all together. Most of the time it's a formality like everything else. In reality, people don't have remotely enough bandwidth to pursue stuff like that unless there's a genuine investigation. But office politics people will office-politique.
Unpopular opinion: private companies should poly people more often in hiring, it could prove more useful than other arbitrary kind of culture fit interviews. Food for thought.