| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
| $ cat noexit.sh | |
| #!/bin/sh | |
| seq 100 | while read; do exit; done # If `exit' terminated the script .. | |
| echo 'Still alive!' # .. this message would not be printed. | |
| $ | |
| $ sh noexit.sh | |
| Still alive! |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
Since this is on Hacker News...
_t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".while loops because shut up, you're overthinking a joke.
| /* | |
| This brute force algorithm was originally written (by me) back in 1998, and has been collecting dust | |
| since then. However, for the purpose of testing Gist on GitHub I decided to rewrite the algorithm | |
| from VB6 to C#, make some improvements and release this fast, compact, non-recursive, brute force | |
| algorithm under the MIT license: http://opensource.org/licenses/MIT | |
| Notes: | |
| - Do a run with testLetters = "0123456789" and testLength = 3, to see what happens | |
| - Remember to keep the callback testCalback as fast as possible | |
| - Tweet some love to @fredrikdev :) |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| greek_alphabet = { | |
| u'\u0391': 'Alpha', | |
| u'\u0392': 'Beta', | |
| u'\u0393': 'Gamma', | |
| u'\u0394': 'Delta', | |
| u'\u0395': 'Epsilon', | |
| u'\u0396': 'Zeta', | |
| u'\u0397': 'Eta', | |
| u'\u0398': 'Theta', | |
| u'\u0399': 'Iota', |
| #!/bin/bash | |
| function jsonval { | |
| temp=`echo $json | sed 's/\\\\\//\//g' | sed 's/[{}]//g' | awk -v k="text" '{n=split($0,a,","); for (i=1; i<=n; i++) print a[i]}' | sed 's/\"\:\"/\|/g' | sed 's/[\,]/ /g' | sed 's/\"//g' | grep -w $prop` | |
| echo ${temp##*|} | |
| } | |
| json=`curl -s -X GET http://twitter.com/users/show/$1.json` | |
| prop='profile_image_url' | |
| picurl=`jsonval` |
| M[16],X=16,W,k;main(){T(system("stty cbreak") | |
| );puts(W&1?"WIN":"LOSE");}K[]={2,3,1};s(f,d,i | |
| ,j,l,P){for(i=4;i--;)for(j=k=l=0;k<4;)j<4?P=M | |
| [w(d,i,j++)],W|=P>>11,l*P&&(f?M[w(d,i,k)]=l<< | |
| (l==P):0,k++),l=l?P?l-P?P:0:l:P:(f?M[w(d,i,k) | |
| ]=l:0,++k,W|=2*!l,l=0);}w(d,i,j){return d?w(d | |
| -1,j,3-i):4*i+j;}T(i){for(i=X+rand()%X;M[i%X] | |
| *i;i--);i?M[i%X]=2<<rand()%2:0;for(W=i=0;i<4; | |
| )s(0,i++);for(i=X,puts("\e[2J\e[H");i--;i%4|| | |
| puts(""))printf(M[i]?"%4d|":" |",M[i]);W-2 |