<?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 Milan Korsos on Medium]]></title>
        <description><![CDATA[Stories by Milan Korsos on Medium]]></description>
        <link>https://medium.com/@milankorsos?source=rss-1978e73ad70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Tb_XKnfLaNfXsaoG.jpeg</url>
            <title>Stories by Milan Korsos on Medium</title>
            <link>https://medium.com/@milankorsos?source=rss-1978e73ad70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:48:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@milankorsos/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[Building Enterprise-Grade UI is Hard]]></title>
            <link>https://medium.com/@milankorsos/building-enterprise-grade-ui-is-hard-ca70aae2db58?source=rss-1978e73ad70------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca70aae2db58</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Milan Korsos]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 21:44:35 GMT</pubDate>
            <atom:updated>2018-04-11T23:18:42.083Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone seems to have an opinion on why most of the enterprise software’s UI is falling behind their consumer grade counterpart. There are indeed many products that serve as examples to support this theory. Also, there are countless posts stating that <a href="https://medium.com/@mdubakov/enterprise-software-vendors-have-no-taste-add7e78b7f69">enterprise companies have no interest to focus on good UX</a>.</p><p>The truth is, <a href="https://news.ycombinator.com/item?id=9190195">the design challenge</a> behind an enterprise-grade product is way harder than it seems at first. It needs to cover all kinds of use cases in very different environments — team size, industry and company culture. In order to win, building a solid core product is not enough. Consistent delivery of new features to accommodate all the different edge cases, configuration and customization requirements is the name of the game. This is very tough, and it’s no surprise that many companies are falling behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uopTnuhyXq928X-DV4LsxA.jpeg" /><figcaption>Sol Tran and Milan Korsos outside Rubrik HQ.</figcaption></figure><p>At Rubrik, we are committed to delivering a high-quality product even with these challenges in mind. However, our desire to deliver a simple, beautiful product is not just a something the small group of UI engineers are excited about. We, as a company, excel because we solve very complex challenges and deliver it in a simple way. It is not just about the UI — our success is <a href="https://www.youtube.com/watch?v=yNFyTNtGGC4">a result of every team working hard</a> — but we certainly couldn’t be where we are right now without investing into our user experience.</p><h3>Bipul Sinha on Twitter</h3><p>Rubrik design motto: If you can use Facebook, you can use Rubrik. #BeautifullySimple #ConsumerGrade #InfinitelyScalable #SuperiorTechnology</p><p>We spent the last four years building the foundations of Rubrik. From day one, <a href="https://www.rubrik.com/blog/introducing-crystal-rubriks-intuitive-user-interface/">we had our users in mind</a>. This helped us become <a href="http://www.information-age.com/inside-fastest-growing-unicorn-silicon-valley-123467489/">one of the fastest growing enterprise companies</a> and we are not stopping here. To fulfill our vision, the UI engineering team has a special role. Our job is to build the bridge between our technologies and our respected users. We believe the only way to build a product for the next decade is to deliver a consumer-grade experience. We are committed to learning from the best consumer facing products, and bring that experience to the enterprise world.</p><p>We are proud to present the next generation of our products, <em>Polaris</em>, where we are betting big on user experience.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFIuER1P0ENA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFIuER1P0ENA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFIuER1P0ENA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/65c65207e95c15e5d28bfa894564077a/href">https://medium.com/media/65c65207e95c15e5d28bfa894564077a/href</a></iframe><p>To bring Polaris to the market, we completely re-architected our UI. We are using the latest and greatest — we write TypeScript, talk to the API via GraphQL, manage state with Redux and Apollo, and display the data with React. We work very closely with the rest of product team writing Python, Go and Scala code, and using Kubernetes to run all of this.</p><p>We decided to start this blog to share our journey of building a consumer grade enterprise UI. We know that most of the challenges are still ahead of us, but we embrace learning and get up excited to push the limits every day.</p><p>In the coming months we’ll share our very own war stories — some problems might be interesting for the rest of community, some might only apply to us.</p><p>Here are some of the challenges that we’ll have to tackle very soon, but many more will arise:</p><ul><li>Developer velocity is everything. We invest in tooling to make our lives easier and more productive. We already have <a href="https://prettier.io/">prettier</a>, <a href="https://palantir.github.io/tslint/">linting</a> and a solid <a href="https://webpack.js.org/">webpack</a> build process setup.</li><li>To deliver all the features, we need to enable more engineers to contribute to our codebase. We do this by investing heavily in our component library, building out <a href="https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0">clear design patterns</a>, and code reviews.</li><li>Day to day, we need to display and manipulate large amount of data in the simplest way. To make this happen, we’re continuously benchmarking and improving the UI performance.</li><li>We deploy code to our users frequently. But to be able to deploy code even faster, we constantly focus on improving our unit and snapshot test coverage, automated e2e testing and continuous integration.</li><li>It isn’t just about delivering fast, but about delivering the right stuff. We have a lot of say in how to build out the features — we work very closely with the product managers and the designers.</li><li>Working on hard problems with the latest technologies gets us to roadblocks and unsolved problems all the time. Overcoming these challenges is a great learning experience, and we are excited to champion these takeaways.</li></ul><p>We are still a very small team where everyone is pulling the weight, but we are inspired by the community and aim to give back.</p><p>As a very first step, let us share a great read from the much respected <a href="https://medium.com/@_ericelliott">Eric Elliott</a> — there is a lot to take away here.</p><p><a href="https://medium.com/javascript-scene/how-to-build-a-high-velocity-development-team-4b2360d34021">How to Build a
