807 karma · joined June 14, 2011
Founder Screenplay https://screenplay.co
San Francisco.
Past:
Founder Apex - private groups https://joinapex.com [closed]
Founder sha.capital - painful hedge fund learnings [closed]
Eng @Shyp, @insightpool, @backplane.io, @keep.network
math + biochem dropout
Atlanta, GA
[ my public key: https://keybase.io/raj; my proof: https://keybase.io/raj/sigs/CRoYVodi1zrXBnBgq6VElfWz2nPI9v-PmgaDXRitQss ]
Should a founder mentality be expected amongst early employees at a certain equity level? Why wouldn't someone want to hire someone who had that mindset, and then appropriately compensate someone for that?
-----------------------------------------------------
"Cost of Living" adjustments are a red herring, what they really are is really "competition density". There are plenty of tech companies paying great salaries in the bay because they have to, otherwise they would just go work for someone else. On the other hand, if you lived in Oklahoma you aren't going to say no to $LOCAL_OFFER+10k just because bay area salaries are $LOCAL_OFFER+90k.
As long as this disparity exists, I forsee bay area salaries and CoL still being high. Until companies move headquarters out of the bay, the trend will continue.
-----------------------------------------------------
Similarly, in this thread, Consultant32452 states [2] that the real argument is between those who can demand a high salary regardless of geography, and those who can only demand a high salary _because_ of geography.
The mistake is many people in the latter group think they are in the former.
[1] https://news.ycombinator.com/item?id=23162855 by hn user nemothekid [2] https://news.ycombinator.com/item?id=23265158 by hn user Consultant32452
The mistake is many people in the latter group think they are in the former.
[1] https://signal.org/blog/private-contact-discovery/ [2] https://signal.org/blog/contact-discovery/
Similarly, I wonder if our increasingly low-trust, hyperconnected society will cause us to adapt (evolutionarily) in new and interesting ways. Obviously, all of this happens way faster than we evolve, and we'll need better tooling or cultural norms to deal with this stuff.
Agree about typed parameters + implied returns, but you can get some of that back using guards + dialixer/dialyzer.
If the purpose of the decision was to get people to move to wireless headphones, then specifically for myself and my network of folks, this seems to have worked.
Initially I had the Oppo Wired headphones. Soon after removing-3.5mm-gate (and dealing with the adapter), I'm exclusively on wireless: the Airpods and the latest Sony over ear headphones.
Honestly, at the cost of sound quality (which used to be important to me), but gaining noise-cancelling and not having to wrangle with wires, it's such a convenience. Apple was right, and I imagine the trend will largely be towards wireless. That being said, experience still has a ways to go (connect, battery), and die-hard audiophiles will never be satiated.
Concretely, its it the case, for an application where Elixir/Erlang/Beam are a great choice, but also, another language would be fine, that the equivalent Elixir application results in less downtime/pages than the alternative. Anything from the perfect app to something with a ton of races/leaks.
Is this a fair question (maybe I'm presuming too much of BEAM/supervisor pattern, I zero experience with it)?
To support that...
Grin contains a phenomenal amount of cryptography: https://github.com/mimblewimble/grin
Bulletproofs implementation in rust (small proof sizes): https://github.com/dalek-cryptography/bulletproofs
...with tons of really well done cryptography by that group (dalek): https://github.com/dalek-cryptography
Pairing based crypto library used in the second largest distribution of Ethereum (and maybe zcash?): https://github.com/paritytech/bn
These libraries have prompted me to start learning rust (albeit slowly as I'm using Go and C at work).
I wonder if this is a marketing stunt, or an effort to increase the visibility and legitimacy of AI generated art.
Oh wait...
https://www.washingtonpost.com/news/business/wp/2018/09/08/t...
Thanks for writing it - folks, take note.
Good news: your centralized pie where you’ve put in tons of time, and built up a huge amount of credibility is safe!
Cryptocurrencies/blockchain shouldn’t, and likely can’t, “disrupt” most of those industries. A glance through some of the industry reports in the comments shows an immense amount of work done in these respective industries. The value is in the edges.
The important thing to think through, critically, is how we’ve organized ourselves as a species, and how that orientation has changed over time. Do cryptocurrencies / blockchain offer a superior way for individuals to organize themselves around a specific network? There are some interesting questions there, and I think if we can answer those questions, the interesting applications will emerge. Right now we’re thinking of how to slap Web 2.0 onto blockchains, which, though interesting, isn’t going to bode well for anyone. Because the status-quo is superior (from performance and pricing perspective), and works well for most.
Store of Value, currencies, and financial instruments are appealing; those are applications in which humans have to orient themselves around a centralized power structure and believe. Switching the focal point of trust from a large institution (or government) to a decentralized network is an interesting thought exercise. Also think DRM.
Folks are comparing things to the 90s, but that’s a tired dog. You’ve really gotta look before that. We’re still in the installation phase, and I don’t think we’ve quite gotten to the dot com phase of this journey. That level of frenzy is yet to come.
I can answer the above for systems I've built, but I've spent quite a bit of time with those systems. How do I get better at doing this during the planning phases, or even better, for a system I'm unfamiliar with (ie. are there tools you lean on here)?
- A reasonable to use API
- A transactional component (or integrations with Sendgrid/other provider)
- Not painful to use
Here's the partial-implementation of Countermeasure 2 in geth: https://github.com/ethereum/go-ethereum/pull/16069
Of note, this fix is still susceptible to attacks, though still an improvement:
> Since geth v1.8.0 still allows the attacker to freely craft node IDs that land in specific buckets, the partial implementation of Countermeasure 2 in geth v1.8.0 means that for a given victim’s table, there can be at most 10 attacker node IDs associated with each attacker IP address. While this improves on the situation prior to geth v1.8.0 (where we could eclipse our victim using just one or two IP addresses), it does not raise the bar for attackers quite as high as we had hoped.
Still making my way through the paper and the PR to identify other things fixed. Here's the entire 1.8 release: https://github.com/ethereum/go-ethereum/releases/tag/v1.8.0