<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Debt on pavsaund.com</title><link>https://www.pavsaund.com/tags/technical-debt/</link><description>Recent content in Technical Debt on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 07 Oct 2021 20:32:48 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/technical-debt/index.xml" rel="self" type="application/rss+xml"/><item><title>Building resilient frontend architecture</title><link>https://www.pavsaund.com/post/2021-10-07-building-resilient-frontend-architecture/</link><pubDate>Thu, 07 Oct 2021 20:32:48 +0000</pubDate><guid>https://www.pavsaund.com/post/2021-10-07-building-resilient-frontend-architecture/</guid><description>Notes on the talk on Building Resilient Frontend Architecture by Monica Lent.
In this wonderful talk, Monica cuts to the heart of core aspects of rewriting code and presents 3 strategies to increase the resiliency of frontend architecture.
Why do we usually rewrite code? Inexperience, it&amp;rsquo;s fun, better solution available and (the big one 🥁) Technical debt 🎉.
Monica&amp;rsquo;s definition of Technical debt:
Code that negatively and repeatedly affects the speed or quality of delivery.</description></item><item><title>The boy scout rule</title><link>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</link><pubDate>Sun, 26 Oct 2014 18:00:21 +0000</pubDate><guid>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</guid><description>&lt;p&gt;Recently I had the discussion with a colleague on how new code was being added to a code-base without maintainability in mind. The discussion was sparked by a code-review that had been ping-ponging between the reviewer and the developer where readability and ( as a result ) maintainability was an issue.&lt;/p&gt;</description></item></channel></rss>