awk 'match($0,/regexp/) {print substr($0,RSTART,RLENGTH)}' inputfile

and about 1 time in 10 I’m startled to remember grep makes this very easy…

grep -o regexp inputfile

From here.

Here’s what I came to understand. Every communication protocol has a state machine. For some protocols they are very simple, for others they are more complex. When you implement a protocol via RPC, you build methods that modify the state of the communication. That state is maintained as a black box at the endpoint. Because the protocol state is hidden, it is easy to get things wrong. For instance, you might call Process before calling Init. People have been looking for ways to avoid these problems by annotating interface type information for a long time, but I’m not aware of any mainstream solutions. The fact that the state of the protocol is encapsulated behind method invocations that modify that state in non-obvious ways also makes versioning interesting.

The essence of REST is to make the states of the protocol explicit and addressible by URIs. The current state of the protocol state machine is represented by the URI you just operated on and the state representation you retrieved. You change state by operating on the URI of the state you’re moving to, making that your new state. A state’s representation includes the links (arcs in the graph) to the other states that you can move to from the current state. This is exactly how browser based apps work, and there is no reason that your app’s protocol can’t work that way too.

Also, Martin Fowler’s article Richardson Maturity Model: steps toward the glory of REST is excellent. Richardson’s book, Restful Web Services, doesn’t mention his own maturity model or HATEOAS itself — it gives the most passing of references to Link tags or headers, for example. Good book, though.

The other night, I needed to dig back into that script and found my brain itching from the way the script had organically grown a bit sideways over time, so I decided to refactor it and toss it up on Github in case it’s helpful as a starting point for anyone who wants to do something similar.

Magit Cheatsheet

Also including the upstream org-mode file in case you feel like wrestling with org-mode’s org-export-as-html and its weird set of quasi-controls.

In order to get org-mode to export that nicely, I had to add two user variables to my .emacs, along with a macro I used to quick-replace the TD elements with the classes they need. Here’s the snippet.

I’m all about top and mytop, but there’s at least one surprise in here for me — namely, /usr/bin/tload.

Measuring & Optimizing I/O Performance using iostat…

If IO performance is suspect, iostat is your best friend. Having said that, the man pages are cryptic so don’t be surprised if you find yourself reading the source. To get started, identify the device in question and start a monitoring process…

which contains a note on how Facebook stores 360 photo uploads every second.

Here’s a blow-by-blow transcript of their systems getting completely wiped out by someone who didn’t agree with their practices. The transcript is hosted on pastebin.com but was originally available as the index.html of the site itself.

It looks like they used custom code to exploit a hole in astalavista’s Litespeed webserver; googling the exploit used just brings up copies of the transcript itself.

This is probably the most brutal exploit transcript I’ve ever seen — reference line 1839 where the exploiter, having found where the backups are being stored by trawling the admin’s .bash_history, FTPs there and deletes their offsite backups. (If your production system stores the FTP password or password-less SSH keys to your offsite backup server, exposed through your .bash_history no less, is it really offsite?)

astalavista is still down at the moment; I imagine they’ve scrambled to change all their passwords, shore up their exposure, and see if they can dig up a backup from anywhere.

It makes a pretty remarkable contrast with this recent How I Hacked Hacker News (with arc security advisory) accounting by someone who compromised Paul Graham’s news.ycombinator.com via some pretty painstaking research of system behavior — and then worked with Robert T. Morris (the Robert T. Morris) to get the issue fixed.

I will show you a technique to impose a rate limit (aka API Throttling) on a Ruby Web Service. I will be using Rack middleware so you can use this no matter what Ruby Web Framework you are using, as long as it is Rack-compliant.

Awesome. I can think of so many uses for this basic pattern to replace stuff I usually have to do at the app level (slow) or at the Apache level (difficult to port, prone to decay).

Comments note that Memcache might be a better pick than Redis, which works even better with the setup I have in mind, though Redis sounded fun too.

Part of the joy of this aboriginal approach is that it’s different every time.

A note on the “Do beans belong in chili?” holy war: Personally, I have no particular use for pulses, though sometimes I’ll make a sidecar batch for my fiancee (who is vegetarian) that includes a robust mix of black beans, white beans and kidney beans. She likes it. I make no specific recommendation in this regard and consider this momentous personal decision best resolved via quiet introspection and discreet consultation of sympathetic clergy members or other local community leaders.

Things pictured here:
2 good 12oz beers (extra shown — I was making a second concurrent batch for a buddy)
Several jars of Goya jalapenos
2 cans of Goya Chipotles
Garlic
Onions
Habaneros
Kielbasa
Stewed tomatoes
Beef broth
Chiles
Paprika
Chili powder
Oregano
Ground cumin
Salt
Pepper

