970 karma · joined December 23, 2016
Agreed on all fronts that City Hall Plaza is a disaster, though. I thought there were plans to revamp it with the Government Center station green line revamp a few years ago, but not sure if that improved anything.
Going with the Cortex A Coral Dev Board or another SBC with the PCIe or USB standalone Coral TPU seems like a better bet. You'd get a better camera (eg via USB), more processing power and memory, and more full featured software (both Linux and TFLite instead of baremetal or embedded OS and TFLite Micro). Price point would be higher for this option, but you'd certainly make that up in saved time very quickly not having to deal with baremetal programming or an embedded OS.
I've recently been describing what a commercial VPN provides to non-technical friends and family as a type of "global virtual Internet cafe" subscription - the pros and cons of using a physical Internet cafe mostly apply. An Internet cafe isn't inherently (i.e. due to technical benefits of underlying technology) any more or less secure than connecting to your home or work wifi/network, and the Internet cafe knows who you are and what websites you're visiting, but your ISP/employer doesn't (since you're "at" the Internet cafe, not on your home/work network).
Of course, your ISP/employer does know that you're visiting the Internet cafe, and in the case of work (and some ISPs) can stop you from doing so.
If you visit a website from an Internet cafe, the website may still be able to figure out who you are, just like they can when you bounce between different networks normally. And of course, if you login to your account on a website or put your shipping address or something in when buying something, you're self identifying (unless you have throwaway accounts or forwarding addresses or whatever).
And finally, if someone really wants to figure out who you are to a high degree of confidence, they will.
I find this lands pretty well and is close enough to being technically correct without getting into the details that non-technical people would start glazing over if I got into.
Of course, your ISP/employer does know that you're visiting the Internet cafe, and in the case of work (and some ISPs) can stop you from doing so.
If you visit a website from an Internet cafe, the website may still be able to figure out who you are, just like they can when you bounce between different networks normally. And of course, if you login to your account on a website or put your shipping address or something in when buying something, you're self identifying (unless you have throwaway accounts or forwarding addresses or whatever). And finally, if someone really wants to figure out who you are to a high degree of confidence, they will.
I find this lands pretty well and is close enough to being technically correct without getting into the details that non-technical people would start glazing over if I got into.
Could be totally off here, but have a feeling this team is going to get scooped up by one of the big co's. Having deja vu of XNOR.ai (purchased by Apple), when partners got the short end of the stick (see Wyze cam saga: https://www.theverge.com/2019/11/27/20985527/wyze-person-det...)
That’s some creative logic. Being a stay at home parent is a full-time job. If the stay at home parent were being paid, they’d...well...be paid. “Effective” payment isn’t helpful to a full time parent raising a child and losing out on wages they would otherwise get at a job that the economy values with a taxable wage.
Interesting that you had this takeaway, I didn’t get a sense of this at all. My takeaway was that the author presented modern findings (which constitute our present model for how the brain works, speaking nothing to a notion of some absolute correctness) to dispel older hypotheses that are disprovable based on the latest research. As presented, IMO, the author captures well that these modern findings are just a reference point against which to refute the stubborn tropes.
Regarding the rate - LTCG depends on ordinary income level. The 2020 rate for someone earning $150k was 15%, so the $10 million exit in the author’s example would be taxed accordingly. Unless I’m missing something here?
One nitpick, the part about comparing possible startup comp in a unicorn exit and as a senior eng at Facebook over an 8 year period is missing the possible tax benefits of the startup comp. Facebook comp will be taxed as ordinary income as the stock is granted as RSUs (basically 40 - 50% in the US in the $500k/year bracket depending on the state you live in), whereas the majority of a $10 million windfall from being an early employee at a startup that exits after 8 years would likely result in at least half of the tax burden if you did it right and the options were ISOs. With a 4 year standard vesting schedule, the majority of options would have vested far before the startup was a unicorn, and the tax burden at time of option exercise may be very low. Assuming then a long term capital gains rate of 15% at time of sale, the comparison to Facebook comp over the same timeline is about 4x in favor of the startup rather than the 2x the article proposed.
As the author says, though, the startup route is exceedingly risky and very highly likely not to come out ahead.
What's worked for us is to not restrict communication, but to hold our engineers accountable to what they say they'll get done and when. If something slips and it's not for a technical or personal reason (i.e. some risk materializing or needing to take unplanned time off), but rather because someone floated in and asked for something that wasn't scoped in, that comes up in a review and reflects poorly on the engineer and the asking party. On the other hand, if the engineer is able to get all of their scoped work done and also get the unplanned work done, that reflects well on the engineer and potentially the asking party. In our experience, approaching these situations in this way also has the benefit of preserving and encouraging individual autonomy.