<?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 Michael Petrosyan on Medium]]></title>
        <description><![CDATA[Stories by Michael Petrosyan on Medium]]></description>
        <link>https://medium.com/@mikpetr?source=rss-e9a35e1d8943------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*x8QsHLIDRAjfUmJ-4JCHBw.jpeg</url>
            <title>Stories by Michael Petrosyan on Medium</title>
            <link>https://medium.com/@mikpetr?source=rss-e9a35e1d8943------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:01:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikpetr/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[What I learned from my first experience of building a startup]]></title>
            <link>https://medium.com/@mikpetr/what-i-learned-from-my-first-experience-of-building-a-startup-851db8c2d335?source=rss-e9a35e1d8943------2</link>
            <guid isPermaLink="false">https://medium.com/p/851db8c2d335</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[market-research]]></category>
            <category><![CDATA[startup-mistakes]]></category>
            <category><![CDATA[idea-validation]]></category>
            <dc:creator><![CDATA[Michael Petrosyan]]></dc:creator>
            <pubDate>Wed, 25 Apr 2018 18:56:18 GMT</pubDate>
            <atom:updated>2018-04-25T18:57:19.877Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QkJbOqsH_lnrxodEWCSYQ.jpeg" /></figure><p>In this article I want to share about my first experience of building a startup.</p><p>Let me tell little bit about myslf. I am a web developer who started his career very soon (for that time :)). I was 14 years old. I have worked mainly with JavaScript and did almost everything JavaScript can do. I worked on front end, back end, hybrid mobile apps and even with Unity.</p><p>At some point there was a startup acceleration program organized by Microsoft. I decided to join to that program. I told about that program to my friend who was also a developer and he agreed to join.</p><p>Next we started to generate an idea. Let me tell some details about the idea.</p><p>It was a mobile application, that allow people to find others who are nearby and have same interests, so you can call them directly through the application and meet them.</p><p>From first read you may think, that it’s a dating app, but no. We decided to hide the photo, gender, name of other people and they can’t text each other. The only way to socialize, is to call and meet with that person.</p><p>Sounds interesting right? But there was a huge problem, that at that point I did’t understand. I will tell about that little bit later :).</p><p>OK we applied for the acceleration program and started building our application.</p><p>Acceleration program is running, we meet with our mentor once a week. And we are building an application parallel. After several meetings I started to take a deeper look about one questions. “What problem solves your product?”.</p><p>Well, actually I think that problem exists, but it need to be validated. So I started a survey and found, that the problem really exists. There are so many people, that don’t do what they want because of a luck of company.</p><p>OK. What we have now? The process of application development is still in progress, we have validated idea, it’s already about 3 months that acceleration program started. Seems all cool.</p><p>And at one day I wake up and understand, that our app is not solving the problem.</p><p>We need a platform, which will help people to find someone who want to do the same thing, but not doing that because he/she don’t have a company. And what we offer? We offer app that allow to call and meet nearby person who have similar interests.</p><p>We decided to change the app. We are now creating platform where every person will post an activity and people who interested in that activity will contact with that person and go to have fun together.</p><p>Seems cool, right? :)</p><p>Next, after two months my friend received a good job offer and leave me alone.</p><p>After several weeks I also break up.</p><p>The main problem of all this was, that we don’t clearly understood what problem we solve. Dose actually consumer have that problem? Is our solution really solve the problem? Beside of this we also did’t have a clear business plan.</p><p>This story is from series “Don’t try to do this at home”. :)</p><p>Today, after 2 years of delay, I have very different approach about how startup must be built.</p><p>I remember the film “Pirates of silicon valley”. Especially <a href="https://www.youtube.com/watch?v=dCTU89hIzvk">the part where Bill Gates sell product, that he don’t even have</a>. And that is the ideal version. :)</p><p>Today, if you tell me that you have an idea, I will ask you those questions.</p><ol><li>Did you do idea validation?</li><li>Did you do market research?</li><li>How you will do business?</li></ol><p>Let me drop it down.</p><p><strong>Idea validation</strong></p><p>Before building anything you need to understand, dose the problem really exists. If yes, are people really care about it?</p><p>So before doing anything just go out and do a survey, or hire someone who you trust. There are many types of surveys, but personally I prefer one to one interviews. You will get more information about your potential customers needs.</p><p><strong>Market research</strong></p><p>The next step is market research. The problem, that you want to solve may really exists, but you need to understand if the market size is enough for you. You need to understand is it worth to dive into it.</p><p>Beside of market size you need to analyze also your competitors. You need to understand how you different from others and why customer should choose your solution.</p><p><strong>Business plan</strong></p><p>The next key point is a business plan. You need to clearly understand how you will make money. There are so many problems that really exists, but people who trying to solve that problems don’t know how to make money from that. They spend their time, build a product, go to investors, asking for investment and investor says “OK, that’s cool, but how you will make money?”.</p><p>If you get a positive answers to all those questions, then go forward and do it as fast as you can.</p><p>But don’t forget one important thing. You are building a solution for solving a problem. From time to time you need to speak with your customers, to understand what they want, dose it easy to use, dose it really solve the problem etc.</p><p>Currently I don’t reach this point yet, but I hope and believe, that it will happen and I will continue this series to share my experience with you.</p><p>Thanks for your time :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=851db8c2d335" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular 5 vs. React vs. Vue]]></title>
            <link>https://itnext.io/angular-5-vs-react-vs-vue-6b976a3f9172?source=rss-e9a35e1d8943------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b976a3f9172</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Michael Petrosyan]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 09:19:19 GMT</pubDate>
            <atom:updated>2018-03-28T23:00:01.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OgqQRDfBtrftDNJrVHbHw.png" /></figure><p>Nowadays, technologies are growing very fast. Every day, week and month more and more tools appear to solve different problems.</p><p>In this article, I want to compare 3 of the most popular technologies for the front end development: <strong>Angular 5</strong>, <strong>React</strong>, and <strong>Vue</strong>. I am going to compare them from the perspective of the project architect or just a developer who is going to choose a framework for the new project.</p><p><a href="https://www.linkedin.com/cws/share?url=https%3A%2F%2Fitnext.io%2Fangular-5-vs-react-vs-vue-6b976a3f9172"><em>Click here to share this article on LinkedIn »</em></a></p><p>OK, let’s start from React. Many people name it a framework. Well, actually it isn’t . React is just a view oriented library. It’s a view in MVC. Angular and Vue are frameworks.</p><p>So, to choose one, we should start from this point: Do we need a library or framework? Let’s look at each one deeper.</p><p>Actually, libraries are designed for doing only some specific tasks and they are not so complex. If you are constructing your application form libraries, you need to choose a library for every task, you need to setup task runners, etc.</p><p>The plus of it is that you have full control over the application. But it will take much more time to set up the project.</p><p>As I mentioned earlier, we are making a comparison from the position of project architect, so we also must think about other developers. And there is one more problem. As React applications constructed from different libraries, stack of libraries changes from project to project. It means, that for other developers it will be harder to join. Also development process will take much more time, because you are working with low level API’s.</p><p>Now let’s take a look to frameworks.</p><p>Frameworks are designed for doing more complex things, so, if you are using framework, there is already solved lot’s of problems for you. Frameworks have predefined design, already setup task runners and many libraries. You already can create fully functional project without other setups. As a result we can setup a new project very easily, development process is much faster, because we are already using high level API’s and every application which developed with that framework use same libraries, so for other developers will be much easier to join. But frameworks have more strict design.</p><p>Now let’s look at each one deeper.</p><p>I want to start from React, as it is smallest from our list.</p><p>React is a library for building user interfaces and for that it use components.<br>If you don’t know, then components are separated part of application which are encapsulated and can be used in different parts of our application. They are encapsulated, so that they can’t affect other, high level, part’s of application.</p><p>React use one way data flow and it’s very similar with <a href="https://redux.js.org/">redux</a> and in real applications redux used very well.</p><p>The next thing is JSX. JSX is an XML like syntax extension to ECMAScript without any defined semantics. It’s intended to be used by various preprocessors (transpilers) to transform these tokens into standard ECMAScript.</p><p>Here is an example of simple JSX syntax:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*TwFkn4CEOXQXykyBcVc9FA.png" /></figure><p>The equivalent ES6 code will be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*DFKn5PDIzWANNEYj0Byfsw.png" /></figure><p>Basically I don’t like an idea of JSX, because it’s no more a HTML. You need to use special attributes and it puts some limits.</p><p>The next big thing in React is the state of application. State is an object, that contains whole public properties of your application. It allows you to just copy the state and send to another device, open app and you will get exactly same screen, that was on first device.</p><p>State management is going through dispatchers and reducers. For example, if we want to handle button click, we set a dispatcher for that action, and when action proceed, dispatcher calls and state changes.</p><p>Now let’s move to Vue.</p><p>By comparing Vue with React we have same components and one way data flow. But there are many additions..</p><p>We have same components, but by default they work with templates, not with JSX. Main advantage of templates is that you are writing pure HTML. But if you want you can use JSX. It’s up to you.</p><p>Another thing, that is very useful, is directive. Directives mostly used for additional functionality and DOM manipulation. It’s very helpful for keeping business logic clear. Imagine, that you have some &lt;div&gt; and there is some content inside. Itself, that &lt;div&gt; is just a block element, that stands on his place. You are adding an attribute “draggable” and it becomes a draggable element. You can move it. You don’t see the logic of dragging, it’s inside directive. You just see that it is a div element that can be dragged.</p><p>Next thing are mixins. If you are familiar with LESS or SASS you are probably familiar with that term. It like inheritance of object, but is our case, that object contains properties and methods, that can be inherited from components.</p><p>Next we have filters. They allow to parse input data. For example, you have a list of dates and you need to show days count since that date (ex. 3 d ago). So instead of writing a helper service for parsing date to days count you can just define a filter and use it like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Aluw69mWPrOzwl3V3kjLEQ.png" /></figure><p>Another big thing is dependency injection. If you are familiar with some object oriented language you probably know about dependency injection. With dependency injection in every module you have exactly those modules, which are needed for that module. It’s one of the core rules of encapsulation. In large applications it is very important.</p><p>Now let’s move to Angular.</p><p>In Angular we have same components, one way data flow, HTML, templates, filters (that named pipes), directives, dependency injection. In addition we have modules and services.</p><p>Modules consists from components, services, directives etc. They are more general and mostly used for providing some feature.</p><p>Services are designed for doing some specific thing. Here is where main business logic must be written.</p><p>Well. The next section, that I want to write about is DOM rendering. Here we have two modules of DOM rendering. React and Vue are using Virtual DOM and Angular use direct DOM rendering system. It’s the same thing that Angular did with version 1.x, but it is optimized and there is a surprise for you :).</p><p>Let’s start from Virtual DOM. Assume, that you have a list of 5 items.</p><p>Now something changes in first row. What most frameworks do is rebuild and re-render whole list. It’s 5 time more work, than necessary. We need to update only first row.</p><p>Not let’s take a look what will do virtual DOM in this situation.</p><p>Before any manipulation it creates the copy of DOM and work with this copy. It is much faster to work with JavaScript objects than with DOM, because nothing drown on screen.</p><p>When virtual DOM has been updated, it compare with the old version, that has been captured before update and find elements that must be updated. This process called “diffing”. After checking difference, in real DOM updates only those parts which are changed.</p><p>This is how manage DOM rendering React and Vue.</p><p>Now let’s take a look to the Angular.</p><p>Angular’s rendering has one very interesting point. Angular uses both browser’s thread (UI area) and service worker thread (worker area). Worker area responsible for building out and compiling directives, services, filters and bootstraps the code. UI area is responsible for DOM rendering. You can compare it with computer’s processor and graphic card. Worker area is the processor and UI area is the graphic card.</p><p>The other awesome part is, that renderer can be different based on environment on which application running. For example if you want to draw your application on canvas, you easily can do that. You just need to implement Renderer class.</p><p>For understanding how this approach make sense let’s compare some benchmarks.</p><p>Here are screenshots of my benchmark test</p><p>I make a calendar with 31 days and 24 hours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bLJJhTDEsphsPHkipsmkGw.png" /></figure><p>When you click on one item, it loads some random number. Instead of making real request I am doing 0-500 ms delay. It is also random. Now imagine what will happen when we click on all items at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M68KjQQtTMfaGK7D1M0eHQ.png" /></figure><p>Theoretically whole table must be loaded within 500ms. But reality is different.</p><p>I am using Google Chrome’s performance tool for calculating time, starting from my button click until rendering process end.</p><p>For React it takes 1819 ms</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmAYyas5k8Z_WtHwbOqAZA.png" /></figure><p>For Vue it takes 1191 ms</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ly274alVQpJx8JlwS-_y3Q.png" /></figure><p>And for Angular it takes 931 ms</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_rdNmS3DGR8evcDaNXNPYw.png" /></figure><p>You can test it by your own. Here are links for each one.</p><p><a href="https://github.com/mikpetr/angular-performance-test">https://github.com/mikpetr/angular-performance-test</a><br><a href="https://github.com/mikpetr/react-performance-test">https://github.com/mikpetr/react-performance-test</a><br><a href="https://github.com/mikpetr/vue-performance-test">https://github.com/mikpetr/vue-performance-test</a></p><p>The next thing, that I want to speak about, is Server Side Rendering. Angular, React and Vue support it. It was really needed part from Angular 1.x. In my opinion, that’s why today exists many websites, that are written by server side rendering logic. So now SEO is not a problem :)</p><p>How it works?<br>Very simple. For each library/framework exists packages, that can render your code as it work in browser and return already rendered page. The cool thing is, that it works automatically. No need to rewrite the application.</p><p>As you may already know mobile technologies are growing very fast and again Angular, React and Vue can be used for developing mobile apps. Angular have many components written directly for Ionic, React have React Native and Vue have Framework 7.</p><p>From the perspective of the architect of the project and for the company itself, learning curve is very important, as if you have a team, than your employees may leave and other’s may join.</p><p>Again let’s start from React. And here we have one tricky moment. React is simple. The only things, that you need to understand are how to work with components, JSX and state management. But for building fully functional application you need to know or learn many additional libraries and it’s very tricky. The main advantage of React applications is that there is a lot’s of custom solutions and from one project to another it can and will vary. So for new employees it’s not so good.</p><p>In Vue you already have fully functional framework and you don’t need to connect lot’s of libraries. Anyway, if you need, they are not change the architecture of the application. But Vue have already more components that you need to be familiar or learn, like directives, mixins, dependency injection etc.</p><p>In Angular learning curve is much longer. And the main problem and feature, is TypeScript. Yes you can use Angular without TypeScript, but in my opinion, if are not going to use TypeScript, then you probably don’t need Angular.</p><p>So from perspective of learning curve I will order those technologies in following order:</p><ol><li>Vue</li><li>React</li><li>Angular</li></ol><p>Of course I can’t say, that one framework is better than other and you need to use that. All depends from project and from the team skills.</p><p>React is good for logic less applications or for specific problems, where you need a custom solution.</p><p>Vue is good if your application is not very small and you need fast development.</p><p>Angular is good if your application big enough, that you need very strict source code.</p><p>Thanks for your attention and for your time. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b976a3f9172" width="1" height="1" alt=""><hr><p><a href="https://itnext.io/angular-5-vs-react-vs-vue-6b976a3f9172">Angular 5 vs. React vs. Vue</a> was originally published in <a href="https://itnext.io/">ITNEXT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>