Things not pictured here:
Cooking sherry
Brown sugar
Large crockpot

Turn the crockpot on warm and add a couple shots of cooking sherry. Add one of the beers (I like to use Middle Ages’ ImPaled Ale).

Toss in a round of the spices. Kind of go crazy, especially with the chili powder.

Then, brown the meat. Nothing special here. This was about 2.5-3 lbs of stewmeat.

One item of note: I read on some chili recipe thread somewhere that the top 10 finalists of some national chili cook-off contest had only the following thing in common: none of them added anything to the meat during this phase. Do with that intel what you will.

Next, ya cuts ya onions. This is how that’ll look. If you’re like me looking at this picture, you’re wondering how it is I’ve chopped the onions but there’s still a whole one left, conspicuously just within frame. You ask yourself: is it possible this scene has been glitzed up to look more wholesome and productive than it actually probably is? Am I being sold a bill of goods here? Will that poor onion ever get a chance to shine? If that’s what you’re asking yourself, time to wake up. Scientists have long known that onions have only a crude approximation of grief and nothing like what we consider loneliness — e.g., they totally lack a pack instinct.

Incidentally, it always kinda cracks me up how you actually cry when you cut onions. I know it’s scientifically normal, but for some reason I put it in the same class of events as slipping on a banana peel and then shooting down a flight of stairs. Maybe I watched the wrong cartoons as a kid.

Here’s the kielbasa all ready to go.

An etymological note. If you look up the word kielbasa, you’ll find that some people pronounce it differently. Wikipedia considers “kielbasa” from the Polish point of view, which, totally. It mentions that NY residents pronounce it “kielbasi”, which sounds demented to me but I guess that could pass for local color. I had originally read pronouncing it that way was Lithuanian (yes, I’ve looked this up multiple times for some reason), but the wiki article now has that pronunciation as Czech. In any case, I move we deprecate any silly i-at-the-end business; kielbasa has a long and hallowed tradition of being delicious and probably doesn’t appreciate anybody getting cute with it.

If you worry about your arteries, get the low-fat turkey-based stuff. On the other hand, I once found something at Wegman’s called ‘Holiday Kielbasa’, and oh man.

Dice the kielbasa. Well, maybe not dice. Make disks, then cut each disk in 2 or 3 pieces. Think of the kielbasa as the main attraction. Thanks to its spongy nature, it won’t break down much so it’ll be the most recognizable part after many hours in the crockpot. Produce shapes you’ll be happy eating. Somewhere between “don’t really need to chew” and “can’t get it in my mouth”.

Interesting technical note: in the “Who Framed Roger Rabbit?” world of Toonville, all dachshund characters were made of kielbasa, or so I like to think.

Then I like to bake that for 10-15 minutes until it’s somewhat cooked but well short of being actually crispy. Black crispy kielbasa will basically ruin your chili experience. I did it last time.

A note that I’m sure hints at past abuses: see the silver stuff peeking through the kielbasa smithereens? There is basically no reason ever to put a pan in the oven with food on it and the food not sitting on tin foil, and here’s why. You, or whoever has the strongest sword-arm in the village (probably you), is going to have to scrub off whatever is on that pan when it comes out of the oven. It takes two seconds to put tin foil on and is the gift you give your future self by planning ahead. As you can plainly see, I’ve used tinfoil here — of course, because I’m the kind of gangster who don’t stop thinking about tomorrow.

Now, while that’s baking, you can start your onions. Or maybe I just got the pictures out of order here; not sure. In any case, caramelize your onions. This takes like 20 or 30 minutes, even though multiple people I’ve spoken to claim it takes 5. I always quietly wonder if I’m doing it wrong. (Please consider this your reply homework.)

When you take the stewmeat out of what I hope is a nice cast iron pan, don’t go rushing off to put it in the crockpot. Put it in a tupperware thing and stash it in the fridge until later. Why? Because you’re going to cook all this stuff for several to many hours, during which time your stewmeat will fall all the hell apart and sublimate into a gross mealy matter. One day, randomly checking out recipes, I accidentally stumbled onto what braising is, and why you don’t want to braise the living hell out of your stewmeat — and realized that’s what had been going wrong with my stewmeat. Braising is cooking meat in liquid, and it breaks down the connective tissues, which is great for a bit, to make meat tender, and then sucks, as it eventually pulverizes your meat into a grody nothingness. If you get the feeling I’m typing this not so much to educate you as to exercise my self-pleasedness at mastering this hard-won intel, then… well-spotted.

