Skip to main content

The Killing: best TV series ever

By
Well, I watched all famous TV series like Lost, Prison Break, Homeland, Misfits, Luther, Flash Forward or Dexter. I even watched probably best feat called Breaking Bad so far. I have to say that The Killing seems to be best of all after I watched all 2x13 parts. I deliberately waited five days with final rating after the final episode.

The simple story about murdered young girl called Rosie exceeds into political drama regarding major elections. There is ton of unsual twists (greetings to It Crowds :-). Just right amount information about main characters, nice camera and many thrilling moments using exciting ends in some episodes. And significant point which many TV series was not able to handle: it's short enough as it should be, no useless lenghtening - the worst problem we could see in Lost.

Also see interesting things [in czech].


Labels:

Comments

Post a Comment

Popular posts from this blog

ETCD: POST vs. PUT understanding

By
ETCD is distributed key value store used as a core component in CoreOS . I've already send a post earlier this week. Here is a page describing how to use ETCD basic commands = ETCD API. Code snippets placed in a page mostly use put , but ETCD allows to use post as well.  Most of us understand differences between those two commands in a notion of a REST(ful) service, but how does it work in key value store? POST Example over many words. curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" Two same command result into following content: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 { "action" : "get" , "node" : { "key" : "/test" , "dir" : true , "nodes" : [ { "key" : "/test/194" , "value" : &
2 comments
Read more

NHibernate performance issues #3: slow inserts (stateless session)

By
The whole series of NHibernate performance issues isn't about simple use-cases. If you develop small app, such as simple website, you don't need to care about performance. But if you design and develop huge application and once you have decided to use NHibernate you'll solve various sort of issue. For today the use-case is obvious: how to insert many entities into the database as fast as possible? Why I'm taking about previous stuff? The are a lot of articles how the original NHibernate's purpose isn't to support batch operations , like inserts. Once you have decided to NHibernate, you have to solve this issue. Slow insertion The basic way how to insert mapped entity into database is: SessionFactory.GetCurrentSession().Save(object); But what happen when I try to insert many entities? Lets say, I want to persist 1000 libraries each library has 100 books = 100k of books each book has 5 rentals - there are 500k of rentals  It's really slow! The inser
8 comments
Read more