<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>javascript on Mari Galicer.</title>
    <link>/tags/javascript/</link>
    <description>Recent content in javascript on Mari Galicer.</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 Feb 2019 01:45:03 +0000</lastBuildDate><atom:link href="/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>async/await vs .then() in JS Promises</title>
      <link>/posts/js-promises/</link>
      <pubDate>Mon, 11 Feb 2019 01:45:03 +0000</pubDate>
      
      <guid>/posts/js-promises/</guid>
      <description>Promises are at the core of asynchronous programming in JavaScript, but sometimes the patterns surrounding their use can be really confusing.
First of all, there are two main things you can do with promises: create and handle them. This post will be mainly focused on the latter: how do we effectively handle promises when we need some information now, some later, and have some behavior that depends on a promise&amp;rsquo;s return value?</description>
    </item>
    
    <item>
      <title>Hardware hacking with Arduino, Neopixels, and MTA data</title>
      <link>/posts/hardware-hacking-with-arduino/</link>
      <pubDate>Wed, 30 Jan 2019 11:02:40 +0000</pubDate>
      
      <guid>/posts/hardware-hacking-with-arduino/</guid>
      <description>As a New Yorker, I&amp;rsquo;ve had this dream, for awhile now - to be able to glance at a display on my wall and know when my train is coming. The MTA has a website that provides this experience, but the user experience is pretty terrible and you can&amp;rsquo;t even bookmark your subway stop.
And thus, the MTA Train Time Display project was born: an LED matrix that displays the number of minutes until the next train arrives at my station.</description>
    </item>
    
  </channel>
</rss>
