<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Learning on miqu.me</title><link>https://miqu.me/blog/categories/learning/</link><description>Recent content in Learning on miqu.me</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 28 Jan 2018 19:06:09 +0000</lastBuildDate><atom:link href="https://miqu.me/blog/categories/learning/index.xml" rel="self" type="application/rss+xml"/><item><title>My top 5 must-have technical books</title><link>https://miqu.me/blog/2018/01/28/top-5-must-have-technical-books/</link><pubDate>Sun, 28 Jan 2018 19:06:09 +0000</pubDate><guid>https://miqu.me/blog/2018/01/28/top-5-must-have-technical-books/</guid><description>&lt;p&gt;Quite recently a team member wanted to suggest interesting technical books to read for a junior engineer. I figured I might as well write my top 5
books here, in no particular order. I believe every Software Engineer should own these books, but reading them is a very good start ;)&lt;/p&gt;</description></item><item><title>Continuously improving with your tools</title><link>https://miqu.me/blog/2014/10/18/continously-improving-with-your-tools/</link><pubDate>Sat, 18 Oct 2014 13:17:49 +0100</pubDate><guid>https://miqu.me/blog/2014/10/18/continously-improving-with-your-tools/</guid><description>&lt;p&gt;Have you ever setup your tools in half an hour? In my opinion, the key to improving your tools is gradually evolving what you use, and how you use them. Here’s what I think about it.&lt;/p&gt;</description></item></channel></rss>