<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>line-by-line on Bald Engineer</title><link>https://www.baldengineer.com/tag/line-by-line</link><description>Recent content in line-by-line on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 01 Oct 2016 00:20:44 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/line-by-line/index.xml" rel="self" type="application/rss+xml"/><item><title>Blink without delay() explained line-by-line</title><link>https://www.baldengineer.com/blink-without-delay-explained.html</link><pubDate>Wed, 05 Aug 2015 13:00:27 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=5275</guid><description>&lt;p&gt;Making the move to millis()-based code can be daunting. You have to rethink your logic, implement flags, program a state machine — and more importantly, start using millis(). Generally in forums and on IRC people will just point to the &amp;ldquo;blink without delay&amp;rdquo; example, hoping the commented code is enough for a new user. It&amp;rsquo;s not enough.&lt;/p&gt;&#10;&lt;p&gt;I have a growing list of millis()-based tasks posted in my millis() cookbook. But sometimes that those examples might be too simple or not close enough to your project&amp;rsquo;s end target. That got me thinking about different ways to help explain how millis() works. I thought &amp;ldquo;wow, you need to understand every line of an example&amp;rdquo; which leads me to: line-by-line.&lt;/p&gt;</description></item></channel></rss>