<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pitfalls on pavsaund.com</title><link>https://www.pavsaund.com/tags/pitfalls/</link><description>Recent content in Pitfalls on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 23 Feb 2016 08:30:02 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/pitfalls/index.xml" rel="self" type="application/rss+xml"/><item><title>Pitfalls of writing software alone</title><link>https://www.pavsaund.com/2016/02/23/pitfalls-of-writing-software-alone/</link><pubDate>Tue, 23 Feb 2016 08:30:02 +0000</pubDate><guid>https://www.pavsaund.com/2016/02/23/pitfalls-of-writing-software-alone/</guid><description>I&amp;rsquo;ve published a new story on the Coding with Empathy blog. Here&amp;rsquo;s an intro. The power of one There&amp;rsquo;s nothing like being able to work on a project by yourself and having complete control of every single aspect of the solution. Everything from the front-end stack to the storage. Using the latest and greatest frameworks and libraries. This is heaven for any software developer. But regardless of any of the above technology-focused aspects, there is one major advantage being that single developer, namely: speed!</description></item></channel></rss>