Prayag Verma prayagverma
| look at love | |
| how it tangles | |
| with the one fallen in love | |
| look at spirit | |
| how it fuses with earth | |
| giving it new life | |
| why are you so busy | |
| with this or that or good or bad |
| var fs = require('fs'), | |
| url = require('url'); | |
| module.exports = function (rootDir, indexFile) { | |
| indexFile = indexFile || "index.html"; | |
| return function(req, res, next){ | |
| var path = url.parse(req.url).pathname; | |
| fs.readFile('./' + rootDir + path, function(err, buf){ |
| angular.module('globalmodule') | |
| .config(['$provide', '$httpProvider', function($provide, $httpProvider){ | |
| $provide.factory('GlobalAjaxInterceptor', ['$q', '$rootScope', function($q, $rootScope){ | |
| var currentRequests={http: {}, ajax: {}}; | |
| function addHttpRequest(conf){ | |
| currentRequests.http[conf.url] = conf.promiseObj; | |
| } |
| " This will install Vundle | |
| " Setting up Vundle - the vim plugin bundler | |
| let iCanHazVundle=1 | |
| let vundle_readme=expand('~/.vim/bundle/vundle/README.md') | |
| if !filereadable(vundle_readme) | |
| echo "Installing Vundle.." | |
| echo "" | |
| silent !mkdir -p ~/.vim/bundle | |
| silent !git clone https://github.com/VundleVim/Vundle.vim ~/.vim/bundle/vundle | |
| let iCanHazVundle=0 |
| <?php | |
| /** | |
| * UNTESTED EXAMPLE! | |
| * Please don’t use in production without having tested it before! | |
| * @link http://wordpress.stackexchange.com/a/12165 | |
| * @return void | |
| */ | |
| function example__disable_rocket_cache_for_amp_pages() { | |
| if ( ! defined( 'AMP_QUERY_VAR' ) ) | |
| return; |
I want to write software that helps kill people.
Please, before you call the police and get my github account put on lockdown, allow me a moment to explain. What I really want to do is work on projects that advance the human condition and improve people's lives. I've been in a mad dash to learn how to program for the past four or five years exactly because I realized how much good I could do for the world with a computer.
| div.page-content.positions { | |
| background-color: #000000; | |
| color: #ffffff; | |
| } | |
| h3.page-title.small { | |
| color: #ffffff; | |
| } | |
| span.text-label.small.aqua.indigo { |
| <?php | |
| /** | |
| * Plugin Name: NGINX FastCGI cache purge | |
| * Version: 0.1 | |
| * Description: Flush NGINX FastCGI cache purge | |
| * Author: The Shipyard Crew | |
| * Author URI: https://theshipyard.se/ | |
| * Plugin URI: https://theshipyard.se/ | |
| * Text Domain: nginx-fastcgi-cache-purge |
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.