When the kielbasa is done, put it in the crockpot, with another round of the spices. Phase 1 is complete: we have a boring but technically edible collection of objects getting warm in the crockpot.

Chop hell out of the garlic. You want as much surface area as possible. I hate peeling garlic, and I’ve tried every device and method known to man, and I can’t do any better than crushing it beneath the flat of the chef’s knife and then cutting off the little foot. I loathe doing it, which is why you see that shameful “someone with more patience than me chopped this garlic and put it in a jar and I bought it” jar up there. Can’t skimp on the garlic but you also don’t want to be in the situation where you’d rather bite your own face off than make some delicious chili, so…

When the garlic is as tiny as it’ll get, you may want to toss it in with the onions for a bit. I’m not sure how much effect this really has on the end product, but it’s fun and feels like a sophisticated thing to do.

Once onions are limp and translucent, dump them and all garlic, crypto-sauteed or otherwise, into the crockpot.

Let’s have a look at how it’s doing. This is a pretty boring picture. Luckily, this next part is technically dangerous, especially if you have eyeballs.

The habaneros. These are the chief force multiplier in the battle against your own face, with garlic running a respectably distant second. Here, I’ve used six. I think my crockpot is a 6-quart — my mom gave it to me long ago and I’ve casually looked around for a high-tech model but I’ve never found one as big — so maybe one habanero per quart is a decent yardstick if you like hot foods. Ratchet up/down as warranted.

Be warned that habaneros are intensely hot, though. Every so often, I make the chili too hot to eat at normal speed, and I resolve at those times to make it less hot next time, but then the next time I fear, Nikola-Tesla-there-are-feathers-on-my-back-style, that I’ve gotten a fluke batch of weak habaneros (This happened once: I could literally eat the habanero like a bellpepper. It was like I was walking on the moon.) and my chili will be pointless and sad, so it has become the art of almost ruining my own day while just barely not, every time.

In any event, they’re hot enough that you’ll want to wear gloves cutting them, no joke.

In the sink, rip — wait

Seriously, put on some gloves. Wash your gloved hands in between working with the habaneros and touching anything else. Scoville units are fun and delicious but you want to be careful choosing when and how your body ingests them. All it takes is one errant swipe to your eye and *BAM*, you’re busy yelling and/or lavaging for at least the next 10 minutes, when you could be producing delicious chili.

Keep the gloves on during clean-up too. There is only winner in Habaneros vs Your Mucous Membranes, and it’s not the local favorite.

In the sink, rip off the black stem of each pepper (technically, I believe these are termed ‘fruits’), then split the body down the middle and get the webbing and the seeds out. You may want to do this under running water. Then again, it may be that the concussive force of the water is what’s driving all that capsaicin into the air and directly into your unwitting lungs, making you cough like ridiculous. Player’s choice, really.

In any case, definitely get all the seeds out. You do not want to be passing these on down the gastro-intestinal line. Another gift you set aside for your future self to enjoy. I’m reminded of the quote about how the stock market can stay irrational a lot longer than you can stay solvent. In quantity, those seeds will outlast your very best attempts to break them down, and a grim shadow will darken thy threshold, and a doom will be visited upon thee, and there will be much beating of breasts and gnashing of teeth and weeping in the streets that day.

Dice like mad. Again, surface area.

Here, we’re at phase 2. When you dump the habaneros into the crockpot, only then is the battle well and truly joined. Turn the heat up to high. Put on some C&C Music Factory if you like. Life is a party.

Do the same rip/gut deal with the goyas.

And dice. Do you like the way I keep the chef’s knife in the shots, as a consistent yardstick to aid your perspective? It’s a thoughtful and classy touch.

Goyas, incidentally, kind of revolutionized the way I ate for several years. Here’s the jar; if you haven’t had the pleasure, run don’t walk.

So add the goyas, which, yes, are technically ‘Goya Jalapenos’, but that’s just not the way it’s worked out so far.

Toss in the can of green chiles, which, to be honest, I’m not sure what effect those can really have, if any, versus the dominating flavors of everything else. I add them out of a sense of tradition.

Toss in two cans of chipotles, pictured here for your convenience (note that, despite everything you’ve ever heard in pop culture, the T comes before the L. I predict that in 40 years the average English-speaker’s discomfort with this pair of consonants pronounced in that order will have smoothed that rough edge over and it really will be pronounced “chipolte”)…

Also toss in the two cans of stewed tomatoes. I drain them first. One of the complex subplots of this hectic affair is monitoring your liquid levels. You don’t want this all to be too liquidy. I press the water (or whatever it is) out of the onions before I toss those in, too.

Do another round of spices. Do a bunch of salt.

