<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Books on Giedrius Statkevičius</title><link>https://giedrius.blog/categories/books/</link><description>Recent content in Books on Giedrius Statkevičius</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 23 May 2022 14:39:43 +0000</lastBuildDate><atom:link href="https://giedrius.blog/categories/books/feed.xml" rel="self" type="application/rss+xml"/><item><title>"Observability Engineering" Book Review</title><link>https://giedrius.blog/2022/05/23/observability-engineering-book-review/</link><pubDate>Mon, 23 May 2022 14:39:43 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=981</guid><description>&lt;p&gt;A great, new book &amp;ldquo;&lt;a href="https://www.amazon.co.uk/Observability-Engineering-Charity-Majors-ebook/dp/B09ZQ6FHTT"&gt;Observability Engineering&lt;/a&gt;&amp;rdquo; came out very recently and I had to jump on reading it. Since it is very closely related to my work, I devoured the pages and read the book in about a day (505 pages). While doing so I wrote down some thoughts that I want to share with you today. They might or might not be true, I am only speaking about the book from my own perspective. Feel free to share your own thoughts!&lt;/p&gt;</description></item><item><title>Designing API Like It Is An Everyday Thing</title><link>https://giedrius.blog/2019/07/18/designing-api-like-it-is-an-everyday-thing/</link><pubDate>Thu, 18 Jul 2019 21:35:39 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=499</guid><description>&lt;p&gt;Recently I have read a quite popular book called &amp;ldquo;The Design of Everyday Things&amp;rdquo;. I feel that with software slowly taking over more and more parts of the world, we could say that it also became an everyday thing and that we should design it like that. This blog post will be about it.&lt;/p&gt;
&lt;p&gt;There are certain, general design principles that were explained in that book which we should apply to the process of programming in general.&lt;/p&gt;</description></item><item><title>2018 in books</title><link>https://giedrius.blog/2018/12/23/2018-in-books/</link><pubDate>Sun, 23 Dec 2018 10:05:30 +0000</pubDate><guid isPermaLink="false">https://giedrius.blog/?p=332</guid><description>&lt;h1 id="intro"&gt;Intro&lt;/h1&gt;
&lt;p&gt;2018 is coming to a close and so I thought that it would be a good idea to again look back on the books that I have read in 2018 and to share what books I have liked the most with my readers. I will mark the most liked books in &lt;strong&gt;bold&lt;/strong&gt; like Aaron Swartz did in his lists. Also, I will expand a bit under the books which I liked the most and which are kind of controversial.&lt;/p&gt;</description></item><item><title>10 nuggets of knowledge that I picked up from "Code Complete"</title><link>https://giedrius.blog/2018/04/27/10-nuggets-of-knowledge-that-i-picked-up-from-code-complete/</link><pubDate>Fri, 27 Apr 2018 22:15:59 +0000</pubDate><guid isPermaLink="false">http://giedrius.blog/?p=181</guid><description>&lt;figure&gt;
&lt;img loading="lazy" src="https://giedrius.blog/wp-content/uploads/2018/04/5781724216906946015.jpg" width="338"/&gt;
&lt;/figure&gt;
&lt;p&gt;You could probably find &amp;ldquo;Code Complete&amp;rdquo; by Steve McConnell in any of the top 10 lists of books recommended to read for all programmers. I recently finished reading that book too. I have to confess that at times the tips and knowledge in there was a bit too basic and fundamental but, on the other hand, I also think that it has a lot of golden nuggets of knowledge.&lt;/p&gt;
&lt;p&gt;While reading it, I was writing down notes after every section. Essentially, they were three/four ideas that I thought were the most important in each section. Sometimes, they were paraphrased from the conclusions of each section written by the author himself. In other cases, I summarised them myself, in my own words.&lt;/p&gt;</description></item><item><title>Review of Dale Carnegie's "How to Win Friends and Influence People" for programmers</title><link>https://giedrius.blog/2017/10/25/review-dale-carnegie-how-to-win-friends-and-influence-people-for-programmers/</link><pubDate>Wed, 25 Oct 2017 07:56:22 +0000</pubDate><guid isPermaLink="false">http://giedrius.blog/?p=56</guid><description>&lt;p&gt;&lt;img loading="lazy" src="https://giedrius.blog/wp-content/uploads/2017/10/how-to-win-friends-and-influence-people.jpg"&gt;Programmers and IT people are often shunned for being shy, timid, fearful, or just in general - we are being thought of someone who have no social (soft) skills. If you can in any way identify with this sentiment - you definitely would be rewarded deeply for reading this book and implementing the suggested tips in your own life. But let us start at the beginning - who is the author, who is he known for, and so on, and then I will tell you why you should deliciously digest this book.&lt;/p&gt;</description></item><item><title>On Trustworthiness of Sources While Gathering Information About Software</title><link>https://giedrius.blog/2017/08/27/on-trustworthiness-of-sources-while-gathering-information-about-software/</link><pubDate>Sun, 27 Aug 2017 16:34:17 +0000</pubDate><guid isPermaLink="false">http://giedrius.blog/?p=25</guid><description>&lt;p&gt;&lt;img alt="Read the fine manual" loading="lazy" src="https://giedrius.blog/wp-content/uploads/2017/08/rtfm.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Time and time I see people who follow all these random online tutorials and then when something does not work they become dazed and confused. “Why this does not work? But this tutorial shows that it should work” – I see similar questions occasionally in various forms on forums and IRC. I think people do not realize that there is some kind of hierarchy of trustworthiness of information sources. We should be conscious of that hierarchy when looking for information and remember it when we notice that something is not correct or up-to-date.&lt;/p&gt;</description></item><item><title>Why You Should Read Programming Books</title><link>https://giedrius.blog/2017/08/16/why-you-should-read-programming-books/</link><pubDate>Wed, 16 Aug 2017 05:31:17 +0000</pubDate><guid isPermaLink="false">http://giedrius.blog/?p=13</guid><description>&lt;p&gt;Nowadays it seems like we are on an information highway and it is very hard to keep up with all the knowledge. Especially this is acute when considering how many websites there are on the Internet and how long it would take you to read and understand them all. However, there is a solution – books offer a way to get condensed information from the field experts and learn a lot of things. Many people think that this is only true for other fields except programming. But I think that is false. In software development, a lot of things are timeless as well and they do not change so often. Let me present this and other arguments in more detail, and try to convince you to pick up a programming book and read it.&lt;/p&gt;</description></item></channel></rss>