<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Circuits on Bald Engineer</title><link>https://www.baldengineer.com/tag/circuits</link><description>Recent content in Circuits on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 24 Mar 2015 21:59:06 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/circuits/index.xml" rel="self" type="application/rss+xml"/><item><title>HackEDA: Collecting and Sharing reusable pieces of electronic designs</title><link>https://www.baldengineer.com/hackeda-collecting-and-sharing-reusable-pieces-of-electronic-designs.html</link><pubDate>Thu, 25 Apr 2013 09:14:56 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=1670</guid><description>One of the most commonly used phrases when writing software is “reusable code.” From the Wikipedia article on “Code Reuse”. Reusable code is:&#10;the use of existing software, or software knowledge, to build new software.&#10;Software coders have been sharing and re-using code since they first start programming. So why can’t this same idea be applied to hardware design? Doesn’t it seem silly to redraw the ATmega328 for an Arduino based project or even the really simple linear regulator circuit? Well, it can thanks to HackEDA you can start using reusable code to save time (and from creating mistakes).<p><img src="https://www.baldengineer.com/wp-content/uploads/2012/09/HackEDA-Banner1.png" alt="HackEDA:  Collecting and Sharing reusable pieces of electronic designs"/></p></description></item></channel></rss>