Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
avandeursen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Year-long kiagram from sky pictures every 15 seconds
(twitter.com)
3 points
by
avandeursen
5y ago
|
0 comments
2.
▲
The network structure of scientific revolutions
(twitter.com)
2 points
by
avandeursen
6y ago
|
0 comments
3.
▲
Dutch universities and Elsevier reach open access deal
(vsnu.nl)
2 points
by
avandeursen
7y ago
|
0 comments
4.
▲
How randomly skipping tests made them better (curl)
(daniel.haxx.se)
10 points
by
avandeursen
7y ago
|
0 comments
5.
▲
Delft Students on Software Architecture: DESOSA 2017
(delftswa.gitbooks.io)
51 points
by
avandeursen
9y ago
|
5 comments
6.
▲
The story of how WoSign gave me an SSL certificate for GitHub.com
(schrauger.com)
2 points
by
avandeursen
10y ago
|
0 comments
7.
▲
FlowDroid: a static taint analysis tool for Android applications
(sseblog.ec-spride.de)
1 points
by
avandeursen
11y ago
|
0 comments
8.
▲
Beyond Page Objects
(avandeursen.com)
1 points
by
avandeursen
11y ago
|
0 comments
9.
▲
by
avandeursen
11y ago
Yes, the paper is from SNAPL 2015, see http://snapl.org/2015/index.html . The incorrect 1998 was derived automatically by HN from the ACM classification in the pdf it seems.
10.
▲
by
avandeursen
11y ago
Yes, it is from the "Summit oN Advances in Programming Languages (SNAPL)", May 3-6, 2015. http://snapl.org/2015/
11.
▲
The Silently Shifting Semicolon [pdf]
(cs.ucla.edu)
53 points
by
avandeursen
11y ago
|
35 comments
12.
▲
Profiling DDL Statements: MySQL versus PostgreSQL
(blog.minicom.nl)
11 points
by
avandeursen
12y ago
|
1 comments
13.
▲
Semantic Versioning? In Maven Central? Breaking Changes!
(avandeursen.com)
1 points
by
avandeursen
12y ago
|
0 comments
14.
▲
Kicking the Bukkit: Anatomy of an open source meltdown
(slideshare.net)
98 points
by
avandeursen
12y ago
|
56 comments
15.
▲
Demystifying Conway's Law
(thoughtworks.com)
2 points
by
avandeursen
12y ago
|
0 comments
16.
▲
Why is it so hard to regulate Bitcoin?
(wired.co.uk)
1 points
by
avandeursen
12y ago
|
0 comments
17.
▲
Programmers’ Build Errors: A Case Study at Google
(cse.ust.hk)
2 points
by
avandeursen
12y ago
|
0 comments
18.
▲
Code review culture meets FreeBSD
(julipedia.meroh.net)
1 points
by
avandeursen
12y ago
|
0 comments
19.
▲
The 10 most collaborative projects on GitHub
(gousios.gr)
2 points
by
avandeursen
13y ago
|
0 comments
20.
▲
by
avandeursen
13y ago
Here's an addition to the answers from the others -- I'm one of the authors of the post. Thanks for your feedback. Perhaps we did not sufficiently emphasize it in the blog post, but we do tell the students about strong existing ar
21.
▲
by
avandeursen
13y ago
The students of the course had the same problem. We advised the students to look critically at recent open (or just closed) issues and pull requests, as well as e.g., the mailing list for the project at hand. Based on that they could get a