<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dor Tzur on Medium]]></title>
        <description><![CDATA[Stories by Dor Tzur on Medium]]></description>
        <link>https://medium.com/@dortzur?source=rss-713212274cd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oeDwjGzTCu0W6rBL.jpg</url>
            <title>Stories by Dor Tzur on Medium</title>
            <link>https://medium.com/@dortzur?source=rss-713212274cd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:10:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dortzur/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Are JavaScript Developers the New Kings of Software?]]></title>
            <link>https://medium.com/@dortzur/javascript-developers-the-new-kings-of-software-c1cb6c288055?source=rss-713212274cd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1cb6c288055</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Dor Tzur]]></dc:creator>
            <pubDate>Mon, 25 Jan 2016 16:15:52 GMT</pubDate>
            <atom:updated>2016-01-25T16:21:01.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-XTWujx88Rjd4rrui-ufg.jpeg" /></figure><p>Not so long ago, being a JavaScript developer wasn’t a thing to be proud of. JavaScript developers were considered 2nd class. “Pixel Pushers” they used to call us.</p><p>Let’s take Matt for example. Matt was a typical junior developer 5–7 years ago.</p><h3>The Old Days</h3><p>Matt’s first programming job was a junior developer for a large software company. Matt was immediately assigned “HTML Duty” upon arrival.</p><p>HTML Duty meant taking a Photoshop PSD file and then “translating” it to HTML and CSS.</p><p>Matt would then have the “awful” and “dreaded” task of dealing with JavaScript. JavaScript was the most feared programming language of all.</p><blockquote><em>Real coding was done in the back end</em></blockquote><p>JavaScript was so feared in fact, that many <a href="https://blogs.windows.com/msedgedev/2015/05/06/a-break-from-the-past-part-2-saying-goodbye-to-activex-vbscript-attachevent/">historic travesties</a> were <a href="http://www.guynirpaz.com/2012/04/28/gwt-is-dead/">made</a> just to avoid it.</p><p>Matt’s task was to create the UI for the “real features” the backend developers were working on.</p><p>You see, real coding used to happen only at the backend. That’s where complex N-Tier Systems shined. Writing stored procedures, making API calls and coding complex BI is what real programmers used to do.</p><p>Matt would continue on playing with JavaScript until a newer developer would come along. Matt would then finally get his chance to do some “real coding”.</p><h3>Fast Forward 2016 — JavaScript is Everywhere</h3><p>Matt currently works on an elaborate single page with React and Node.js. Matt now uses JavaScript on the server too. He’s a full stack web developer.</p><p>Matt isn’t constrained to developing web apps alone. Armed with his knowledge of JavaScript, he’s now set to conquer <a href="https://facebook.github.io/react-native/">native mobile apps</a> and the <a href="http://cylonjs.com/">internet of things</a> as well. I guess <a href="http://blog.codinghorror.com/the-principle-of-least-power/">Atwood was right</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*TYIdSa6iB4KCzLZo5Kax-w.png" /><figcaption>End of 2015 Stack Overflow Survey</figcaption></figure><blockquote><em>We’ve come a long way since the days HTML was a chore</em></blockquote><p>JavaScript developers are highly sought after in 2016. 3 out of 5 of Stack Overflow’s most wanted technologies are JavaScript and JavaScript related.</p><h3>Front End is Front Stage — Back End as a Service</h3><p>The front end of apps and services is now much more complex and demanding than it used to be. Users today set a high bar when it comes to their experience.</p><p>The back end on the other hand, became much simpler for a lot of us. Login with Facebook, enter some data and I’ll show you how I do something cool and useful with it.</p><p>In some apps, the back end has become so “uninteresting” for developers, that there are third party services that claim they <a href="http://parse.com/">can handle it for you.</a></p><h3>JavaScript Developers have an Amazing Ecosystem</h3><p>Every modern programming language has got have a thriving module ecosystem.<br> Ruby has Ruby Gems and Java has Maven.</p><p>JavaScript didn’t have one for a very long time. But npm played catch-up in at an astounding rate.</p><p>npm started as a Node.js only package manager. But as time passed and dev tools such as webpack gained popularity, npm became the package for front end packages as well.</p><h3>The day that npm unofficially became the package manager for the front end</h3><p>There was one major event that made npm the clear choice for front end modules. On February of 2015, jQuery shut down its plugin repository recommending <strong>npm</strong> as the alternative.</p><blockquote><em>npm is the bigger than any other package manager of any language.</em></blockquote><p>And it’s only getting bigger.</p><h3>Average new packages per day (measured Jan 7 — Jan 13, 2016)</h3><ol><li>npm (JavaScript): <strong>434</strong></li><li>GoDoc (Go): <strong>142</strong></li><li>Packagist (PHP): <strong>102</strong></li><li>Maven (Java): <strong>75</strong></li><li>nuget (.NET): <strong>64</strong></li></ol><blockquote><em>Source: Module Counts</em></blockquote><blockquote><strong><em>If you sum up the 4 fastest growing languages after JavaScript, you’ll still be 51 packages/day short of npm.</em></strong></blockquote><p>I don’t know about you, but I’m pretty impressed.</p><h3>JavaScript Developers Wanted</h3><p>JavaScript developers are needed in almost every major software company. There’s an unfair reason for that. No matter what the company’s tech stack is, if they want to run on browsers, they have to speak JavaScript.</p><p>There are 2 awesome side effects to this fact.</p><h3>1. High Demand</h3><p>There’s an enormous demand for JavaScript developers. The market right now is great for any developer. But JavaScript developers who pass the “good enough” criteria are in <a href="http://www.talentbuddy.co/blog/top-tech-skills-required-for-entry-level-programming-jobs/?utm_source=%20http%3A%2F%2Fthefullstack.xyz%2Fjavascript-developers%2F&amp;utm_medium=content_page&amp;utm_campaign=The%20Full%20Stack">especially high demand.</a></p><h3>2. Tech Mobility</h3><p>JavaScript equals tech mobility. I was able to switch from a .Net company to a Ruby/Node.js company without losing seniority. Because of my JS knowledge, I was able to learn Ruby from scratch while still providing high value on the front end. No other language allows you to do that.</p><p>I think JavaScript developers have had a hard time in the past. But today I can honestly say investing in my JavaScript skills is the best decision I’ve ever made.</p><p><em>Originally published at </em><a href="http://thefullstack.xyz/javascript-developers/"><em>TheFullStack.xyz</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1cb6c288055" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Sweet Javascript Newsletters That Will Help You Out]]></title>
            <link>https://medium.com/the-full-stack/6-sweet-javascript-newsletters-that-will-help-you-out-aa3b2f7b279?source=rss-713212274cd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa3b2f7b279</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Dor Tzur]]></dc:creator>
            <pubDate>Fri, 15 Jan 2016 10:56:00 GMT</pubDate>
            <atom:updated>2016-01-15T11:07:19.017Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F2KuhiDw2eGkVQn8W8ebMw.jpeg" /></figure><h4>Originally posted on <a href="http://thefullstack.xyz/web-development-newsletters/">The Full Stack</a></h4><p>Technology cycles are lightning fast right now for web developers. I sometimes feel <a href="http://thefullstack.xyz/framework-fatigue/">exhausted from all the noise.</a></p><p>Angular used to be all the rage. So I started learn all about angular, and even became the angular evangelist of my workplace.</p><p>Then one day Angular was out and React was in.</p><p>If you then decided to start learning React, you quickly realized you need to choose a Flux implementation.</p><p>When you do your research you quickly realize that there are a dozen of different flux implementations. The “King” of flux implementations also changes every week. From Reflux to Alt (for like a day) and then to Redux.</p><p>Redux isn’t even really a flux implementation, but I consider it the best choice right now. At least until next week.</p><p>To keep up with all of the insanity around me, I subscribe to these 5 newsletters which are pretty awesome. Reading through them every week has been helping me to keep up with everything. ​</p><h3>Top Web Development Newsletters</h3><h3>JavaScript Weekly</h3><p><a href="http://javascriptweekly.com/">JavaScript Weekly</a> is the undisputed king of web development newsletters. JS Weekly the number one resource for getting the latest JavaScript news and updates. If you’re going to subscribe to just one newsletter, JS Weekly should be it.</p><h3>​JSter</h3><p><a href="http://jster.net/">JSter</a> is a high quality newsletter. It always starts with a short intro and then dives right down to business</p><p>Its sections include​:</p><ul><li>Libraries</li><li>Articles</li><li>Guides</li><li>Techniques</li><li>Interviews</li><li>Resources</li><li>Demos</li></ul><h3>HTML5 Weekly</h3><p><a href="http://html5weekly.com/">HTML5 Weekly</a> is a great place to find out more about browser technologies, ​and the latest and greatest developments regarding Chrome, Safari, and other browser vendors.</p><p>They also feature nice CSS tips, design tips, and developer tools tricks.​</p><h3>React Native Weekly</h3><p>​This is the new kid on the block. <a href="http://brentvatne.ca/react-native-newsletter/">React Native</a> is barely one years old, but already has its very own newsletter. And a good one.</p><h3>Node Weekly​</h3><p>If you’re into node, which ​you should because it’s awesome, <a href="http://nodeweekly.com/">Node Weekly</a> is the newsletter for you. Another hit from Cooper Press.</p><h3>​Mobile Web Weekly</h3><p>The mobile web ​is <a href="https://www.clickz.com/clickz/column/2388915/why-mobile-web-still-matters-in-2015">important</a>. In fact, we’re already past the mobile tipping point. Mobile browser usage is more popular than the desktop.</p><p>That’s where <a href="http://mobilewebweekly.co/">Mobile Web Weekly</a> comes in handy.</p><p>MW Weekly isn’t quite on the same level as the rest of Coppers press’s newsletters. But if you’re into Ionic and Cordova it’s definitely worth a look.</p><p>What are your favorite ways to keep up with up with the pace?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa3b2f7b279" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack/6-sweet-javascript-newsletters-that-will-help-you-out-aa3b2f7b279">6 Sweet Javascript Newsletters That Will Help You Out</a> was originally published in <a href="https://medium.com/the-full-stack">The Full Stack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you have Framework Fatigue?]]></title>
            <link>https://medium.com/the-full-stack/do-you-have-framework-fatigue-7680bae31bdb?source=rss-713212274cd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7680bae31bdb</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dor Tzur]]></dc:creator>
            <pubDate>Wed, 06 Jan 2016 01:03:02 GMT</pubDate>
            <atom:updated>2016-01-18T17:27:49.051Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s play a game.</p><p>Write down all the frameworks/build tools/libraries you can think of for 30 seconds straight and then stop.</p><p>Ready, set, go!</p><p>Ember, Angular, React, Express, Grunt, Bower, npm, Broccoli, Gulp, Lodash, Underscore, rxjs, Knockout, SocketIO, Threejs, D3, Backbone, Ionic, Angular2, React Native, Redux, Alt, Reflux, Webpack, Bluebird, Q, Express, Mocha, Jasmine, Chai, Koa, Less, Sass, Postcss, Impressjs, Revealjs.</p><p>Tired yet? In short, that’s what framework fatigue is.</p><h3>Framework Fatigue in Detail</h3><p>You gotta love JavaScript. This tiny language is now the most popular in the world.</p><p>It’s also everywhere. Although it was originally meant to run only on Netscape Navigator.</p><p>JavaScript is now the only language modern browsers speak. It has a clear monopoly as others will be lost in the sands of time. Poor VBScript, we won’t miss you.</p><p>But JavaScript’s unfair monopoly wasn’t enough for this tiny language. It now runs on servers thanks to node, and mobile apps thanks to Cordova and React Native. It might also <a href="https://samsung.github.io/iotjs/">run on your fridge</a> sooner than you think.</p><p>As JavaScript tackles bigger and more complex problems, we want higher level of abstraction to help us deal with those problems.</p><h3>JavaScript frameworks to the rescue!</h3><p>npm is the de facto package manager for both frontend and backend JavaScript libraries. It passed Ruby Gems and Maven, making it <a href="http://www.modulecounts.com/">largest package manager</a> for any language.</p><p>npm having such a huge number of libraries is both great and awful at the same time. You can find libraries on npm that will help you with anything from machine learning to telling the time.</p><p>But there’s so much choice. Too much choice. It’s <a href="http://thefullstack.xyz/web-development-newsletters/">hard to keep up.</a></p><p>Let’s imagine the following scenario</p><p>You’re starting your brand new side project. You can choose whichever framework you like. The world is your oyster.</p><p>Let’s say you decide to go with React, because it’s the cool kid on the block right now.</p><p>To use React you need to transpile JSX, so you’re going to use Babel.</p><p>You realize that to use Babel effectively you’ll need some sort build tool. You shop around between grunt, gulp, broccoli, browserify and weback. After careful consideration, you decide webpack is the best choice for you.</p><p>You’re now finished with all the fiddling around and can finally start coding.</p><p>After a few hours of coding, you realize React is just the view layer of your app. You wonder what’s the best way to manage the state of your app. Soon enough the word Flux comes up.</p><p>Luckily enough Facebook released it’s Flux implementation, problem solved. Back to coding.</p><p>After reading through Facebook’s Flux implementation, you realize that there seems to be a lot of boilerplate code involved in doing simple tasks. While that might make sense for a huge website such as Facebook, your pet project is better off with something leaner and meaner.</p><blockquote><em>So you start to wonder, are there any other Flux implementations out there?</em></blockquote><p>Between 5 to 20 minutes after you ask yourself that question you encounter this fantastic <a href="https://github.com/voronianski/flux-comparison">flux comparison table</a>. This is the part where you start questioning life choices. If you’d have only listened to your mother and became a doctor, they make much less scary and fateful decisions.</p><p>You’re now left several choices:</p><ol><li>Go over each of the flux library’s source code and documentation. After carefully reviewing each and every library and doing a small benchmark for each one you decide which library best suits your need. <strong><em>This has been done exactly zero times by no one ever.</em></strong></li><li>Type into Google “Best flux implementation”. You search until you find 2 separate blog posts which both state the same library as “best”, and go with that. <strong><em>Most popular choice.</em></strong></li><li>See which library has the most stars on GitHub. <strong><em>Works best when combined with 2</em></strong></li><li>Choose nuclear.js because it has the coolest sounding name of the bunch.</li><li>Kill your pet project and go hang out in the sun.</li><li>Learn COBOL. Find a COBOL programmer job. Never worry about any language update or new framework ever again.</li></ol><blockquote><em>COBOL developers don’t have framework fatigue</em></blockquote><p>By the way as of this writing, Redux is considered the “best” right now. I just saved you some time if you chose option 2. Just one more blog post and you’re set.</p><p>This is just a tiny example of the many decisions web developers have to make.</p><p>And if you’re developer your server-side with node you, you’ll find yourself going through this whole process all over again from scratch. <a href="http://alternativeto.net/software/expressjs/">Express vs. * anyone?</a></p><blockquote><em>Framework Fatigue is the result of the JavaScript ecosystem continued growth.</em></blockquote><p>JavaScript is becoming more and more popular. Demand for full stack web developers continues to rise. I’m sure we’ll see many more talented people creating many more wonderful npm packages.</p><p>I hope that as the JavaScript ecosystem matures, we’ll see more convergence between libraries. Making framework fatigue just another scary story we tell our kids.</p><p><em>Originally published at </em><a href="http://thefullstack.xyz/framework-fatigue"><em>TheFullStack.xyz</em></a><em> on January 6, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7680bae31bdb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack/do-you-have-framework-fatigue-7680bae31bdb">Do you have Framework Fatigue?</a> was originally published in <a href="https://medium.com/the-full-stack">The Full Stack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native for Android — The Promised Land]]></title>
            <link>https://medium.com/@dortzur/react-native-for-android-the-promised-land-2a7311ecf5e5?source=rss-713212274cd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a7311ecf5e5</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dor Tzur]]></dc:creator>
            <pubDate>Tue, 15 Sep 2015 11:21:02 GMT</pubDate>
            <atom:updated>2015-09-15T11:21:02.560Z</atom:updated>
            <content:encoded><![CDATA[<p>The day has finally arrived. As a Cordova developer for past 3 years I could not be more excited. My expectations were high, and React Native for Android didn’t disappoint.</p><h3>First Impressions</h3><p>I followed the <a href="http://facebook.github.io/react-native/docs/tutorial.html#content">simple tutorial</a> on the react-native main page. After creating a new React Native project you get a very intuitive project structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*NlytzvBiWXv_dChOPoSLZg.png" /></figure><p>As you might have also noticed I’ve used Ubuntu for this tutorial. Although only OS X is currently officially supported, everything “just worked”</p><p>Developing with React Native feels like magic. After every edit of “index.android.js” you see a loading indicator for half a second and the entire screen instantly reloads with the changes. Live reload with native views is very impressive by itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*kPHhteGYa_xT7N48u6ecZA.png" /><figcaption>Look mom, a native list view written in JavaScript</figcaption></figure><p>Following the tutorial was a breeze, every step was working as described. I was able to use styling with the flexbox model, use arrow functions, and add “Text”, ”Image” and “ListView” components easily.</p><h3>To Sum it Up</h3><p>React native more than lives up to the hype. Not to be too dramatic but this feels like we’re the brink of a new era, at least for jaded Cordova developers who just want their animations to work properly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a7311ecf5e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>