At this point, I’ll bust out the beef broth. I’ve tried a couple different things, including a turkey stock my fiancee made for me last Thanksgiving (finding, sadly, that turkey is too mild a flavor to defeat the various tastes currently in your crockpot), and I think I’ve settled on “Better than Bouillon” Beef Base, which is actually a vegemite-like mealy black paste, which is definitely a phrase that doesn’t go out of its way to reward contemplation. If you can, avoid mixing it into water, because what does water do for you here? Instead, I like to take the juice from the two goya jars (maybe one if I’ve got too much liquid on board already), nuke it for a minute or so, and then mix in a giant teaspoon or two of the beef broth. Toss it into your chili. I like to do A/B tests, i.e. set aside a bit of the chili liquid, add the broth to the main batch, and then compare flavors. The beef broth is crucial.

Lastly, I’ll add a couple large chunks of brown sugar. Sounds wierd, but try it. Once you’re able to pick it out amongst the other flavors, you’ll do backflips. Subtle, smoky-sweet ones though.

Put the lid on that concoction and walk away for as long as you can bear. I know I’ve made a really decent batch when it’s substantially gone by the time it’s done.

Several hours before dinner, toss in the browned stewmeat and let it cook on low. Check back every hour or so. You want the stewmeat tender and delicious, not all grainy and gross. (…which, come to think of it, is a pretty good algorithm for basically everything else, too.)

Final lackluster shot of crockpot full of red-brown semi-liquid matter. This is roughly 450 times better-tasting than it looks. Eat with a nice bread (e.g., a good sourdough) and some sharp cheese and a large glass of milk or other coolant of choice. (As part of this routine, I make sure to have a couple gallons of skim milk on hand. There’s nothing better.)

TODO:

- Experiment with adding corn. (I usually plan to do this “next time” but then balk at the last minute. I expect it’s a pretty substantial departure.)

- Find a way to make cornmeal work more consistently as a thickener. I’ve stopped using it because between the too-strong cornmeal flavor, the occasional graininess, and the alarming efficiency with which one can seriously mess up a nice pot during preparation, it seems a bit uncalled-for.

A final post-implementation note: I think I’m skipping the stewmeat from here on out. The process is kind of annoying, it sucks up all the heat, and the return on investment is sub-optimal.

I work with a ton of stuff that uses underscores, especially SQL, and it’s been driving me crazy that, on its own, my emacs config doesn’t consider the underscore punctuation in all modes, so hitting M-DEL (Alt+Backspace) to delete back one word in sqlplus mode deletes the whole string — underscores and all.

That is, if | is our cursor, and we’re inside emacs at a sqlplus prompt like so…

desc prod.some_long_table_name|

hitting Alt+Backspace once gets you…

desc prod.|

which is annoying, especially because emacs’ autocomplete is so awesomely useful in sqlplus mode. I’d guess most database schemas have lots of tablenames that share prefixes (e.g., user_history, user_bookmarks, user_buddies, etc), which renders that autocomplete somewhat less than effective.

I’d much rather have it so that the cursor stopped at underscores. On successive keypresses, you’d zap back another segment, stopping at the underscore, like so…

desc prod.some_long_table_name|
desc prod.some_long_table_|
desc prod.some_long_|
desc prod.some_|
desc prod.|

This is already the long-established behavior of interfaces that inherit from emacs, like BASH’s emacs mode, and irssi, but is evidently a legacy design decision within Emacs without an obvious config handle, nearly undiscussed as far as I could google…

From a comment in python-mode.el:

;; For historical reasons, underscore is word class instead of
;; symbol class. GNU conventions say it should be symbol class, but
;; there’s a natural conflict between what major mode authors want
;; and what users expect from `forward-word’ and `backward-word’.
;; Guido and I have hashed this out and have decided to keep
;; underscore in word class. If you’re tempted to change it, try
;; binding M-f and M-b to py-forward-into-nomenclature and
;; py-backward-into-nomenclature instead. This doesn’t help in all
;; situations where you’d want the different behavior
;; (e.g. backward-kill-word).

Luckily, TFM is rather nice.

The short answer is: one needs to specify the underscore character as a member of emacs’ punctuation class…

(modify-syntax-entry ?_ "_")

That will only work for text-mode, and gets overwritten on a major-mode switch by any new syntax table specified, so the following hook reference is necessary for this change to be global for all major modes…

(defun change-major-mode-hook ()
(modify-syntax-entry ?_ "_"))

Folks who aren’t emacs newbs might be aware of further subtleties, but this seems to produce exactly what I want — autocomplete and word navigation in every mode that’s identical to the other command-line interfaces I use.