Hacker News new | past | comments | ask | show | jobs | submit | mattschmulen's comments login

Yup, really they had the right idea in that it was native components that were hoisted by JavaScript binding... it really lost steam because it became easier to just build native Swift (and later kotlin android). It was a solid play at the problem in it’s time. Note: I worked at Appcelerator in the “gogo” years and it was great, and they/we almost made it happen in a real way.


How else do you identify your mbp going through TSA. Call me laptop roulette paranoid.


Mine is the one with no stickers


What is the likelihood of seeing another macbook with no stickers compared to the one with the exact same stickers as yours arranged in the exact same way? I think that should address the issue with your argument.


Mine is the one with the gunk.


It's the one next to my shoes and my wallet.


I think that's how pretty much everybody does it

Though every MacBook has some small details that can be picked up even if "identical"


I usually put my carry on (a rolling bag) and personal item (backpack) on the bookends of other bins/belongings on the belt, s.t. all the bins are between two large, distinctly-mine items. It also makes pointing out the items which are mine to a TSA agent significantly easier.


I live in Europe, you need to put the laptop into a plastic box, with all the cables, etc. It's easy to identify it. I put also personal belongings


Precheck saves that hassle.


I have had some nice results with swift. It’s still predominately Apple tech (macOS,iOS) but the packages manager is nice and it’s has nice “script” feel for a compiled language.


Great article, I love seeing server and client side worlds colliding. It reminds me of the early days of lib-uv/nodeJS. In addition to the swift NIO specific endeavors I’m excited about the integration work with Swift package manager (spm) and xCode. I think there is real impact on sharing server side and client side models/serializers similar to Android and JavaScript isometric models. It’s not effective for every project, but for many iOS first endeavors itnhas real value in the design & define stages of app creation. Very cool


In my humble experience the impact of this issue is multiplied on mobile; given the mobile context the user expectation is in amplified and the need for clear communication made more relevant. A simple “spinning wheel of death” is often not enough. However, I’m not bought in on the term ”benevolent deception”. Where I’m from we differentiate this by differentiating being honest with being earnest. “The importance of being earnest” (forgive the pun) is that the earnest person has your objectives/priority in mind regarding the outcome for the recipient. An honest persons is an indifferent to the outcome or result. The earnest person is looking out for you.


If I had a dollar for every time an XO, Sales VP, or board investor (I’m looking at you Todd Rulon-Miller) said we were expecting an IPO filing in two years (bless thier optimistic little hearts) and sold for executive bonuses and a common stock price for the parts then I would have 3$. Best exit I ever had was an XO who’s singular prediction statement was “I think we have a chance at building and contributing to this technology and I think that might be valuable to this software enterprise segment, do you want to go find out?”. Buyer beware, contributor beware; it’s just how the game goes. Look for the humble introspective and you increase your odds, there is no guarantee, you only control your investment. That’s a tough break for those that were over exposed you have to cap your liability to your comfort level. bummer for those that caught the bill.


How does an engineer protect themselves against this sort of outcome? Just never work for startups?

I currently find myself in a similar situation, where the books look dire but the executives keep saying that we're so close to profitability. I'm 85% certain that my stocks will be worth nothing, but I stick around because I still see an ounce of promise. Am I just a sucker?


Don't take a pay cut unless you love the work.

In other words, assume the stock will always be worth zero, and then make your decision to work there based on that assumption. Will you be happy doing what they want you to do for the salary they are offering if you know the stock will be worth nothing?

The answer isn't always no. Sometimes you'll get to work with amazing people, or on a really hard problem, or get a lot of responsibility you couldn't get at a big company. All of these intangibles might be worth the pay cut.


I think for early stage companies you should see the startup as a 1) learning opportunity first and chance to work with a great team driven by a passion outside of pure money, and 2) an out-of-the-money call option / favorable lottery ticket. Also, the new tax bill got rid of AMT for incomes under $500,000 for individuals ($1m for couples). It's difficult to go over that amount with ISO's as the FMV of your shares is valued at around 10-30% of preferred. You could exercise your options once every year for example to stay under that limit.

If you've already exercised and paid AMT, try to invest your other savings and if you need to take a loss you can offset it against those capital gains.

While it might not be something you're passionate about, I would also add that reading about startup law, discussing with your peers, and knowing your rights, and even asking (getting in writing) the terms of the investment rounds, is invaluable and certainly something you should do if you want to understand your full package.


Can you elaborate or point to any references on how this works? Does this essentially mean if I have some amount of options I want to exercise, and the combined total of that + my income is <$500k, I don't need to pay taxes on the options at all?


I believe they're mistaken - 500k/1MM are the new exemption phaseout points.


So how does it actually work though? I'm not really familiar with this stuff, so any basic info or good links to learn more would be much appreciated.


Step one: understand your deal. When your hiring manager -- the founder -- breathlessly tells you "FIFTY THOUSAND SHARES" you should respond with these questions:

