<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on miqu.me</title><link>https://miqu.me/blog/categories/productivity/</link><description>Recent content in Productivity on miqu.me</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Nov 2015 22:19:24 +0000</lastBuildDate><atom:link href="https://miqu.me/blog/categories/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Three months with XVim</title><link>https://miqu.me/blog/2015/11/19/three-months-with-xvim/</link><pubDate>Thu, 19 Nov 2015 22:19:24 +0000</pubDate><guid>https://miqu.me/blog/2015/11/19/three-months-with-xvim/</guid><description>&lt;p&gt;&amp;lsquo;Know your key shortcuts&amp;rsquo; is the mantra of the productive programmer. I&amp;rsquo;ve chosen to try using the same keybindings everywhere, investing time and learning Vim. And using &lt;a href="https://github.com/XVimProject/XVim"&gt;xvim&lt;/a&gt; in Xcode. In this article I&amp;rsquo;m going to try to explain why I did this, and I&amp;rsquo;ll share my experience of the process.&lt;/p&gt;</description></item><item><title>Jumping into existing codebases</title><link>https://miqu.me/blog/2015/11/15/jumping-into-existing-codebases/</link><pubDate>Sun, 15 Nov 2015 18:55:18 +0000</pubDate><guid>https://miqu.me/blog/2015/11/15/jumping-into-existing-codebases/</guid><description>&lt;p&gt;I’ve recently changed workplace - &lt;a href="https://peak.net"&gt;we’re hiring!&lt;/a&gt; - and I’ve jumped into an existing codebase. This is a good time to review what I like to do when I start to work on a project in these circumstances.&lt;/p&gt;</description></item><item><title>Code injection: Continued</title><link>https://miqu.me/blog/2015/01/29/code-injection-continued/</link><pubDate>Thu, 29 Jan 2015 17:33:30 +0000</pubDate><guid>https://miqu.me/blog/2015/01/29/code-injection-continued/</guid><description>&lt;p&gt;I&amp;rsquo;ve recently done a short talk &lt;a href="https://badoo.com"&gt;@Badoo&lt;/a&gt; about code injection. Summarized and gave a demo of my previous &lt;a href="https://miqu.me/blog/2014/11/23/ios-code-injection/"&gt;blog post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=VEardIxgZNE&amp;amp;feature=youtu.be"&gt;Check it out&lt;/a&gt; if you are interested. Feedback on the talk is more than welcome, &lt;a href="https://twitter.com/miguelquinon"&gt;contact me&lt;/a&gt;&lt;/p&gt;</description></item><item><title>iOS Code Injection</title><link>https://miqu.me/blog/2014/11/23/ios-code-injection/</link><pubDate>Sun, 23 Nov 2014 12:21:36 +0000</pubDate><guid>https://miqu.me/blog/2014/11/23/ios-code-injection/</guid><description>&lt;p&gt;Write code, compile, &lt;strong&gt;wait&lt;/strong&gt;, navigate to screen in application. Fix problem, recompile &lt;strong&gt;wait&lt;/strong&gt;. Oh it was not fixed, start again&amp;hellip; Does it sound familiar? For compiled languages there seems to be no workaround this bottleneck. Even though this is true, there are situations where we can reduce the waiting time, increasing our productivity and happiness. Enter code injection.
&lt;br/&gt;&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>