A fitting end for the Fitz and the Fool storyline. I still think the orginal trilogy was one of the best fantasy books ever written and it was nice to read the 'conclusion'
The followup (i guess it can be called that ) to Broken Empire . Different main character, different "quest" but the madness is still there. While i didn't enjoyed Red Queen's War as much as Broken Empire (different strokes for different folks i believe ) it is still a good and enjoyable (you can read it independently of the Broken Empire but you'll miss some jokes/callbacks) series.
Bring them on , Mark Lawrence.
The first tip is about upgrading your powershell help files so it will be up to date. For this just run :
Second tip is about searching for useful cmdlets when trying to achieve something with powershell. For instance if you are interesting in looking at the event viewer entries (for instance), you can run :
and get back all the cmdlets that let you interact with the event viewer.
The golem and the jinni
Very nice, very different from the "typical" fantasy novel. The genie in the past bits were the best, i'd gladly read a full novel with those parts.
The Night Angel trilogy
It's enjoyable. A much more "typical" fantasy series with good world building and character development.Most of it presented from a stealth assassin perspective. Towards the end , the narrative kind of stumbles a bit , but overall a enjoyable read.
First 2 are the last books from the Companions Codex trilogy while the last if first book from new Homecoming trilogy.
First 2 books are fine, they reminded me of the old school Drizzt stories, even the cast of characters are very.....familiar. The last one is pretty bad though. The entire books is used as a setup for the cooler things to happen next.
It's a simple equation with 3 variables : time (and implicit money), set of features/bugs ratio and code quality. For best results the trick is not to overemphasize one over the remaining 2 and just keep all 3 balanced. Sounds simple but sometimes it feels like the hardest thing in the world.
Non functional requirements are just as important as functional ones. Yet not much thought is given to them (especially at the beginning when writing the specs for a new "system"). For instance everyone, obviously, wants a secure application (also security is a bool, it's either secure or not, there are no intermediary steps) so a new application will not be released if it's insecure no matter how many functional requirements are implemented.
The idea is to always keep in mind non functional requirements when designing a new "system". Some of the non functional requirements (like capacity/performance or security) can even have a direct impact over the functional requirements.