339 karma · joined April 2, 2012
1. Personal attach on a former employee as the head of public relation for a multi-billion corporation from a personal blog seems cowardly. Did he give Olson a chance to respond? Is there extenuating circumstances? How did Amazon carry out the investigation? Who knew what when? He accused NYTimes lapses in journalistic standard; he isn't even pretending there is any standard.
2. His attack on reporters is unconvincing. His rhetorical questions sound conniving. The reporters might not have asked those exact questions but they must have examined the named sources' credibility and employment history. Amazon might have refused to give details about Olson's termination, ironically on employee's privacy concern, and then itself divulges specifics, though I am sure after being cleared by their legal department. Noticed that Carney went into hyperboles here rather than stating any facts. A few sentences describing Amazon's interaction with reporters would go a long way here. But no, nothing.
3. His refutation of other three named sources amounts to verbal parsing. Some parts of the review are good so no parts can be called bad. Written review is good so no verbal review can be abusive. No direct requirement so everything is employee's fault and they deserve everything they get. It is almost offensive to read this part. If this is the best Amazon can come up with, it must be bad.
4. Cheery picking Amazon's interaction with NYTimes' reporter. Select publication of correspondence and one-sided characterization of interaction is sly. Make public all correspondence, with proper permission, so we can get a full picture.
Fundementall Carney is a former reporter and whitehouse spokesman who is now attacking former employees in behalf of a giant corporation with enormous resources on personal blog. He is committing every bad act he accuses NYTimes of and a lot more. It is debatable whether NYTimes followed the ideal journalistic standards but it is clear Carney follows none here.
It is hard to accurately judge someone in 45 minutes. I made a mistake with fizzbuzz three years ago when interviewing with the hacker school (now called recurse center), so what? It isn't I cannot do it but that I was looking for better ways and not finding it. After reading that there is no shorter way than to enumerate all four possibilities I was able to mentally unlock. It took just a few months of studying example code and discerning coding patterns for different logic control flows and now multiple programmers have commented that I write readable code. Anyone who has worked through real analysis problems can reason through most code well. It is a matter of concentration and time. I firmly believe programmers can make good ML engineers even though I spent years on numerical linear algebra, mathematical programming (optimization), statistics with measure theory and I still feel I have huge gaps in knowledge. So what if someone doesn't know a basic theorem, as long as they can learn enough and apply it to do their job. We take people as they are and help them grow into roles we want. I hope you will give everyone a fair chance.
I guess I am saying don't underestimate the importance of rigor in knowing precise definition of mathematical notations.
Hopefully Julia can work out all the language features and mature into a good technical language. It would also help if there is a guide about the canonical programming style. I prefer static typing but thought using type annotation I could come close to static typing while still retain the freedom of quick-and-dirty code. I believe for the current Julia I was wrong.
If Amazon is not a nice place to work, honest people writing good journalistic reporting on it are going to write negative stories, no way around that. As negative stories, this particular article isn't bad. At least it puts a leadership-principle spin on it.
The reason I said iterative optimization algorithms can be used for regression because linear regression is a quadratic optimization problem. We have analytic solutions because of special linear algebra properties. It can be said that we have a good handle on quadratic optimization problems, hence the multitude of algorithm choices. General optimization algorithms necessarily carry cost in numerical instability, but it may be a cost worth paying, especially for large data sets.
Finally, I want to echo your sentiment that DO NOT invert. Solve linear equations should be by tailored algorithms. In theory they yield identical results, in practice specific algorithms are much better.
BTW, thanks for a thought provoking article. You have given me a lot to ponder.
Modern Hadoop ecosystem is designed for different workload from MPI's. It emphasizes co-localizing date and computation, seamless robustness,and trades off raw power for simple programmingmodels. MapReduce turns out too simple, so Spark implements graph execution, which is nothing new to HPC. As far I know Spark's authors don't believe it is ready for distributed numerical linear algebra yet. But a counterpoint is that I am seeing machine learning libraries using Spark, so perhaps things are improving.
One thing I have learnt today is that MPI isn't gaining popularity. I just have a hard time picturing a JVM language in overall control in HPC where precise control of memory is paramount to performance.
I would caution people of survivor's bias. Only saints promote people with strong different options and who act on their options. Academia is full of strong egos.
Let's face it. The "top" students that Harvard and Stanford accept are past experts at gaming the system. They are total believer in and are totally committed to climbing the existing social-economic hiearchy. They worship the authorities, are perfectly content in following established lines of research, and pad themselves in the back when they re-search past results to apply to an arcane area, which in all probability ten people are ever going to find interesting and never useful. They are the perfect sheeps pretending to be lions.
Talk about entitlement.
One good thing coming from HGP for the general public and journalists, I have noticed, is that they have more discernment regarding scientists' promises. Trust, but verify. There is a snowball's chance in hell that NIH will see a substantial budget increase in this decade, or the next for that matter.
BTW, that $1000 human genome sequencing claim is not believed by most scientists. Lawyers can argue it, especially Illumina's, but not according to common sense.
By the way, Cramer's rule is useless for numerical computation, but it is immensely useful in theoretical work. It belongs to the vast body of work dealing with determinants before the rise of linear algebra. Determinant is the only obvious connection to algebra left in an undergraduate's linear algebra course, so I can understand people are turned off by it.
I agree that the accessors, setters of GRange are consistent. I was having trouble picturing how manipulating the range part impacts the dataframe. I think they are like a database table joint but that is not explicitly spelled out. It becomes even less clear what happens to the attached dataframes when merging two GRange intervals. I once had to a symmetric difference of two GRange and it took a few hours of staring at the manual and trying out things at the command prompt.