High Velocity
Development Team</a></p><h4><a href="https://www.rubrik.com/blog/"><em>You can read more about the technology behind Rubrik</em></a><em>.</em></h4><p><a href="https://www.rubrik.com/company/careers/engineering/jobs/software-engineer-frontend-637076"><em>Also, we are hiring!</em></a><em> :-)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca70aae2db58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AB Testing with Optimizely and server-side rendering React]]></title>
            <link>https://medium.com/@milankorsos/ab-testing-with-optimizely-and-server-side-rendering-react-e6d104f7befb?source=rss-1978e73ad70------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6d104f7befb</guid>
            <category><![CDATA[ab-testing]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[optimizely]]></category>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Milan Korsos]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 04:42:50 GMT</pubDate>
            <atom:updated>2016-07-13T04:42:50.994Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>We started using Optimizely for simple AB testing on Discovery. However since Optimizely is a client side AB testing tool, we run into issues using it with our React code that is rendering the page on the server side.</p><blockquote><strong>Client-side tools</strong> create a variation of your test page by doing manipulations on your browser via clever JavaScript. Your web server sends the same version of the page, the default, as it would normally do. All the variations are reflected by the visitor’s browser. Since the changes aren’t done on your server, and are instead on the visitor’s browser, they’re called ‘client-side tools’</blockquote><blockquote><strong>Server-side tools</strong> are different, in that no modification occurs at the browser level. When the visitor lands on your page, a randomly picked version of your test is sent straight from your server. Yes, this means you have to involve your developers in testing, but it also gives you robustness and flexibility.</blockquote><blockquote>[Client-Side, Server-Side: What’s The Difference?](<a href="http://conversionxl.com/server-side-vs-client-side-ab-testing-tools-whats-the-difference/">http://conversionxl.com/server-side-vs-client-side-ab-testing-tools-whats-the-difference/</a>)</blockquote><h3>Issue with Optimizely &amp; server-side rendering</h3><p>React renders the HTML code on the server (NodeJS), sends it down to the browser where React is trying to pick it up where it left off and start modifying the page based on user actions. However after the rendered page arrives to the browser the Optimizely script modifies the DOM based on the different variations using jQuery, so when React in the browser is running into DOM inconsistencies when trying to pick up where it left off on the server.</p><h3>Possible solutions</h3><p>Unfortunately it appears that there is no way we can make a use of the Optimizely Quick Edit (HTML) feature (client side AB testing) if we keep the server side rendering. Rendering the pages on the server side is crucial for (perceived) performance and UX, as well for SEO. However we don’t need to give up on AB testing for this, we just can’t use Optimizely out-of-the-box.</p><p>The drawback of any of the solutions is that to support the server side rendering we need to have the different variations in the codebase. Which means adding and removing variants will need dev effort and deploy. However we can still use online tools to manage the experiments, which can be either Optimizely, or GA, or something else.</p><h4>How (technology run down)</h4><p>We use Redux &amp; React to render the pages both on server &amp; client side based on the data we have in the *application store*. That said if the *application store* will have information about the different AB tests, the app can render the different variations easily.</p><p>The idea is that before pageload we get all the active experiments, and the decision of what variation to serve for the user **from somewhere**, save that in the *application store*, then log the clicks on the UI and push the results **to somewhere**. (**Somewhere** can be either Optimizely or GA.)</p><p>After all the variations are deployed on the server, the pageload consists of the following steps:</p><p>I. Before page load (Node.js)<br> 1. Make an API call to get the active experiments, and the decision on the variation for the user<br> 2. Update store with the experiment information<br> 3. Render page on the server side from the store (which will be the variation per the experiment)</p><p>II. After page load (Browser) <br> 1. React will be able to pick up the render where the server left it off because the DOM is consistent to the store information -&gt; the correct variation is displayed and React is happy <br> 2. We track different events (experiment goal) on the UI and push them via an Ajax call to where we store the results.</p><h4>Using Optimizely</h4><p>We can continue to use Optimizely for managing the variations, collecting and analyzing the results. Important to note that this solution will require dev efforts to put the variations in place, but once they are deployed to staging/production PO can turn the experiments off and on anytime. Also will see all the results &amp; goals in the same way on the Optimizely UI as she would using their client side library.</p><p>* Add variations to the codebase manually<br>* Use Optimizely UI for results analysis and managing active experiments<br>* Use Optimizely UI for segmenting experiments based on the tools we have available for our account<br>* Node.js connects to [Optimizely REST API](<a href="http://developers.optimizely.com/rest/getting-started/index.html">http://developers.optimizely.com/rest/getting-started/index.html</a>) to get current active experiments &amp; the variation needed to serve for the specific user<br>* Browser application will push the results to Optimizely via the [JavaScript API](<a href="http://developers.optimizely.com/javascript/introduction/index.html">http://developers.optimizely.com/javascript/introduction/index.html</a>)</p><h4>Using GA Experiments</h4><p>Seems like GA is getting in the AB testing game and we could use the same analytics account to create and analyize experiments. This definitely needs a bit more research from us on the GA side, but this looks promising:</p><p>* [Google’s New Content Experiments API Turns Google Analytics Into A Full-Blown A/B Testing Platform<br>](<a href="https://techcrunch.com/2013/06/04/googles-content-experiments-api-a-b-testing/">https://techcrunch.com/2013/06/04/googles-content-experiments-api-a-b-testing/</a>)<br>* [Google Analytics Experiments API](<a href="https://developers.google.com/analytics/solutions/experiments">https://developers.google.com/analytics/solutions/experiments</a>)<br>* Add variations to the codebase manually<br>* Use GA for results analysis and managing active experiments<br>* Use GA for segmenting experiments based on the tools we have available for our account<br>* Node.js connects to [Optimizely REST API](<a href="http://developers.optimizely.com/rest/getting-started/index.html">http://developers.optimizely.com/rest/getting-started/index.html</a>) to get current active experiments &amp; the variation needed to serve for the specific user<br>* Browser application will push the results to Optimizely via the [JavaScript API](<a href="http://developers.optimizely.com/javascript/introduction/index.html">http://developers.optimizely.com/javascript/introduction/index.html</a>)</p><h3># Readups</h3><p>* [Roll Your Own A/B Tests With Optimizely and React](<a href="http://engineering.tilt.com/roll-your-own-ab-tests-with-optimizely-and-react/">http://engineering.tilt.com/roll-your-own-ab-tests-with-optimizely-and-react/</a>)<br>* [npm react-ab-test](<a href="https://www.npmjs.com/package/react-ab-test">https://www.npmjs.com/package/react-ab-test</a>)<br>* [npm redux-ab-test](<a href="https://www.npmjs.com/package/redux-ab-test">https://www.npmjs.com/package/redux-ab-test</a>)<br>* [npm react-ab](<a href="https://www.npmjs.com/package/react-ab">https://www.npmjs.com/package/react-ab</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6d104f7befb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Our UI To The Next Level]]></title>
            <link>https://medium.com/@milankorsos/ui-next-level-4e9a862077bd?source=rss-1978e73ad70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e9a862077bd</guid>
            <dc:creator><![CDATA[Milan Korsos]]></dc:creator>
            <pubDate>Tue, 20 Jan 2015 18:05:47 GMT</pubDate>
            <atom:updated>2015-01-21T16:08:54.655Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moving our UI to the next level</h3><p><em>This is the first post of our blog series, — the story of building a modern web app.</em></p><p>Building a product is hard, — a balance between writing great code and moving fast. Over the last three years we built <a href="http://usetallie.com/">Tallie</a> from the ground up. It has the right features, looks good, and used by hundreds of companies on a daily basis. We feel good about where we are at right now.</p><p>We are not done yet — perfecting a product is even harder. To deliver the best possible experience we need to solve some exciting engineering problems. For us, this year will be about leveling up our UI and pushing the boundaries of the browsers.</p><h3>Our current stack</h3><p>We started with a clean plate. Only had an idea about the product, but no designs or specifications. No front-end codebase or UI engineering team. We shaped the product along the way, and learned a lot.</p><p>As a first step, we had to pick our front-end stack.</p><h4>CoffeeScript</h4><p>With years of JavaScript experience we understood the strengths and weaknesses of the language. Feeling adventurous, we decided to dive into CoffeeScript instead. The main reason was to help the team write better code by enforcing the right patterns. It also gives us the confidence that the compiled code is syntactically correct. We understood this is a controversial topic, and I’m not saying this is the only, or <a href="https://github.com/raganwald-deprecated/homoiconic/blob/master/2011/12/jargon.md">the right way</a> to build a product. But after 25k lines we are happy with <a href="https://tech.dropbox.com/2012/09/dropbox-dives-into-coffeescript/">this decision</a>.</p><h4>Knockout.js</h4><p>Building a lean startup means not knowing how the product will look in 6 months, especially in the early days. To get started, we built separate pages for the different parts of the product. Later these pages evolved into complex views, handling lots of data and user interactions. To support this multi-page structure, we chose Knockout.js, which is strong at the UI data bindings. Looking back, it made sense to support the lightwave pages and ensure the application UI is always in sync with the data.</p><h4>Libraries / Tools</h4><p>We experimented with a lot of open-source libraries to solve smaller problems. Here is a few that proved to be mature enough for production.<br>- We built our dropdowns and typeaheads on <a href="https://select2.github.io/">Select2</a> and <a href="https://twitter.github.io/typeahead.js/">Typeahead.js</a><br>- We use <a href="http://signalr.net/">SignalR</a> to send down real-time messages to the client side<br>- Our drag and drop and file upload features are built on <a href="http://www.html5rocks.com/en/tutorials/dnd/basics/">HTML5 DND</a> and <a href="http://www.html5rocks.com/en/tutorials/file/dndfiles/">File APIs</a>.<br>- <a href="https://github.com/ServiceStack/Bundler">Bundler</a> compiles, bundles and minifies our CoffeeScript and LESS files<br>- <a href="http://gruntjs.com/">Grunt.js</a> runs our unit tests with <a href="http://mochajs.org/">mocha.js</a></p><p>Over time we learned a lot about these technologies, and how to build a complex web app, — which we are planning to share in the future.</p><p>But <a href="https://medium.com/@addyosmani/javascript-application-architecture-on-the-road-to-2015-d8125811101b">the front-end industry is moving fast</a>, and there is always room for improvement. Here are a few problems we see coming our way this year.</p><h3>Single Page Application</h3><p>To create a more-native-app-like product experience, we are converting to a single page application. This will enable us to create more robust features and make the experience faster.</p><h4>Architecture</h4><p>We are using <a href="http://knockoutjs.com/">Knockout.js</a> — powerful with UI bindings, but the rest of the code is on us. A single page app will need a more robust architecture. Either powering up our current view layer, or introducing a new framework for this. Finding one that plays well with the current codebase will be tricky, but not impossible. <a href="http://durandaljs.com/">Durandal.js</a> feels like an obvious choice, since its built on Knockout. <a href="http://eisenbergeffect.bluespire.com/all-about-angular-2-0/">Angular 2.0</a> looks promising, having the best of Durandal and <a href="https://angularjs.org/">Angular</a>. <a href="https://github.com/facebook/flux">Flux</a> has an interesting concept, and the Facebook libraries look really strong. We need to pick the one that fits our current architecture the most.</p><h4>Dependency injection</h4><p>JavaScript and CSS adds up, and you can’t just load 50MB of assets on page load. <a href="https://github.com/ServiceStack/Bundler">Bundler</a> is breaking these assets to smaller bundles, but we are not happy with it. It is not supporting SourceMaps, hard to fit in our Grunt flow and we will need to load assets on the fly. Our options are moving to <a href="http://requirejs.org/">RequireJS</a> or <a href="http://browserify.org/">Browserify</a> to support the single page architecture.</p><h4>CSS</h4><p>Took us 25k+ lines of <a href="http://lesscss.org/">LESS</a> to get to the current product — a lot of styling. And a customized Bootstrap 2.3. While there are best practices for complex JS apps, not that many for structuring styling. It will be quite a journey to get our LESS codebase under control again, and upgrade to the latest <a href="http://getbootstrap.com/">Bootstrap</a>.</p><h4>Node.js</h4><p>Our back-end is built on the .<a href="http://www.asp.net/mvc">NET MVC framework</a>, which serves us well. But on page load you have two options — use Razor templates, or dump the data in a JSON and let Knockout display it. While this second way speeds up development, causes some delay on every page load. With Node.js we could use the Knockout templates to render the HTML on the server side.</p><h3>Quality</h3><p>We all strive for a smooth product experience. Quantifying quality is challenging but there are things we can improve on.</p><h4>Stability</h4><p>Eliminating all the bugs is hard when moving fast — but better tests can help with it. We already have unit tests for data models; the tricky part will be to expand these to the views. To improve the code coverage we are implementing TDD in the team. We are also adding automated UI tests for more confidence when shipping the code.</p><h4>Performance</h4><p>We deal with a lot of data — that is pushing the limits of the browsers. To build a fast product we are constantly working on eliminating the performance bottlenecks. We have work to do on both the CSS and the JavaScript side, — and need to be wise about what data to render.</p><h4>Tablets</h4><p>The best way to get receipts into Tallie is to use our native iPhone and Android apps. Our users do everything else on a computer, that’s why we tailored that experience. But we understand this is changing and more people will use it on the road. We need to make sure our tablet experience is as smooth as using it from desktop.</p><h4>Static Typing</h4><p>Dynamic typing makes JavaScript a powerful language, but after a certain size, things get tricky. While CoffeeScript is doing a great job hiding some shortcomings of JS, but this one is not solved. Our <a href="https://twitter.com/korsosm/status/517178040078856193">friends at Facebook</a> just open sourced <a href="https://code.facebook.com/posts/1505962329687926/flow-a-new-static-type-checker-for-javascript/">Flow</a> that brings static typing to JavaScript. Although Flow is not playing well with CoffeeScript yet, this is definitely an interesting area to look into. Introducing static typing in our codebase will result in less bugs.</p><h3>Team</h3><p>As the front-end team grows we need to enhance our processes to foster learning and improve productivity.</p><h4>Environment</h4><p>Currently Bundler and Grunt split the tasks during the deployment flow. Our plan is to push Grunt.js into the spotlight — compile, minify, bundle and lint code, run unit and automated tests and generate docs. We are also moving all our libraries over to <a href="http://bower.io/">Bower</a> and <a href="https://www.npmjs.com/">npm</a> for an easier maintainability.</p><h4>Code Review</h4><p>We have regular code reviews but we need to involve them more in our daily routine. We believe code review can turn into the most important step for writing quality code, and learning from each other.</p><h4>Documentation</h4><p>As we grow more and more engineers asks the same questions — starting a code style guide will help with this. We are a big fan of productivity: no one has time to write docs — well commented code should speak for itself. That said, there are couple of good tools to auto generate docs from code comments that we need to explore and incorporate.</p><p>There is <a href="https://github.com/lukehoban/es6features">much</a> <a href="http://www.html5rocks.com/en/tutorials/es6/promises/">more</a> <a href="http://www.html5rocks.com/en/tutorials/workers/basics/">cool</a> <a href="http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom/">stuff</a> <a href="https://www.meteor.com/">out</a> <a href="http://momentjs.com/">there</a> for front-end engineering these days. <a href="https://www.youtube.com/watch?v=DqMFX91ToLw">And even better improvements are coming with ES7.</a></p><p>But we are not there yet. We don’t have time to rewrite code just for the sake of rewriting code. Our story is about to find <em>the right way</em> to make our UI a magnitude better. Please join us for this exciting journey.</p><p>Follow me <a href="http://twitter.com/korsosm">@korsosm</a> for more updates.</p><p><a href="https://www.linkedin.com/jobs2/view/25832883">We are also hiring if any of this gets you excited.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e9a862077bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>