46 karma · joined July 31, 2015
The main problem I see w/ Eth login is that it relies on your credentials being on the machine, and makes propagating those to other machines harder for non-tech folks. Whereas the whole user/pass solution is much easier to follow for the common person.
I feel like there's a need for something between roll-your-own and what vercel is offering.
I did a similar project that I pitched to a few VCs, got negative feedback, then saw Vercel (was Zeit at the time) launch that feature. So I archived the project & OS'd it. Guess I should have pressed on
now the same thing is happening with netflix. i'm not sure if it's that the selection has greatly diminished, or if it's the algos (hbo max suggestions are pretty good imo)
i think the smartest thing these services do is allow you to share accounts. i would have canceled a while back but my family is using it too
Apple took off with the .com boom and became a staple of every startup. But since the iPhone they've shifted to being a consumer focused company, and I don't see any reason why they would dedicate too much resources to improving their products for developers/designers.
It's pretty sad because they are still the best option. But people are not happy with them, and it's been getting worse over time. I really think Microsoft has an opportunity to cater to power users and release a really beautiful OS. But not Windows - would have to be something new
Letting apps link out to websites for paywalls circumvents all of this. If I was in Apple's position I'd limit that as well.
A few years later the data was much more restricted, much harder to get, and much clearer to the user what was going on.
It's easy to point to Fb and say they are evil, but it really seems to me like it's the 3rd parties that are causing most of the issues, and Fb has been pretty decent at locking it down in the last number of years. Keeping in mind that they were the first who had social data in such large amounts where there was no prior example.
Glad to see this kind of workflow gaining momentum.
I had joined and was learning the ropes of their dev process. There was still some paperwork that needed to be signed. Someone brought me the contract to sign, and I read it through, and it had a non-compete clause that said that I could not work for rival company, or "any other software engineering company" in "connecticut, new england, the eastern United States, or anywhere else in the United States" for "a minimum of 2 years." No joke.
I asked them what that was all about, and they said it was a company policy. I did some research, learned all about non-competes, and told them that the clause was so broad that it would never be upheld, but they said everyone just signs it. I told them no, grabbed my stuff and drove home. Was probably one of the best decisions I made, since the path I went down led me to a company that was acquired by Fb, etc etc
Also led an engineering team at a startup that is seeing some good growth, but left it at the end of the year after some internal drama.
I have struggled with these roles and names, similar to Bryan Helmig, the author of this post. I have consulted with some former bosses, that now lead engineering teams at some of the larger companies here in the bay area, and have come to the conclusion that most CTOs are really VPEs, just using the wrong title, but in the end, the title does not really matter. Since it is extremely flexible in definition.