ok
> CVE-2013-4484: Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI.
:|
21–29 of 29 posts
ok
> CVE-2013-4484: Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI.
:|
"I no longer think about code lines as an asset to be accumulated, but rather as an expenditure to be avoided." Good quote. Took me until my 30s before I started realizing this myself. Seems obvious in retrospect.
A practice we've implemented to manage this is tagging pull requests that have anything over 250 added (green) lines of code. Before anyone is willing to give you a code review, you have to justify why such a pull request requires so many lines, break it into multiple pull requests, or refactor your code. Often times, it makes review easier because the PR's are smaller and enforces a simple baseline that tells the pr…
https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD103...
Also, the varnish source is really nice! Pen kode ;)
http://programmers.stackexchange.com/questions/103807/what-i...
Slovak proverb: "ponáhľaj sa pomaly" -- Be not hasty, when you hurry.
English has "more haste, less speed" which I think carries the same message.
It's just so awkward. Yet the grammar isn't bad; there is nothing wrong with "walk slowly" or "eat slowly".
"Ponáhľaj sa pomaly" is perfectly euphonic to the Slovak ear, while "hurry slowly" seems clumsy somehow. We need to make it more sophisticated somehow, like "make slow haste", or "slow haste makes faster" or whatever.
What is the reason ...
I suppose; if everyone said "hurry slowly!" it might wear into usage.
Slovak proverb: "ponáhľaj sa pomaly" -- Be not hasty, when you hurry.
"I no longer think about code lines as an asset to be accumulated, but rather as an expenditure to be avoided." Good quote. Took me until my 30s before I started realizing this myself. Seems obvious in retrospect.
http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036...
...if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.
2 December 1988