SEEKING WORK (New York City + remote) iOS developer (Objective-C and Swift) for the past 7 years, with full-stack and startup experience (mostly Ruby on Rails) Recent projects: * built all of the NexTravel (YC 15) iOS…
To me, something like your syntax makes sense when there isn't a clear hierarchy among selectorPart1, selectorPart2, selectorPart3, etc. However, in every case where a method can be thought of as having a single primary…
Looks like the pieces are reversible, so the two L's and two S's are actually L, J, S, and Z.
Of course, it's only a failing strategy if adopting that strategy causes everyone to adopt the same strategy, which is very unlikely for most people.
That's the way it should be. Otherwise, you'd be incentivized to leave (dishonestly) positive reviews.
Ideally, I think the complete list of votes (with receipt confirmation numbers, but no names, obviously) would be available for inspection.
If the receipts are anonymous, they can't prove how you voted, only that you were able to obtain a receipt. So what if we increase the supply of receipts enough to destroy the value of an individual receipt? For…
What you're buying isn't a vote, but a receipt. What if we could increase the supply of valid receipts enough to make them effectively worthless? For example, voting machines could drop duplicate receipts into a bucket…
I find that while a neighborhood filter gets the job done, its usability isn't great, for a number of reasons: * You have to roughly know the boundaries of all the neighborhoods for the list of names to be useful * A…
Or just show the subtitles after a short delay. Or show a word-by-word translation in realtime. Or both.
Using UDIDs for authentication isn't a good idea for a serious app. Even if it were unspoofable, devices aren't users. Users have iPhones and iPod Touches and iPads; they upgrade; they sell devices to other users.
SEEKING WORK (New York City + remote) iOS developer (Objective-C and Swift) for the past 7 years, with full-stack and startup experience (mostly Ruby on Rails) Recent projects: * built all of the NexTravel (YC 15) iOS…
To me, something like your syntax makes sense when there isn't a clear hierarchy among selectorPart1, selectorPart2, selectorPart3, etc. However, in every case where a method can be thought of as having a single primary…
Looks like the pieces are reversible, so the two L's and two S's are actually L, J, S, and Z.
Of course, it's only a failing strategy if adopting that strategy causes everyone to adopt the same strategy, which is very unlikely for most people.
That's the way it should be. Otherwise, you'd be incentivized to leave (dishonestly) positive reviews.
Ideally, I think the complete list of votes (with receipt confirmation numbers, but no names, obviously) would be available for inspection.
If the receipts are anonymous, they can't prove how you voted, only that you were able to obtain a receipt. So what if we increase the supply of receipts enough to destroy the value of an individual receipt? For…
What you're buying isn't a vote, but a receipt. What if we could increase the supply of valid receipts enough to make them effectively worthless? For example, voting machines could drop duplicate receipts into a bucket…
I find that while a neighborhood filter gets the job done, its usability isn't great, for a number of reasons: * You have to roughly know the boundaries of all the neighborhoods for the list of names to be useful * A…
Or just show the subtitles after a short delay. Or show a word-by-word translation in realtime. Or both.
Using UDIDs for authentication isn't a good idea for a serious app. Even if it were unspoofable, devices aren't users. Users have iPhones and iPod Touches and iPads; they upgrade; they sell devices to other users.