<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tsigorf</title>
    <description>The latest articles on DEV Community by Tsigorf (@tsigorf).</description>
    <link>https://dev.to/tsigorf</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F77453%2F35493599-d806-4aab-b1ca-c77dcf7e346d.png</url>
      <title>DEV Community: Tsigorf</title>
      <link>https://dev.to/tsigorf</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tsigorf"/>
    <language>en</language>
    <item>
      <title>What's the point using callbacks if they're only called once?</title>
      <dc:creator>Tsigorf</dc:creator>
      <pubDate>Tue, 28 Aug 2018 09:09:24 +0000</pubDate>
      <link>https://dev.to/tsigorf/whats-the-point-using-callbacks-if-theyre-only-called-once-npf</link>
      <guid>https://dev.to/tsigorf/whats-the-point-using-callbacks-if-theyre-only-called-once-npf</guid>
      <description>&lt;p&gt;Can someone explain what's the point using a callback if it's only called once?&lt;br&gt;
Concurrency?&lt;/p&gt;

&lt;p&gt;Don't we barely need concurrency if all of our program is waiting for a single request result? (That's often the case for me.)&lt;/p&gt;

&lt;p&gt;Moreover, pyramidal code obstruct readability.&lt;br&gt;
For me, &lt;code&gt;await&lt;/code&gt; is a gift (not always, but very often).&lt;/p&gt;

&lt;p&gt;So, how are you handling asynchronous code most of the time?&lt;br&gt;
I'd be happy to find out great design patterns I may not know :-)&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>javascript</category>
      <category>node</category>
    </item>
  </channel>
</rss>
