I have been reading some of Brandon Sanderson‘s works. Also, I have been listening to them, since I have the audiobooks as well as the actual texts. It has proved to be a fresh pleasure. I had thought that Martin’s A Song of Ice and Fire was going to be a rare gem, not to be ever rivaled in its time. I was mistaken.
The Cosmere, the artificial world weaved together through a complex web of unparalleled story-telling throughout Sanderson’s numerous and voluminous works, is staggering in its intricacy. It is so vast and delicate, in fact, that a whole community of fans have trouble keeping up with it. They have set up this awesome encyclopedia of his works and their relations, the Coppermind (the name is a Cosmere reference). The stories, and the series are, while pleasurable reading as standalone works, are so greatly fitted together that the seams seem inexplicably hidden.
The character of Hoid, the mysterious man appearing in nearly every novel, is my personal favorite piece of ingenuity.
I recommend the books in the Mistborn series, the Stormlight Archive (though still incomplete), and the Elantris series (also incomplete) to all the people who enjoy a masterfully crafted puzzle and a good fantasy read.
This week, I started some rather serious work on buffing up my metaphorical know-how muscles. So, I started reading “Pro Spring 3”.
However, since just reading isn’t enough, I also have started to walk through the beautiful codes written by Rod Johnson and Juergen Hoeller.
I began my way where most applications using Spring begin theirs: the ApplicationContext. It is a long, long journey, and I know that I won’t be done anytime soon. However, wish me luck
Gradle, is another build automation tool I’ve been introduced to by colleagues and friends. For those who are not familiar with it, Gradle (with words taken from the official site) is:
Gradle is build automation evolved. Gradle can automate the building, testing, publishing, deployment and more of software packages or other types of projects such as generated static websites, generated documentation or indeed anything else.
Right now, I’m reading the book “Building and Testing with Gradle” which is available online for free as a registered-access content. It is a good book, and I intend to finish it soon, so that I can get to actual programming and building projects using it.
Currently, the struggle for me is to not get confused by the Groovy syntax. However, I think I’m getting the hang of it.
I will probably be posting a short introduction soon, if I find such a thing necessary.
About two weeks ago, I finally got my hands on an original version of the latest edition of the CLRS book. Most significantly, the pseudo-code convention has changed to be a little more like modern, object-oriented languages (e.g. Java, C#, etc.).
For example, to access a property of an object, instead of property[object] (which was the notation used by the 2nd edition) we will write object.property.
Also, there are many places that the whole text has been rewritten. All in all, it was a very good buy. My only regret is that from now on my “CLRS at a glance” articles won’t be compatible with my earlier notes.
(Cover picture courtesy of Amazon)