I hereby claim:
- I am dandrzejewski on github.
- I am dandrzejewski (https://keybase.io/dandrzejewski) on keybase.
- I have a public key ASAAWF9MMWtGes-S6bR5MRk4ctqjGrKaQKDtCzulY4qJoQo
To claim this, I am signing this object:
#!/bin/sh | |
# cron script for checking wlan connectivity | |
# change 192.168.1.1 to whatever IP you want to check. | |
IP_FOR_TEST="192.168.1.1" | |
PING_COUNT=1 | |
PING="/bin/ping" | |
IFUP="/sbin/ifup" | |
IFDOWN="/sbin/ifdown --force" |
I hereby claim:
To claim this, I am signing this object:
<meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no, width=device-width"> | |
<meta name="format-detection" content="address=no;email=no" /> |
Hello software developers,
Please check your code to ensure you're not making one of the following mistakes related to cryptography.
Kris Nuttycombe asks:
I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?
I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.
I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.