--What fraction of the company's outstanding shares is that? --How many of those shares are some kind of preferred shares? --What was your premoney valuation in your last financing round, both total and per-share? --How much money did you raise, in return for how many shares?

Or you can ask to see the capitalization table, which if not fraudulent, will answer these questions.

Then you will have some idea of the potential value of the shares you have.

These are reasonable questions for you--for any investor--to ask. They are asking you to invest the one thing they can't pay back: your time.

What if the hiring founder doesn't want to answer these questions for a mere underling such as yourself? In that case, assume a potential share value of zero and make your decisions accordingly.


> What if the hiring founder doesn't want to answer these questions for a mere underling such as yourself? In that case, assume a potential share value of zero and make your decisions accordingly.

That’s your cue to walk: it won’t be the last time they try to scam you and you’ll never be less committed to staying at that company.


You're right of course. My "mild" language was perhaps too mild.


Try to get the real scoop. If the corporation isn't very transparent to employees, it might help to exercise at least one share, to have stockholders rights.

It's one thing to be nearly profitable like Amazon was for many years, where current income was going into investment for the future; if a need for profitability arose, investment could be toned down and margins would appear. It's another thing when the current costs are slightly more than the current revenue, but decreasing spending immediately will also decrease revenue immediately. The later situation could be ok, if there's some realistic medium/longer term cost savings or revenue growth plan that is likely to be finished before the money runs out.

Startups that have revenue but not profits are judged a lot harsher in the market right now than they used to be; certainly they're judged harsher than startups with no revenue. If your stock makes your total compensation good/acceptable only if there's a big exit and the required exit is much bigger than is realistic, you're not well compensated -- unless you're getting something else out of it.


> If the corporation isn't very transparent to employees, it might help to exercise at least one share, to have stockholders rights.

Can you elaborate on the benefits of this? I exercised ~10% of my vested options at my 1 year cliff, but I have not received any additional communications. I looked into requesting specifics from the company because they're "A Delaware Company", but apparently the law says that "curiosity" is not a valid reason.


I would ask a lawyer versed in Delaware case law. I am sure they could give you some reasons. I'd imagine you could make a request for inspection on the grounds of independently (and confidentially) assessing the fair market value of your remaining options to determine if you want to purchase them. I mean that's really why you want to documents right? You want to see actual revenues, contracts etc... If the company balks then you might want to engage a law firm to handle your request (or get a group of shareholders together to do so). Also if the company is not forth coming then that's probably a red flag.


> I'd imagine you could make a request for inspection on the grounds of independently (and confidentially) assessing the fair market value of your remaining options to determine if you want to purchase them.

I think you need to be careful to make the purpose to assess the fair value of your current holdings, as the purpose has to be "a purpose reasonably related to such person’s interest as a stockholder". Assessing the value of your unexercised options isn't in the interest of your current holdings. If they push back on this, "why do you want to know the value, you're not planning to sell are you?, etc", then say you need it for estate planning, which is reasonable enough.


It’s a package deal: cash, lottery tickets, skills, connections.

A good reason to stay would be a lot of cash. Or modest cash but a lot skill-learning and/or connection building to open more doors for you next year. Subpar cash plus lottery tickets is not a good reason to stay.

There are some unique skills you can only pick up at startups, namely: 1) running a startup skill, learned from founders 2) running entire product rather than one small piece (larger companies will not let you run the whole product until you “prove” yourself) 3) understanding fundamentals of business, which will slow you to pick better startups to work for, or to make one.


If the C team knew they were going to IPO, the incentive is to mention it as least as possible to employees that leave dont exercise. I dont blame the C team for responding to basic incentives. Its insane to believe someone will choose to fork over their own money in favor of others that are not even at the negotiating table.

Thats why it should not be in the hands of anyone but the stock owner what he can or cant do with the shares. That way, when they send you a spreadsheet showing you will be a millionare, you go to see how much the shares are actually being sold in the market and worst case scenario, you buy some without being an employee!


When choosing a language, framework or “platform” there are only three things that matter:

(1) Time to market: how fast can you implement a “ship-able” feature, app

(2) Resource cost/availability: can you find delivery resources easily and cost effectively. Sometimes this resource is you, metric appropriately.

(3) Scalability: as you grow and features change, how do the other two things change. Do they change for the better or the worse.

The weighting of these depends on longitivtiy expectations. If your short sighted for immediate reward weigh (1) and (2) higher if your confidence is high on the outcome of what your doing then weigh (2) and (3) higher.

For this discussion Swift wins on almost all fronts. The exception might be legacy maintenance , and even then it might be a knife fight of when and how.


While legacy iOS developers are justifying objective-c over swift. Swift is “eating the world” of iOS and macOS app ( and some server side ) development, avoid it at your own peril. The Xcode issues are undeniable but it does not change the situation. swift lang is superior and it is the overwhelming choice for new apps and new developers.


Completely true for the last two years, however if the last two months are any indicator things are looking up on this front. The swift 4 update was relatively painless compared to 2 and 3.


How is this measured? I'm a big fan of Vapor, just curious


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: