Skip to main content

The Daylight War by Peter V. Brett

Third part of the "Demon Cycle". See review of second part "The Desert Spear".

I was into the story after the second book so second and thirds are hard for me to distinguish unfortunately. This has additional consequence of remembering exactly what happened in second book.
In second book it was great to see the story from the beginning as I needed to learn about world again. I would like third book more if I would make bigger gap before third as well.
Additionally to main story we get to know background of other people. I feel that it was shorter than in second book but it was too much for me. Don't get me wrong, it was still fun to read but I found myself looking at it as obstacle to knowing main story more often.

Book is really good and of course all of you who liked previous parts are going to read it so I'm not saying anything more.

Rating: 7/10


Popular posts from this blog

How to simulate slow connection (developer proxy in Node.js)

Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy.

Toggle device modeChoose Network type.Refresh the page 


For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me.

I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one.

With this module I can write really short code to create slow server:

var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host: 'localhost', port: 8080, …

How to use NPM packages from private repositories on bitbucket

Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public but still want to have an ability to install them easily.

After googling and experimenting I have found simple solution.
First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important.

Change example from below to:
user - username
PASS - password of the user
organization - owner of the project (you can find it in bitbucket url to your project)
project - your project name