Dave Rolsky
blog.urth.org · Personal blog · on HN since 2009
Dave Rolsky, a software developer, writes about Perl, Rust, Go, security issues in libraries, and tech job hunting and interviewing.
What HN saysHN links it for his posts on TAP parsing problems, Perl IP address security bugs, and interview practice. One commenter calls his interviewing style sensible.
20HN people shared it
4linked it in comments
42stories submitted
563story points
8 months agolast shared
2009people per year2026
Most-shared posts
- 1Yet Another GitHub Profile Generator2 people · 83 points · first shared 2022 · 23 comments on HN
- 2Tech Interviewer Theory2 people · 4 points · first shared 2016 · discussion on HN
- 3Security Issues in Perl IP Address Distros2 people · 3 points · first shared 2021 · 3 comments on HN
- 4Front End Rust Without Node2 people · 3 points · first shared 2022 · discussion on HN
- 5Writing a PostgreSQL formatter / pretty printer in Rust. (2021)2 people · 2 points · first shared 2021 · discussion on HN
- 6Software Job Search 2022 Retrospective: Coding Challenges2 people · 2 points · first shared 2022 · 3 comments on HN
- 7Perl 6 is fun1 people · 194 points · first shared 2015 · 145 comments on HN
- 8Down the Golang Nil Rabbit Hole1 people · 181 points · first shared 2021 · 157 comments on HN
- 9Want Good Tools? Break Your Problems Down1 people · 34 points · first shared 2009 · 1 comments on HN
- 10Project Stack Push/Pop1 people · 5 points · first shared 2010 · 2 comments on HN
- 11Perl 5 Core Principles1 people · 4 points · first shared 2011 · discussion on HN
- 12A World Without Copyright1 people · 4 points · first shared 2012 · 1 comments on HN
- 13Google Plus Circles Don't Solve My Problem1 people · 3 points · first shared 2011 · discussion on HN
- 14My New OO Docs for the Perl Core Have Been Merged1 people · 2 points · first shared 2011 · discussion on HN
- 15Simple.com’s Password Strength Check1 people · 2 points · first shared 2013 · discussion on HN
What HN people wrote when they linked it
autarch · 2022-11-05
TAP is better than some things, but it has some serious issues that I wrote about on my blog a while back - https://blog.urth.org/2017/01/21/tap-is-great-except-when-its-not/
Basically it's nearly impossible to fully parse it correctly.
matthewpersico · 2022-04-25
https://blog.urth.org/2022/04/19/software-job-search-2022-retrospectiv…
I have a two word answer: Intellectual Property. Not everyone is an accomplished Open Source publisher, nor should that be a requirement for employment. So what existing project do those candidates point the interviewer at? Someone else's IP? And then the hiring company is obligated in self-defense to make sure that it's not someone else's IP, lest it end up in someone's hard disk accidentally and get discovered in some otherwise unrelated audit? No. Thank. You. Keep your own code to yourself.
Now, you might point out your own code with some URLs and they may take a look at it. But that's not the same as making it part of the interview process.
fanf2 · 2021-03-29
And as predicted, the issue is turning up in other places, for instance https://blog.urth.org/2021/03/29/security-issues-in-perl-ip-address-di… (comments https://news.ycombinator.com/item?id=26628827)
kafkaesq · 2016-03-10
And the above poster would seem to have an eminently sensible interviewing style, himself:
http://blog.urth.org/2016/03/08/tech-interviewer-theory/