| #!/bin/bash | |
| # | |
| # Add latency to all outgoing traffic on $DEV on tcp/udp $PORT, | |
| # in the amount of $DELAY. | |
| # | |
| # This is matching on both source port and destination port, which | |
| # may hit you twice if you're accessing a local resource. | |
| # | |
| # To see what's currently in effect, | |
| # tc -s qdisc show dev lo |
| #!/usr/bin/env python3 | |
| """ | |
| Command line zbase32 encoder and decoder. | |
| See http://philzimmermann.com/docs/human-oriented-base-32-encoding.txt | |
| Please note that scrip loads the data in memory. | |
| Copyright: Tocho Tochev <tocho AT tochev DOT net> | |
| Licence: MIT | |
| """ |
| /* | |
| * tunproxy.c --- small demo program for tunneling over UDP with tun/tap | |
| * | |
| * Copyright (C) 2003 Philippe Biondi <[email protected]> | |
| * | |
| * This program is free software; you can redistribute it and/or modify it | |
| * under the terms of the GNU Lesser General Public License as published by | |
| * the Free Software Foundation. | |
| * | |
| * This program is distributed in the hope that it will be useful, but |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
Okay, the title of this post is a bit of a lie. There's no one secret trick to becoming a genius programmer - there are two, and they're more habits than tricks. Nevertheless, these kind of 'secret tricks' seem to resonate with people, so I went for this title anyway.
Every once in a while, a somewhat strange thing happens to me. I'll be helping somebody out on IRC - usually a beginner - answering a number of their questions in rapid succession, about a variety of topics. Then after a while, they call me a "genius" for being able to answer everything they're asking; either directly, or while talking about me to somebody else.
Now, I don't really agree with this "genius" characterization, and it can make me feel a bit awkward, but it shows that a lot of developers have a somewhat idealistic and nebulous notion of the "genius programmer" - the programmer that knows everything, who can do everything, who's never stumped by a problem, and of which ther