<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>kicon on Bald Engineer</title><link>https://www.baldengineer.com/tag/kicon</link><description>Recent content in kicon on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 31 Mar 2022 04:01:37 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/kicon/index.xml" rel="self" type="application/rss+xml"/><item><title>6 things I learned about KiCad at KiCon 2019</title><link>https://www.baldengineer.com/6-things-i-learned-about-kicad-at-kicon-2019.html</link><pubDate>Fri, 17 May 2019 18:26:00 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=7786</guid><description>In April 2019, hardware hackers, hobbyist, and engineers joined together for the first KiCon. A couple of people asked me, “why is there a conference for KiCad?” Some questioned if KiCad was significant enough software to warrant a conference. That question is valid. But KiCon is larger than the KiCad software. Even in its first iteration, KiCon evolved more into a meeting for people building electronics hardware from small scale hobbyist to professionally designed systems, than just a conference on a single piece of software. Some might call it a maker conference. I call it a hardware developer conference. The key that tied everyone together is the open source software behind our printed circuit boards.<p><img src="https://www.baldengineer.com/wp-content/uploads/2019/05/Kicon2019-Banner.jpg" alt="6 things I learned about KiCad at KiCon 2019"/></p></description></item></channel></rss>