<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Builder on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/builder/</link>
    <description>Recent content in Builder on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 22:25:45 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/builder/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Builder Design Pattern</title>
      <link>https://www.bradcypert.com/design-patterns-builder/</link>
      <pubDate>Tue, 24 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/design-patterns-builder/</guid>
      <description>&lt;p&gt;Welcome back. I’m writing today to talk about something that I think is pretty cool — design patterns in code! Specifically, we’re going to cover the builder pattern, which I find myself using all the time when writing Android applications and sometimes when writing plain Java applications. Let’s setup a scenario: You have a class that has a constructor. You call it a &lt;code&gt;User&lt;/code&gt; class. The constructor for this class takes in a &lt;code&gt;String firstName&lt;/code&gt; and a &lt;code&gt;String lastName&lt;/code&gt;. You write some awesome logic in this class and use it everywhere. You new it up all over your codebase because it’s just &lt;strong&gt;that&lt;/strong&gt; good. You kick back and enjoy the good life, until you have another developer walk over to you and say &lt;em&gt;“Oh, hey. We need to add email address to the user class. And we’ll probably want to add phone number and mailing address, too.”&lt;/em&gt; Crap.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
