<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://blog.hindsightmetrics.com/</id><title>Hindsight Metrics</title><subtitle>A minimal, responsive and feature-rich Jekyll theme for technical writing.</subtitle> <updated>2026-04-26T23:06:26-07:00</updated> <author> <name>Fausto Ruvalcaba</name> <uri>https://blog.hindsightmetrics.com/</uri> </author><link rel="self" type="application/atom+xml" href="https://blog.hindsightmetrics.com/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://blog.hindsightmetrics.com/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Fausto Ruvalcaba </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Why KISS is sometimes better than DRY</title><link href="https://blog.hindsightmetrics.com/posts/why-kiss-is-sometimes-better-than-dry/" rel="alternate" type="text/html" title="Why KISS is sometimes better than DRY" /><published>2026-04-25T12:00:00-07:00</published> <updated>2026-04-25T12:00:00-07:00</updated> <id>https://blog.hindsightmetrics.com/posts/why-kiss-is-sometimes-better-than-dry/</id> <content type="text/html" src="https://blog.hindsightmetrics.com/posts/why-kiss-is-sometimes-better-than-dry/" /> <author> <name>Fausto Ruvalcaba</name> </author> <category term="Software Engineering" /> <category term="Design Patterns" /> <summary>Introduction I recently worked on a project where the concepts of Don’t Repeat Yourself clashes with Keep It Simple, Stupid. Don’t repeat yourself The goal of this principle is to not duplicate code. By doing so we have more control of where code is and make it so a fix or an update is automatically applied to wherever it is consumed. This is usually accomplished by inheritance and abstracti...</summary> </entry> <entry><title>How does software get complicated?</title><link href="https://blog.hindsightmetrics.com/posts/how-does-software-get-complicated/" rel="alternate" type="text/html" title="How does software get complicated?" /><published>2026-04-25T12:00:00-07:00</published> <updated>2026-04-26T08:18:22-07:00</updated> <id>https://blog.hindsightmetrics.com/posts/how-does-software-get-complicated/</id> <content type="text/html" src="https://blog.hindsightmetrics.com/posts/how-does-software-get-complicated/" /> <author> <name>Fausto Ruvalcaba</name> </author> <category term="Software Development" /> <category term="Performance" /> <summary>Introduction This is pretty obvious, but as a software solution grows the more complicated the code becomes. This is due to having different requirements for the system, business models, multiple access points, data stores, etc. I want to go over a very simple example of how a Circle class can go from very basic to a more complicated one in the name of performance Evolution of a Circle class...</summary> </entry> <entry><title>Solving Problems with Code?</title><link href="https://blog.hindsightmetrics.com/posts/solving-problems-with-code/" rel="alternate" type="text/html" title="Solving Problems with Code?" /><published>2026-04-13T12:00:00-07:00</published> <updated>2026-04-13T12:00:00-07:00</updated> <id>https://blog.hindsightmetrics.com/posts/solving-problems-with-code/</id> <content type="text/html" src="https://blog.hindsightmetrics.com/posts/solving-problems-with-code/" /> <author> <name>Fausto Ruvalcaba</name> </author> <category term="Software Engineering" /> <summary>As a Software Engineer, my instinct is to solve problems with writing code. Obviously, that’s the “software” part, but lately I’ve been thinking about the “engineer” part derived from the Latin word “ingenium” which means cleverness or ingenuity. This came to mind recently with the Sleeper API, the best app for Fantasy Sports: Initially, I wanted to develop a console app (or a private API)...</summary> </entry> <entry><title>Forming Storming Norming Performing</title><link href="https://blog.hindsightmetrics.com/posts/forming-storming-norming-performing/" rel="alternate" type="text/html" title="Forming Storming Norming Performing" /><published>2026-03-08T12:00:00-07:00</published> <updated>2026-03-08T12:00:00-07:00</updated> <id>https://blog.hindsightmetrics.com/posts/forming-storming-norming-performing/</id> <content type="text/html" src="https://blog.hindsightmetrics.com/posts/forming-storming-norming-performing/" /> <author> <name>Fausto Ruvalcaba</name> </author> <category term="Software Engineering" /> <summary>Introduction The title of this blog refers to what a newly formed team goes through. Each word represents a stage that the members go through, as they get to know and work with each other. Below I’ll describe what happens at each stage, and how each one is important for a successful team. It’s important to note that each team member has a different way of understanding things, we all create me...</summary> </entry> <entry><title>Imposter Syndrome and How I've Handled It</title><link href="https://blog.hindsightmetrics.com/posts/imporstor-syndrome-and-how-i-have-handled-it/" rel="alternate" type="text/html" title="Imposter Syndrome and How I&amp;apos;ve Handled It" /><published>2026-03-08T12:00:00-07:00</published> <updated>2026-03-08T12:00:00-07:00</updated> <id>https://blog.hindsightmetrics.com/posts/imporstor-syndrome-and-how-i-have-handled-it/</id> <content type="text/html" src="https://blog.hindsightmetrics.com/posts/imporstor-syndrome-and-how-i-have-handled-it/" /> <author> <name>Fausto Ruvalcaba</name> </author> <category term="Software Engineering" /> <summary>Introduction For those who don’t know, Impostor Syndrome is the persistent feeling that your success is undeserved, that your accomplishments are due to luck rather than skill or effort. Even those with significant achievements often feel they don’t truly belong. There are many causes for this, external or internal high expectations, comparison with other seemingly successful people in the sa...</summary> </entry> </feed>
