For anyone interested, Eater did a great job profiling them and their factory [1]. Sun Noodle pretty much owns the entire NYC ramen scene (with the notable exception of Ippudo). They also sell their noodles & kits at Whole Foods and Japanese grocery stores.
Just a heads up, the 90 day out clauses are usually put in there by the company lawyers. The only rule the IRS has is that ISO options flip to NSO after 90 days[0].
Take a look at the Pinterest options plan[1], where Pinterest actually gives you 7 years from when you leave to exercise. Your ISO options just flip to NSO after 90 days.
The ISO -> NSO switch can have severe tax consequences for the employee. Even if your company doesn't expire your options in 90 days, consider exercising within 90 days anyway (and talk to a tax lawyer, etc.).
One not-as-obvious reason why companies are reluctant to set long expiration dates on options is because it means former employees take up space in the cap table even if they have no intention of ever exercising that option. The company essentially has to treat those shares as having been purchased, without having received any cash for said purchase. Cap table cruft can make it harder to negotiate subsequent funding rounds.
In this situation it would be great if there were something similar to the 83b letter for non-founder employees. I know too many people who have exercised options when leaving a company (and paid a hefty tax) only to see the value of the resulting equity trickle down to 0.
Yes, but if the 90 day expiration is in the plan, then it is 90 days. It doesn't matter why the lawyers put it in there, though IRS treatment is a reason why it is very common. You aren't going to be able to negotiate changes in the stock option plan with a company you are thinking of joining.
If you are working at a company like Pinterest with a more employee-friendly option plan, then you should value the stock options at a higher value as compared to less employee-friendly plans. I ultra-long expiration periods are awesome, and they are another practical method to deal with the longer period to IPO. These types of options aren't as good as having liquidity for the stock, but with them you can be sure that if you vest the option and the company value goes way up, you'll get the benefit from that.
Isn't this one of Apple's main goals in their Activity app (w/ the Apple Watch)? To get around and move for a couple minutes each hour at least 12 times a day? Lots of other fitness bands have done this as well (Jawbone Up comes to mind).
This is an awful oversimplification, but in my experience, there are two different kinds of applications:
- User-centeric (think: an e-commerce site): your costs are going to grow somewhat linearly with your userbase/traffic. Do a load test to figure out how many concurrent users each dyno supports and then model your costs with that in mind.
- Data-centric (think: an analytics platform): your costs are to going to grow linearly with the amount of data points each customer is going to be using. Figure out how many data points a single worker dyno (running 24x7) can process and then model your costs with that in mind.
You can also have a combination of both.
But basically I second this post, you have to figure out what is going to increase as your product gain momentum. If you will be handling millions of requests because each client is going to do plenty of them, are they going to store data...
Like if you were Netflix, you would have to consider the number of users growing, but also the size of your catalogue. Try to define what direction your business is going as it grows and then you will be able to narrow down the costs more accurately.
I realize that this took a huge amount of time, so asking for an open source version of this might be asking a bit much. But, I would absolutely be willing to pay for a SaaS product, or a licensing fee for the code. It's absolutely beautiful, and as someone who does this in a gross spreadsheet, moving to something like this would be unbelievable.
Considering most people are casual observers 3 comments about paying for this is a positive signal. vpj should just throw up a landing page asking for money and start building. :)
I would also love to pay for this. However I would not want a typical SAAS product. I don't want my data on your servers. Give me something I can install myself really easily. There are products out their which do the SAAS things and ones which I can install locally (if I setup a server, database, configure it all etc.etc.). Give me something really simple and something I can secure myself locally and you have lots of my money. I don't have much, but I will give you lots of it :)
> I realize that this took a huge amount of time, so asking for an open source version of this might be asking a bit much.
What's this to mean? Linux and gcc took much more time from many more developers. Licensing isn't a function of your investment into the project, it's a function of how the project will best benefit the world.
It's been proven these arbitrary restrictions don't actually enhance security. We need to see the TSA move to behavioral analysis for them to actually make a difference.
> It's been proven these arbitrary restrictions don't actually enhance security.
Agreed.
> We need to see the TSA move to behavioral analysis for them to actually make a difference.
They've tried this. In practice, it ends up being a very thin cover for racial profiling[0].
Of course, when the TSA itself admits[1] that there is no evidence of a threat of terrorism against aviation in the US, it's not surprising that more "advanced" techniques of detecting terrorism prove to be ineffective.
Of course there's a flip side of this coin. I think it's a very good bet that this action was not taken in a vacuum. So someone disguised a weapon or a bomb as an electronic device in their hand luggage, and got it on board and was caught.
So who takes responsibility ? Because that's the million dollar question, although in this case, more like 100 million dollar question. If you make the TSA less onerous and the result is a plane plowing into a skyscraper, who pays ?
I think this action is at least partially the result of insurance companies saying "not us".
I am quite naive in these matters but I see two reasons why this won't happen: 1). This will effectively tear down the security theater (again, I assume this is what it is and may be uninformed that there is a real threat). 2). It is difficult to train a large number of personnel to perform behavioral analysis given the traffic the US airports handle.
Israeil has a small population/traveler count and a relatively direct threat. The US has a huge population/traveler count and a vague possibility of threat.
While I haven't personally used seed-fu, it seems to solve a different problem. There are two main problems we're trying to solve here:
- Having the seeds.rb file mirror the records you need from production. You wouldn't want to to register your User model, since you don't want all your production users. You would want to register a model like Product.
- Being able to easily migrate data on our production systems. Being able to easily migrate (and rollback if something goes wrong) is key to having predictable deploys (for us at least).
It's key to migrate seeds on a "clean" database. Any models you register will be exported from the database into the seeds file, so we usually rake db:reset before running rake seed:migrate on development systems. We actually built this gem almost a year into our current system, so our first bootstrap of this loaded all the records from our production database for the models we needed (products, shipping types, etc.), which gave us a clean seeds file to use on development and test systems.
https://github.com/harrystech/kontrast