Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phasmantistes
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
phasmantistes
10y ago
Assigning pull requests to multiple people is fantastic: sometimes you're modifying a library and want the owner of that library to review your code, but you're simultaneously modifying the clients of that library and want their o
62.
▲
by
phasmantistes
10y ago
This is just the pipeline argument. And while there are very real aspects to the pipeline -- yes, women and minorities drop out of the tech industry in early education, late education, and on the job -- the problem with the argument is that
63.
▲
by
phasmantistes
10y ago
A short summary: * Oracle sues Google on copyright grounds. * Case is overseen by Judge Alsup, who taught himself Java in order to understand the technical merits of the case. Case is split into two phases: copyright and patents. * A jury f
64.
▲
by
phasmantistes
10y ago
As I understand it, she was taking unpaid leave from her day-job at Vice Motherboard (despite then producing full-length articles for Motherboard on the topic).
65.
▲
by
phasmantistes
10y ago
That was from the first time around in this trial, before it was overturned at the Federal Circuit level and sent back to Judge Alsup for a retrial.
66.
▲
by
phasmantistes
10y ago
I'd also just like to give huge props to Sarah Jeong for keeping up such a high-quality live stream of tweets over the course of the entire trial. That's reporting done right.
67.
▲
Jury decides in favor of Google in Google v. Oracle case
(mobile.twitter.com)
4 points
by
phasmantistes
10y ago
|
1 comments
68.
▲
by
phasmantistes
10y ago
The primary reason you don't use those large wheels is the same reason that the boosted board has the same range as your monowheel at half the weight: large wheels (especially air-filled ones) with tread have incredibly high rolling re
69.
▲
by
phasmantistes
10y ago
Chromium already puts heroic effort into maintaining form state. Note that, a lot of the time, it works great. For example, here on HN, if you enter half a comment, go back, and then forward, your comment will be preserved. But it is hard
70.
▲
by
phasmantistes
10y ago
Those folks are already using Alt+<arrow keys>, because that is guaranteed to work no matter what element is focused.
71.
▲
by
phasmantistes
10y ago
Code reviews should be asynchronous. Everyone on your team should be able to be working on multiple small changes/commits/whatever in parallel. While one is out for review, they're working on the others. Different people keep
72.
▲
by
phasmantistes
10y ago
What? These statements and conclusions make no sense to me. Code reviews mean that every time I want to integrate with master I've got to 'grab a lock' and schedule and wait for a code review. You're using a terrible c
73.
▲
by
phasmantistes
10y ago
Yep, and design docs are the most important part of that planning for change. If you haven't planned the desired design, you can't see how circumstances are forcing you to change it, and what tradeoffs you'll be making to acc
74.
▲
by
phasmantistes
10y ago
Yep, that's right. To lay out the example the way you did in the article, it would look like: >>> foo = A.b >>> bar = A.b >>> hex(id(foo)) '0xdeadbeef' >>> hex(id(bar)
75.
▲
by
phasmantistes
10y ago
The Offshore Secrets (2013) was a specific leak about British offshore holdings in the Virgin Islands. The Panama Papers (2016) is a specific leak about offshore holdings managed by Mossack Fonseca in Panama. This database contains data fro
76.
▲
by
phasmantistes
10y ago
It's clearly not just a design error. A conscious design decision was made: build the building with supports in the middle of the sides instead of the corners. This, in and of itself, was not a bug. In addition, a conscious implementa
77.
▲
by
phasmantistes
10y ago
Good on Dan for being a voice of reason and collecting the findings of reddit/hn/#bitcoin into a central location. And as he says, good on Gavin for being equanimical despite the vitriol being thrown his direction from some quarte
78.
▲
by
phasmantistes
10y ago
If you had this exploit, how would you have monetized it? Do you know who to talk to? Do you know where to go on the darkweb to find the people who know the people who have the money to actually pay you for this? Do you know how to negotiat
79.
▲
by
phasmantistes
10y ago
“You can’t have the technology to wake people up and not have the technology to do a bunch of other great things, like provide abundance to the population.” Sure you can. Just a couple paragraphs previously, you were making the point that
80.
▲
by
phasmantistes
10y ago
A Beautiful Mind isn't as long ago as you think: less than 15 years. In the space of cinema (which was producing films about famous artists at least as early as the '30s) that's not very long. Takedown and Pirates of Sil
81.
▲
by
phasmantistes
10y ago
You're absolutely right. But the movie is not meant to be a documentary about the math, it is meant to be a story about his life. The same goes for Theory of Everything, Imitation Game, and A Beautiful Mind. The different here is that
82.
▲
by
phasmantistes
10y ago
I was lucky enough to see The Man Who Knew Infinity this past weekend at the San Francisco International Film Festival. And I'd just like to say that it is a truly beautiful film, and I encourage everyone to go see it. After the showin
83.
▲
by
phasmantistes
10y ago
It's not, not to much of the general populate. This has been reinforced by decades of science fiction in which fingerprints or handprints get characters access to secure resources. It's also been reinforced by Apple's messagi
84.
▲
Monorail, Chromium's bug/issue tracker, is now Open Source
(chromium.googlesource.com)
5 points
by
phasmantistes
10y ago
|
0 comments
85.
▲
by
phasmantistes
11y ago
At what point does lack of information disclosure in the warrant application render the warrant itself invalid? Is there any precedent for invalidating warrants -- and therefore any information gleaned from the search, and perhaps allowing
86.
▲
Remove Chromium Sandbox on Windows
(codereview.chromium.org)
6 points
by
phasmantistes
11y ago
|
0 comments
87.
▲
by
phasmantistes
11y ago
Yep, in chromium-land we do something similar: You can upload multiple different versions of a single code review, and reviewers can diff both against the base and against previous versions of the review. This is helpful for showing "s
88.
▲
by
phasmantistes
11y ago
Absolutely. If someone formulates their PR such that every commit in the chain is small, easily reviewable, and passes all tests, that's fantastic! That makes reviewing code, searching history, and bisecting all easier. Unfortunately,
89.
▲
by
phasmantistes
11y ago
Squashing entire pull requests that change multiple things into a single commit is a bad idea, yes. But uploading and asking for review on such wide-reaching pull requests is a bad idea in the first place. Using fast-forward without squash
90.
▲
by
phasmantistes
11y ago
I actually disagree. Large teams that still have linear commit histories doesn't mean it is a lie. It means that the code review process is more important that the code writing process. For example: I check out a repository, and cr
More ›