Skip to content

Instantly share code, notes, and snippets.

View pberry's full-sized avatar
🏠
Working from home

Patrick Berry pberry

🏠
Working from home
View GitHub Profile
@pberry
pberry / call-numbers.txt
Created February 21, 2012 18:38
Call Numbers
D764.3.M6 B73 2006
D757.9.D7 D4 2006
D772.M23 M67 2006
DS126.6.S42 D3613 2006
DS485.K27 B395 2006
D757.56 Nr. 7 .M57 2007
D760.L56 M68 2006
DA45 P62 (Main Collection)
DK511 S3 P65 1989 (Main Collection)
DS63.1 P69 1989 (Main Collection)
@pberry
pberry / stupid_sort.txt
Created February 13, 2012 21:55
Excel nightmare sort
AC1 G72 vol.53 (Main Collection)
AC1 G72 vol.54 (Main Collection)
AC1 G72 vol.7 (Main Collection)
AC1 G72 vol.8 (Main Collection)
AC1 G72 vol.9 (Main Collection)
The definition of "sysadmin" may be a bit murky. So, some context...at my institution, sysadmins handle system provisioning, patching, security, networking -- real "low level" stuff. They don't like to touch "apps". These "low level" jobs (minus the security of course!) are the kinds of jobs that are increasingly becoming commoditized by hosted services (or every locally with awesome systems like Puppet). And that's great! It gives organizations a choice.
When you're think about pushing systems outside of your own infrastructure you need to consider more than just the initial deployment. In fact, you mention that the future is about "managing your own cloud-based solution" and I couldn't agree more. About the managing part, this is! Who will maintain the system? I'm not talking about keeping it running, that's what the cloud service does. I'm talking about configuration.Who will integrate it with other existing systems? Who will even figure out if it can be integrated? Who will patch it, if you're
name: Albondigas (meatballs)
ingredients: |
2 lbs grass fed ground beef
2 cloves minced garlic
2 tbsp ground cumin
2 tbsp dried oregano
1 tbsp black pepper (in the demo I said 2 tbsp but I meant 1)
1/8 tsp cayenne pepper
1 tsp sea salt
4 tbsp olive oil
@pberry
pberry / example.yml
Created May 17, 2011 22:59
Example recipe file for Paprika
name: My Tasty Recipe
servings: 4-6 servings
source: Food Network
source_url: http://www.google.com
prep_time: 10 min
cook_time: 30 min
nutritional_info: 500 calories
difficulty: Easy
rating: 5
notes: |
javascript:
(
function()
{
var source = document.documentElement.innerHTML;
var regex1 = /appeared in print on
((January|February|March|April|May|June|July|August|September|October|November|December)
([1-2][0-9]|3[0-1]|0?[1-9]), ((19|20)[0-9][0-9])), on page (\w+) of the
New York edition with the headline:(.*)</g;
var match = regex1.exec(source);
def penny(self, irc, msg, args):
html = urlopen("http://www.penny-arcade.com/archive/").read()
soup = BeautifulSoup(html)
tagcloud = soup.find("ul","tagcloud")
tags = []
for tag in tagcloud.findAll('li'):
tags.append(tag.a.string)
mytag = tags[randint(0, len(tags))]
search = urlopen("http://www.penny-arcade.com/archive/?q=" + mytag).read()
comiclist = BeautifulSoup(search)
def wine(self, irc, msg, args):
"""Get a nice glass of wine
"""
json = urlopen("http://www.patandkat.com/json/wine.json").read()
wines = []
for bottle in simplejson.loads(json):
wines.append(bottle['url'],bottle['wine'])
wine = wines[randint(0, len(wines))]
if len(args) > 0:
nick = ' '.join(args)
@pberry
pberry / messages.log
Created December 23, 2010 17:56
Supybot choking on wordstats
ERROR 2010-12-23T09:54:12 supybot Uncaught exception in ['wordstats'].
Traceback (most recent call last):
File "/home/pberry/lib/python2.4/site-packages/supybot/callbacks.py", line 1181, in _callCommand
self.callCommand(command, irc, msg, *args, **kwargs)
File "/home/pberry/lib/python2.4/site-packages/supybot/utils/python.py", line 86, in g
f(self, *args, **kwargs)
File "/home/pberry/supybot/plugins/WordStats/plugin.py", line 174, in callCommand
return self.__parent.callCommand(*args, **kwargs)
File "/home/pberry/lib/python2.4/site-packages/supybot/utils/python.py", line 86, in g
f(self, *args, **kwargs)
Old: /prs/EMs/EM86/em86_04.htm
New: /prs/EMs/1986/86-004.shtml
Reg:
Old: /prs/EMs/EM00/em00_01.htm
New: /prs/EMs/2000/00-001.shtml
Reg:
Old: /pre/EMs/EM00/em00_105.htm
New: /prs/EMs/2000/00-105.shtml