Like redis cluster, we'll use a shard space of 2^14 = 16384. Essentially what this means is that we'll take our entire geo area, and split it into 16384 segments of approximately equal entries.
Each instance will be responsible for any number of segments, typically a cluster of segments that are geographically close.
| import array | |
| import collections | |
| import itertools | |
| # Placeholder constants | |
| FREE = -1 | |
| DUMMY = -2 | |
| class Dict(collections.MutableMapping): | |
| 'Space efficient dictionary with fast iteration and cheap resizes.' |
| Lisp interpreter in 90 lines of C++ | |
| I've enjoyed reading Peter Norvig's recent articles on Lisp. He implements a Scheme interpreter in 90 lines of Python in the first, and develops it further in the second. | |
| Just for fun I wondered if I could write one in C++. My goals would be | |
| 1. A Lisp interpreter that would complete Peter's Lis.py test cases correctly... | |
| 2. ...in no more than 90 lines of C++. | |
| Although I've been thinking about this for a few weeks, as I write this I have not written a line of the code. I'm pretty sure I will achieve 1, and 2 will be... a piece of cake! |
| """ | |
| Single Responsibility Principle | |
| “…You had one job” — Loki to Skurge in Thor: Ragnarok | |
| A class should have only one job. | |
| If a class has more than one responsibility, it becomes coupled. | |
| A change to one responsibility results to modification of the other responsibility. | |
| """ | |
| class Animal: | |
| def __init__(self, name: str): |
I have a pet project I work on, every now and then. CNoEvil.
The concept is simple enough.
What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?
• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.
More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).
Interview is all about taking an ambiguous question of how you might build a system and letting
| Some useful Python one-liners taken from http://www.reddit.com/r/Python/comments/fofan/suggestion_for_a_python_blogger_figure_out_what/ | |
| All modules listed are part of the standard library and should work with Python 2.6+ | |
| How to use: | |
| $ python -m [module] [arguments] | |
| calendar - does default to displaying a yearly calendar, but it has a bunch of options (args are year or year month, options are HTML output, calendar locale, encoding, and some type-specific stuff, see python -m calendar -h) | |
| cgi, dumps a bunch of information as HTML to stdout |
The following attack will display a "you've been signed out" page for GMail, and attempt to steal your account credentials.
DO NOT PUT ANY ACCOUNT CREDENTIALS INTO ANY TABS CREATED AFTER VISITING THESE LINKS :)
I received an email in my GMail inbox with a fake attachment image, styled to look like the real GMail attachment UI:
This linked to a page that ended up displaying a fake "you've been signed out" link, via the data:text/html... URL feature of Chrome:
| ;; magit stuff!! | |
| (magit-file-header ((t (:foreground "violet")))) | |
| (magit-hunk-header ((t (:foreground "blue")))) | |
| (magit-header ((t (:foreground "cyan")))) | |
| (magit-tag-label ((t (:background "blue" :foreground "orange")))) | |
| (magit-diff-add ((t (:foreground "MediumSlateBlue")))) | |
| (magit-diff-del ((t (:foreground "maroon")))) | |
| (magit-item-highlight ((t (:background "#000012")))) |
| #!/bin/bash | |
| # @link https://gist.github.com/mattscilipoti/8424018 | |
| # | |
| # Called by "git push" after it has checked the remote status, | |
| # but before anything has been pushed. | |
| # | |
| # If this script exits with a non-zero status nothing will be pushed. | |
| # | |
| # Steps to install, from the root directory of your repo... |
