HN user
Lots of platforms like gaming consoles have exclusive content where the same company is both the hardware/services owner and the content creator. What would be anticompetitive is they leveraged their position as an app platform to stunt other legitimate chat apps from gaining popularity. Beeper claims that’s what’s happening to them but their legitimacy is debatable.
It’s also either naive or a troll. If that did become the handshake it would be reverse engineered and spoofed by bad actors just the same.
I honestly don't think there's anything wrong with admitting we as humans have these kinds of pre-selection social biases baked into us as a survival trait. We just have to be conscious of it and try to fight it when we sense it working against our goals, especially in a hiring context.
That said what you did for your friend was perfectly reasonable knowing full well many people have these biases and will not make the effort to fight them consciously.
And maps. Pretty big misfire by the author.
A few quick tips to help slow Spark tests.
1. Make sure you're using a shared session between the test suite. So that spin-up only has to occur once per suite and not per test. This has the drawback of not allowing dataframe name reuse across tests, but who cares.
2. If you have any kind of magic-number N in the SparkSQL or dataframe calls (e.g coalesce(N), repartition(N)) change N to be parameterized, and set it to 1 for the test.
3. Make sure the master doesn't have any more than 'local[2]' set. Or less depending on your workstation.
Looks like there was internal pressure at Meta to reverse the reversal once this got traction. https://www.linkedin.com/posts/zhuozhuo_update-yesterday-aft...
Georgia Tech online masters looks like it does. I found this in the article author’s links when he breaks down the schools. Id really like to take this class too so it stood out to me.
And yet the vast majority of money laundering still happens through traditional banking channels. If crypto was such a panacea for laundering all the traffic would have switched over by now.
Profit comes when their operating costs are less than the take home from any transaction fees and Coinbase rewards they’ve collected in the same period. It’s not a direct function of liquidity entering the system. It’s true that rising prices from new cash flow means more profit for miners, but that doesn’t imply the opposite. The price could stay constant for the next 100 years and miners that have found a way to remain profitable within that price point would be fine.
This is addressed in the original white paper. In a world where BTC is valued at 1M USD/coin you’d also expect a decent amount of day to day usage. Miners could still make decent profits based on transaction fees just from confirming blocks even once the Coinbase rewards stop. I’m not saying that’s currently the case, but that is the design. Also if miners are making a profit off let’s say $40k/coin and the price goes down to 30, yet there’s still a profit for some miners, how exactly does that become unsustainable?
This is effectively what CTE style syntax gives you. I always find them more intuitive for intermediate to advanced queries for exactly this reason. They’re also much easier for another reader to later come in and deduce what the query is doing.
We use the dialyzer and also heavy usage of the @spec function signature annotation on public module functions to work around this. It’s an nice compromise between some defensive safety while still enjoying the readability of the dynamic typing.
He’s saying if someone gets in the habit of using that style they have to be very careful. If they forget to change True to False when using an OR that it could have major consequences. Performance being the least of concerns.
Thanks. I tweaked the script to include an incremental printout across files and also creating an index on phone num to easily search.
The interface got rolled into Pandora Premium after they were acquired.
An early acquisition that he played a pivotal role inducing. They would have been better off without him, so it's hard to call him a founder with a straight face.
I'm sorry if he was some kind of hero of yours that you have to emphasis some trivial contribution he made in the grand scheme of Reddit's success.
Doubtful in this scenario that they would take it as far as to threaten physical violence. That would up the anty involving law enforcement if Sony were to call out their bluff.
The threat is most likely real.
The last section on organizational chaos and the magic power is key.
This is a good point. A company should not be expected to just throw a bunch of shows out and see which ones stick. Too expensive.
What stuck out to me most in the speech was Kevin Spacey's quick mention of Netflix's response to the pitch: "We ran the numbers and we think our customer base would like it".
Media outlets thinking of taking the all-in approach will need the technology to calculate and hedge the risk . Netflix clearly has that in place, and it helped convince them to take a chance.
Been loving Diffbot for my startup. Only downside is you very rapidly approach the freemium tier for any production loads. It works fantastically well though.
One of the Cloudera devs told me 80% of all Hadoop users run Hive. This suggests most devs secretly want to continue using SQL, but want more scalable relational solutions. Thus why Cloudera is backing Impala, and Facebook is about to open source Presto.
I worked on an entire team of developers where I was the only one who understood the raw Java MapReduce API. Almost everyone else on my team got by with learning HiveQL, and a very minimal understand of MapReduce design flow.
Your belief is absolutely correct.
One of my earlier employers exhaustively tried many of these strategies including generous referrals. Ultimately it came down to just a numbers game. Pay a reputable tech-recruiter for resumes, hit the grind, and you'll find some diamonds in the rough. If you have 30k budget to offer tempting bonuses, you should just hire a recruiter.
Tech hiring almost has to be approached like the NFL draft. Companies seem fixated on playing the free agency aspect, making lucrative offers to known entities and depending on word of mouth and reputation. Waiting on a 'sure thing' can cripple your business. They'd be better off interviewing and taking more chances on younger unproven commodities out of college without the rockstar resume and ego. A talented young engineer can become senior very quickly.
DARPA is also working closely with the Blaze team on several projects to enhance its functionality and performance, so it will continue to improve. I'm not aware of any money being directly invested, but the organization has a way of encouraging projects it finds promising.
I agree everybody should know the basics of HTML/CSS to become what I call "semi-technical", even if you're not attempting a startup. You might find you have an artistic flare for digital design, and suddenly become that much more marketable.
That being said, why would you want to found a startup if not to build something cool and get people interested in it? If that's not your natural passion, it's no coincidence you don't already have skills a technical company would find valuable.
Most users would just answer yes, thinking bad things might happen if they run out of 'disk space'. So you'd still need some kind of eviction strategy for people that never said no.
Prompting should be a configurable setting for users aware of the restrictions. By default, I would have it evict based on timing interval for normal users, unless prompting was enabled.
There's always the ever-popular enron emails. http://www.cs.cmu.edu/~enron/
A bit played out, but solid.
My experience has been more big data management and analytics. Less on the startup angle. There are a lot of hidden costs associated with maintaining your own dedicated hardware. Our projects here invested quite a bit into several internally maintained clusters, and it hasn't been perfect. There is a lot of opportunity cost wasted in having developers forced to constantly flex their sysadmin muscles. My time is best served solving problems that leverage the cloud, not tuning and maintaining it. The context switching can be very distracting.
It's actually faster for me to use EC2 whenever I have major calculations than our internal cluster. I get on demand scaling up with the fine tune control I need to micromanage when necessary.