That doesn't always work, and is still quite dangerous in the (abstract), usually your other programmers are friendly, but you should definitely be careful about it.
I've played around with vimscript and my .vimrc many many times, and always found it very unwieldy. I've started using a new and very different approach, which involves using the amoffat/snake library to write my new .vimrc functions in python. This is definitely not for everyone, but I've been able to do some pretty cool stuff with it, like creating a function for writing trace like debug statements, or sending the currently selected vim lines to a shell via the window manager/os level, rather than a terminal multiplexer like screen. If anyone else is interested, an example can be found at gist.github.com/sac2171/ce7b086421e8387193fd
That was one of the best articles I've read in a while. While I think the article could have had a better title, and it doesn't dispose any 'useful' information, it is incredibly well written, and interesting.
Being young, I stumbled on PK Ware once while doing a task for a job. I started inquiring about their service, and was slightly rude to a rep. The conversation went something like...
Me: Why would I pay 40 dollars for zipping software I get for free? You guys are totally late to the game, winzip and winrar already exist.
Rep: ....... Yea, we started the industry, and our founder died from alcohol abuse...
A lot of people are mentioning the idea that this should actually be a continuous curve... As someone who has used the cafeteria for a couple months, I would say this is most likely an over optimization. You are creating a complication for every transaction, and making it so now there is now set points where you can save the most money, namely at the beginning/end of the window. Which actually creates more of the two 'two hump system' swombat, saalweachter, smickie and others have mentioned. Just like there is a natural gradient to lunch from 12 to 1, you still get a gradient in the discounted hours. 11:30 isn't a better time to eat lunch then 11:55, It's simply an attempt to split up lunch times so that the cafeteria can effectively have 3 rush hour instead of 1. And since traffic effects aren't linear, you get a much quicker overall experience as a result. "The people standing around" is overplayed, Those are the people's elevator rides who were are little shorter/longer than expected.
Slightly silly question, but can anyone tell me what font he uses on the first couple of code screenshots? Something about them look astoundingly clear, and I can't figure out what it is about them.