I hereby claim:
- I am bag-man on github.
- I am bag_man (https://keybase.io/bag_man) on keybase.
- I have a public key ASDcVWpn_Gzg_zivsjlklILaFDKNDBCaRxiwJdJvvdMIdQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
module.exports = function findCodingRange (codingSeq, contig, reverse) { | |
let codingLength = codingSeq.length | |
, start = 0 | |
, end = 0 | |
, selector = 12 | |
, fail = false | |
start = contig.indexOf(codingSeq.substring(0, selector)) | |
end = contig.indexOf(codingSeq.substring(codingLength - selector, codingLength)) + selector |
This is an assessed reflection on some workshops that we did for Agile Methodologies
As part of the course we have done three two hour workshops on Agile methodologies. These have been interesting as they have formalised the practises that I had been doing previously in my industrial year.
For example I wasn't aware that pair programming, test driven development, and continuous integration were part of extreme programming, however I had been using them all year. It was also interesting to see that other practices I had been trained in were closely related to the agile manifesto, such as creating and weighting stories, but we weren't following agile in any formal way.
Pair programming is an excellent tool and from experience of the workshops, personal projects and my industrial year, I can argue that working as a pair is a lot more efficient than working individually. The caveat for this is that both partners are at the same level of familiarisation
import praw | |
import random | |
import os | |
from urllib.request import urlretrieve | |
r = praw.Reddit(user_agent='wallpapergrabber') | |
submissions = r.get_subreddit('offensive_wallpapers').get_hot() | |
urls = [] |
'use strict' | |
const url = require('url') | |
function getUrl (dataUrl) { | |
if (dataUrl.split('://').length === 1 || dataUrl.startsWith('://')) { | |
dataUrl = `http://${dataUrl.replace('://', '')}` | |
} | |
return dataUrl | |
} |
Here at Clock we love ZFS, and have been running it in production on our Linux file servers for several years. It provides us with numerous excellent features, such as snapshotting, incremental send/receive, and transparent compression. With the recent release of Ubuntu Xenial 16.04 official support for ZFS is now here, and we are keen to integrate it fully into our next generation hosting stack.
As a Node.js and MongoDB house, one of our main concerns has been how MongoDB will perform on ZFS on Linux, especially after reading about potential problems other people have faced. There really isn't much data out there to put our minds at rest.
We decided to setup a method of benchmar
formatDrives() { | |
mkfs.ext4 /dev/sdc | |
mkfs.xfs /dev/sdd | |
} | |
createZFS () { | |
sleep 30 | |
zpool destroy tank | |
zpool create -f -m /zfs tank /dev/sde | |
if [ $1 ]; then |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <unistd.h> | |
#include <pthread.h> | |
void end() { | |
printf("Game over.\n"); | |
exit(0); | |
} |
index a2cb700..2c44b3d 100644 | |
--- a/plugin/fugitive.vim | |
+++ b/plugin/fugitive.vim | |
@@ -3012,7 +3012,7 @@ function! fugitive#statusline(...) abort | |
if &statusline =~# '%[MRHWY]' && &statusline !~# '%[mrhwy]' | |
return ',GIT'.status | |
else | |
- return '[Git'.status.']' | |
+ return ' '.status | |
endif |
loadkeys uk | |
wifi-menu | |
lsblk | |
cgdisk /dev/sda #100M EF01 boot | |
cryptsetup -y -v luksFormat /dev/sdaX | |
cryptsetup open /dev/sdaX cryptroot | |
mkfs -t ext4 /dev/mapper/cryptroot | |
mount -t ext4 /dev/mapper/cryptroot /mnt | |
mkfs -t ext4 /dev/sdaY | |
mkdir /mnt/boot |