Having worked at multiple IoT companies with many millions of connections. This is the way.
People tend to overcomplicate things with K8S. I have never once seen a massively distributed IoT system run without a TON of headache and outages with k8s. Sure, it can be done, but it requires spending 4-8x the amount of of development time and has many more outages due to random things.
It's not just the network, its also the amount of config you have to do to get a deterministic system. For IoT, you dont need as much bursting (for most workloads). Its a bunch of devices that are connected 24/7 with fairly deterministic workloads, that are usually using some type of TCP connection that is not HTTP, and trying to shove it into an HTTP paradigm costs more money and more complexity and is not reliable.
If you are open to sharing, what is your business?
Otherwise, "it depends"... If you get a job, you can also be laid off.
But if you are able to get a job, while also keeping your business going, this seems to be the best way to financially insulate yourself - as long as you don't let your business actually stagnate too badly, which will only make the economic environment likely impact it more.
Yup, same here. If you have any moderately large data set and do manage to get it loaded , then it will break with only a light graph traversal of 3 layers deep. Played with this for a couple weeks but eventually realized this is not for a large data set.
Yes agreed. Oatly is horrible for you. It's one of the worst Oat milks they sell in my store. (when comparing by nutrition facts).
It is so bizarre this alternative milk that goes around. I am totally onboard with finding an alternative to save cows from inhumane practice, however, very little of the alternative milk that is out there is anywhere near as healthy as normal milk.
Meanwhile anyone can produce any type of alternative milk and people think they are buying health food.
The one year cliff is not that problematic to me since I would expect I am getting paid market, and the options are like a hiring bonus (which you often must return if you quit within a year). What am I missing? Is people really worried that a startup whose stock has risen will fire a productive employee?
That said, I have seen 5 year vesting (which seemed like a red flag to me), and have heard of Amazon's schedule where you mainly vest in later years. These were bigger red flags for me than a 1 year cliff.
Depends on the company. I joined Twitter in 2016. The stock, which was circa 1/3rd of my total comp, had a one year cliff. 7 months in, one executive got the upper hand in a power struggle, pushing out my boss and laying off the people he hired, me included. I don't think they did it because of the stock. But I'm sure it didn't hurt. I'm still mad about it.
Disclaimer: Ex-Amazonian, so discount as you see fit based on whatever brainwashing you might assume I’ve been subjected to ;)
The rear weighted AMZN approach made sense to me in terms of both optimising retention and some proxy for reward to contribution. I say this also as someone who left after 2 years and as a result left most of their stock unvested. It definitely made the choice to leave much harder so I’d expect it to skew more heavily toward retention benefits than a typical schedule. A typical schedule has a linear growth of what you’ve vested. I’d expect the value of contribution of a person to grow over time though. More context, more experience, more everything. Hopefully that means the you 3 years from now is making a more significant contribution than the you they hired. Typical schedules hope that the increase in valuation accounts for that compounding return. AMZN have shifted it to the vesting schedule.
That said they always talk about “total compensation”. So for the stock you’re not getting in the first two years you typically get as cash via a “hiring bonus” anyway. You could always just use that cash to go buy the equivalent amount in stock, no vesting required.
I was exposed to this while talking to an Amazon recruiter recently, while I also hear stories about how they seem to work people to a breaking point.
The median tenure at AMZN is also 1.5yrs, per linkedin. Their strategy seems to be to work their people extremely hard to earn their RSUs and pay them like plebs with hard caps on earning potential (base comp).
As the other reply said, vesting was 5% first year, 15% second year, then 20% per six months.
As for why: a rebalancing of priorities re work/life/travel balance and a better sense of connectedness to my actual work and the success of the company. Not gonna lie though, I look back at what I left on the table and the AMZN share price over the past 2 years and I still wonder if it was the right choice.
I feel like amazon-style vesting helps remove some perverse incentives.
It makes "stay 53 weeks and cash out" less appealing, it makes "stay 6 more months to hit the next cliff" less appealing, and it rewards long-haulers (who are underpaid almost everywhere else in tech).
Yes, that was my hope also. As it becomes more common to not have a cliff.
It was just strange that the recruiter couldnt discuss this further or at least give an offer with a nice cash compensation that would be paid out monthly (sort of like how Amazon does it) to compensate for cliff.
Really? I'm surprised. My employer just removed cliffs for new offers, it does seem to becoming more popular. But my assumption is the cliff is something I couldn't easily negotiate as an individual.
It’s happened multiple times for me, all with extremely well known VC backed companies. Once at later stage, but applying for a very senior role, and another at an early stage, where there was a good fit.
It can be a tough sell, and recruiters are trained to just say no, but persistence pays off. Same thing applies to getting jobs in general. If you aren’t persistent in your application process and aggressive in your negotiation process, you simply won’t have the best outcomes. It just becomes easy to turn you down.
Telegram is one potential answer. I find it to be the fastest messaging platform , and super reliable. Not to mention their desktop apps are not bloated, and message history, drafts, etc sync really well. (note - there is also a secret mode that works like signal, that also doesn't sync message content, which is parity with signal)
Makes sense that some people will not be a fan of this.
Personally however this would be awesome. It is extremely rare I don’t have my phone. already any passport control area is digitally scanning my passport so there is not really more privacy concerns. In addition I imagine a lot of us use the plane ticket features of iphone already, so not having to also separately get my ID out would be great.
From what I've heard about TSA I'd already hesitate bringing my main phone to the US at all, let alone one that's connected with my ID. And what if the phone dies during a trip? Now you've got the 2FA problem but with borders instead of just a Gmail login. Fantastic.
I don't think saving a few grams of paper is worth all that.
Hi - very cool idea! Will probably try it out. Apologize if this is on the site (could not find it) but do you plan to offer any features to "meet" local runners in person? I am always trying new run clubs, and some have stuck and some have not, but I would absolutely LOVE a way to meet local runners that run similar terrain/fitness levels as me. Thanks!
Thank you for the kind words. As of right now, we don't have an option to meet-up through the app, but we do have many users that are organizing their own meet-up groups via our Facebook Run Club.
Most major automotive and ev companies use tools such as environmental chambers to do phases of R&D. (quite possibly all do but obvs can’t confirm, but do have first hand knowledge of several major companies adopting this) Even companies much smaller than Tesla.
Would be shocked if Tesla did not have this capability.
So who knows if this is part of their testing and validation, but it is not true that you can’t test for different environments than where the core design takes place. It is extremely common to do this in rapid fashion without having to transport things to an alternate climate.
Ya same here. The name issues, the killing of the ability to auto mail paper checks (bills), and seemingly over time extremely strict policies on everything from deposits, to addresses, Simple has already been going down hill for awhile.
Personally I have gone out of my way to submit polite and concise feedback, as I really wanted them to win. I used to be so happy here as a customer but inch by inch it had just become overwhelmingly unpleasant.
So over the last year I have slowly moved most of my banking to a competitor, and which as a whole is bigger and does have as smooth of a UX, but has been flawless with actual banking features. The support has made me feel like they actually want my business rather than being a nuisance to them.
It was good while it was good simple, I imagine running a bank is not easy, best of luck to everyone that was a part of it in their next venture.
People tend to overcomplicate things with K8S. I have never once seen a massively distributed IoT system run without a TON of headache and outages with k8s. Sure, it can be done, but it requires spending 4-8x the amount of of development time and has many more outages due to random things.
It's not just the network, its also the amount of config you have to do to get a deterministic system. For IoT, you dont need as much bursting (for most workloads). Its a bunch of devices that are connected 24/7 with fairly deterministic workloads, that are usually using some type of TCP connection that is not HTTP, and trying to shove it into an HTTP paradigm costs more money and more complexity and is not reliable.