Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

Making Due

Posted on December 22, 2010February 9, 2011 by slowder

Over the course of my career, I’ve been asked to build something that has already been built. I always point out that the task being assigned has already been built, and point to the solution that already exists. There are several reasons why I don’t like building something that someone else has already built.  Those reasons usually come down to, it will save money, it will save time, both,  or it’s been done as well as it can be done.

It’ll save us money to buy it.

Almost any issue you can have with SQL, someone else has faced it before.  If you’re lucky, they shared that solution with the rest of the SQL community.  If enough people have faced that problem,  several solutions will be released.  When you have several solutions released, capitalism sets in.  Market forces start acting on the prices. And prices start falling.

When the market pushes the solution to a price that is lower than my charge rate, it’s simply cheaper to buy the existing solution.  I honestly feel that I have to be fair with those companies that choose to employ me.  If I’m fair with them, they’ll be fair with me.  If I know about a product that can do what I’ve been asked to do, It’s my responsibility to give the company the option to purchase the solution, rather than billing them for my time to reproduce the wheel.

It’ll save us time to buy it

It’s extremely rare to have a job where you have more time than tasks to accomplish.  If you’re like most people, you have plenty to keep you busy.  If there are other tasks I can work on, I’ll offer an existing solution, rather than build it again.  That way the company and I can accomplish more tasks in less time.  Efficiency is king!

Why would we want to waste time?

It’ll save us time and money to buy it.

Quite often, my first two reasons come together.  This is the scenario where companies most often will choose to purchase the solution, rather than build it again.  I still haven’t quite figured out how to make the case without it being a time saver and a money saver.

The best has already been done, I can’t top it.

This one was the hardest for me to admit.

No one likes to admit they have limitations, but I’ve finally gotten to a point where I feel more comfortable with the fact that others are far better than me at some things.  In those cases, I have to tell my employers “This solution right here is better than anything I could produce.  Buy it.”

I push myself every day to be better than I was yesterday.  If I tell you this other solution is better than anything I could produce, you might want to really think about it.  I’m trying to be fair to both of us.

Once the decision is made to build it anyway…

When the decision comes to recreate the wheel, how you deal with it is as important as the work itself.  Push yourself to build the best wheel you can.  Learn everything you can from the experience.  You never know when you’ll have to build that wheel again.  Take notes, and maybe you can save yourself some time in the future.

Or better yet, maybe your solution becomes the best one available.

How about that?

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme