<?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>Modas Pasajeras on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/modas-pasajeras/</link><description>Recent content in Modas Pasajeras on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Fri, 25 Nov 2016 20:29:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/modas-pasajeras/index.xml" rel="self" type="application/rss+xml"/><item><title>Hype Driven Development</title><link>http://karpoke.ignaciocano.com/2016/11/25/hype-driven-development/</link><pubDate>Fri, 25 Nov 2016 20:29:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/11/25/hype-driven-development/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Software development teams often make decisions about software architecture
or technological stack based on inaccurate opinions, social media, and in
general on what is considered to be “hot”, rather than solid research and
any serious consideration of expected impact on their projects. I call this
trend Hype Driven Development, perceive it harmful and advocate for a more
professional approach I call “Solid Software Engineering”. Learn more about
how it works and find out what you can do instead.&lt;/p&gt;</description></item></channel></rss>