Skip to main content

The Song Of Ice And Fire: An Empirical Gudie To Survival of the Game of Thrones.

In no particular order:

You can safely skip the detailed description of the food being served. It rarely has anything to do with the way people consuming the food will die. Besides, there are only two cuisines in Westeros: Northern, where everything is glazed with, braised with, or dipped in honey, and Southern, which is a hot snake stew. The rest of the world eats horse and puppies on a stick.

You don't have to try to memorize ancestral lineage of every character in the books. Most of them will die soon enough, and the rest will talk about their fathers, grandfathers, and grand grandfathers endlessly, so you will learn anyway.

Regardless of how carefully and meticulously somebody plans something, that something will never come through. Once you embrace this simple concept, you will save yourself a lot of disappointment, because everything always goes terribly wrong. Strangely enough, all that does happen is commonly a result of an elaborate plan of some shadowy character, of whom we know very little and whose intentions are unclear. They evidently know how to plan for success.

If you feel that a character is growing on you, it is best to be ready to part with him or her and prepare yourself for his or her demise. Then consider each new chapter with that character to be a nice surprise. I have to admit, though, that character's lifespan seems to be directly proportional to the complexity of the one's persona, and disposition to intense inner conflict. Simpler people seem to expire much faster, deeply tormented souls tend to linger awhile.

If a character of any significance is said or believed to be dead, it's a sure sign that he or she is not. Even if you read the whole chapter about it, it might still not be true. And even if it is, some might come back from the dead.

And finally, like with all of those epics, there is always another book coming.

Or two...

Popular posts from this blog

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic...

How to Make a Website Everyone Has