I think this is a very classic "waterfall" world view.
In many cases, the problem can only be understood through many failed solution attempts. It could be because the actual problem is novel. It could be because there is a different way of thinking about the problem that is not apparent studying only what a customer does today with the limitations of the software that they have right now.
The point of "move fast, break things" is to address this fallacy that anyone can fully understand a problem before attempting the solution; it is often the case that in attempting a solution, one comes to understand the actual, valuable problem.
Waterfall means designing and building everything before rolling it out to users. Researching a problem before you start tackling it is just general good advice. You can be more effective while moving fast and breaking things while still taking some time to know where to move and what is ok vs not ok to break.
So what? The article describes the political implications of the Census Bureau errors. I cited the Census Bureau release itself so you can cross-check whether the factual assertions in the article are accurate.
> and also implies political causes.
> So it's useful to identify this as not something a journalist or credible outlet would actually put their name to.
> An independent analysis by the Pew Research Center and election data experts calculated exactly how those specific errors altered the final map. If the census had perfectly matched the PES estimates, the seats would have shifted as follows: [table showing apportionment errors cost Texas and Florida 1 seat each, and gave Minnesota, Rhode Island, and New York 1 undeserved seat each.
Fucking up 5 House seats for a decade seems like a firing-worthy offense.
> Sergey Brin and Larry Page came up with this precise algorithm, i.e., PageRank, which was one of the key algorithms that helped catapult Google into a household name and made them tons of money. Both Sergey and Larry were grad students at Stanford, so their coming up with such an amazing algorithm doesn’t seem surprising.
Inventor in the context of a U.S. patent has a very narrow and technical meaning, different from the broader concept of "coming up with something." Larry Page and Sergey Brin developed PageRank together as grad students in Stanford's Digital Library Project, led by Hector Garcia-Molina. This is simply undisputable and both are listed as co-authors of the PageRank paper [1]. The list of inventors on a patent, especially nowadays, should not be seen as a historical finding about credit.
Inventorship of patents has a clear legal basis, and is quite different from the basis of scientific authorship.
The system disincentifies adding "ghost" inventors since incorrect listing of the inventors can invalidate a patent.
So, yes, it's likely that the patent attorneys hired by Stanford advised that only Page should be listed as an inventor. Stanford gets its money via the assignment, not the inventor list.
How much effect the CPU's register remapping has? Probably a lot and the article doesn't discuss it at all.
However, the Intel Xeon E-2236 was released in 2019; so it's hardly ancient and the current E-2400 isn't so different.
As for hardware register renaming, Tomasulo dates to 1967 and out-of-order ROBs were common in the 90s. I don't know that there's been any major new ideas microarchitectural ideas in register renaming since the 90s.
I still think it's a meaningful experiment but could be improved with consideration of microarchitectural features.
I was taking 5mg of Creatine and was in the ER for an unrelated reason. My metabolic panel measured creatinine at 1.34 mg/dL. A panel from last year without the supplement was a very normal 0.95. These were gummies and I wasn’t slamming water.
BTW, it tends to trash the eGFR test which relies on an unbiased creatinine reading.
reply