<?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 Kristoffer Eckhoff on Medium]]></title>
        <description><![CDATA[Stories by Kristoffer Eckhoff on Medium]]></description>
        <link>https://medium.com/@Doff3n?source=rss-27dfe33a0471------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sLbCixn5lmh8hg5s.jpg</url>
            <title>Stories by Kristoffer Eckhoff on Medium</title>
            <link>https://medium.com/@Doff3n?source=rss-27dfe33a0471------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:19:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Doff3n/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[How do you spot a 0.5x engineer?]]></title>
            <link>https://medium.com/@Doff3n/how-do-you-spot-a-0-5x-engineer-2bbc3b1afee3?source=rss-27dfe33a0471------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bbc3b1afee3</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Kristoffer Eckhoff]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 08:46:30 GMT</pubDate>
            <atom:updated>2019-07-19T08:46:30.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*mewz_KZKX9UUTX5g.jpg" /><figcaption>Thanos in “Avengers: Infinity War” should read this</figcaption></figure><p>Managers if you ever come across this rare breed of engineers, grab them. If you have a 0.5x engineer as part of your first few engineers, you increase the odds of your startup success significantly. OK, here is a tough question.</p><p>How do you spot a 0.5x engineer?</p><ol><li>0.5x engineers encourage other team members and face problems together with them. They may discuss a lot and by all means fight over a solution, but then shake hands and are happy after the discussion that they found a good solution together with the team.</li><li>0.5x engineers listens to their colleagues. Hears them out and discuss solutions. If they do not understand what the other part is trying to say, they ask questions humbly. And try to in a most open way to see the team-members perspective. Sometimes the 0.5x engineer is wrong.</li><li>0.5x engineers are patient. Towards themselves because they give themselves time to learn and understand the problem. And the same applies to others. They see that often time is needed to synchronize ideas, understand each other and then face the problems together.</li><li>0.5x engineers may pick some fights, or they may not because they have a stomach for avoiding conflict. 0.5x engineers could get into a conversation and the conversation can get a bit heated, but not to worry, the next day you may spot that the 0.5x engineers are working together and happily so!</li><li>0.5x engineers adapt their language to who they talk to. Sometimes they fail explaining things and you may spot them jumping up to draw on a board to illustrate what they are trying to say.</li><li>0.5x engineers are proud of all the stuff they need to think about. The complex domains and problems that they need to translate through their brain and then out into code as a product. Sometimes 0.5x engineers are wrong and can not see a good solution to a problem before going through multiple iterations over time.</li><li>0.5x engineers use their time about 50% of the time to do some engineering: Developing code or doing technical tasks. They are studying turning to books, articles, API documentation or using something called StackOverflow. You can spot a 0.5x engineer by looking at their keyboard and seeing worn out ctrl, c and v keys.</li></ol><p>So in other words only about a half of an engineer is enough. That’s it!</p><p>ps. I am happy to get some input on this article, it is written as sarcasm in the aftermath of the 10x developer post on twitter found here: <a href="https://twitter.com/skirani/status/1149302828420067328?source=post_page---------------------------">https://twitter.com/skirani/status/1149302828420067328</a>! Reach me on Twitter @Doff3n or comment below. Thumbs up multiple times if you like the article, thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bbc3b1afee3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The humble developer]]></title>
            <link>https://medium.com/@Doff3n/the-ten-commandments-for-being-a-good-and-humble-developer-and-making-a-career-4e394973902d?source=rss-27dfe33a0471------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e394973902d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[soft-skills]]></category>
            <dc:creator><![CDATA[Kristoffer Eckhoff]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 00:02:34 GMT</pubDate>
            <atom:updated>2020-03-26T23:27:40.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wbhBpF8R2QzLQlwq6JhZKw.jpeg" /></figure><blockquote><em>I have in recent years experienced both ups and downs. Mostly ups, but some downs as well that I hope to have learned from. I wrote this article in summary of my career. It presents some of my thoughts on what I think makes a good and humble engineer. This is one of my first articles of this kind, so I would love some feedback and discussion on this topic!</em></blockquote><h4>1. Be visible</h4><p>One of the best tips I have got from a mentor is to be visible. This is also hyper relevant in the age of home offices. Talk to people and have fun at work. Walk over to other developers and ask them what they are working on and how they are doing. Do a presentation on a small topic that you learned about, or talk about it during lunch. Try to learn something together, discuss it. Then next time you meet say hi do some smalltalk about the weather. It is hard to define this one, but maybe try to be a little bit more forward leaning than you might want to think that you are, so that you challenge yourself and are visible without showing off</p><h4>2. In other words do some networking</h4><p>Another pro tip that I also want to put creds to to another mentor is that there is a lot of value in networking. At first I thought that the statement is overrated. Then I found that most of my projects have had a link to someone I have met previously in my career. And meeting people throughout my career has been the best part of it. But don’t just go to a social event just to be visible and network, that can be a rookie mistake. But rather find a fine balance between where you think that going to a social or learning event is important for you, and that you can actually learn something and get some value from the event.</p><h4>3. Try to be a goto guy</h4><p>Try to learn a lot about something that interest you well. This is the stuff that you can read about on your bed at 1am when you should be sleeping. Don’t try to learn stuff that you have no interest for, you will probably don’t enjoy being a goto guy then. Soon enough you can be a goto guy which is good because you can help others. For me I found that most developers I have worked with don’t enjoy Cascading Style Sheets so much, but that is a goto thing that I could happily adress that I want to help others with. In any case just help people if they are stuck, that is always good even though it can be annoying when you are in middle of your super complex train of thoughts.</p><p>☆ I think point 1.,2. and 3. sums up a trinity that can kickstart your career. The next few points are more on how you should act towards colleagues.</p><h4>4. Be a good colleague</h4><p>Help people that are stuck. Always try to leave the path behind you clean. This also goes a bit into networking, you never know when the tables are turned. This means that you should try to give credit to people that deserves it, encourage your team members and face problems together. Discuss a lot and by all means fight over a solution, but then shake hands and be happy after the discussion that you found a good solution together. Do not hold grudges for long, remember it is just work and you are discussing a problem that probably has a better solution to the problem a few years from now. Have fun at work with your colleagues.</p><h4>5. Remember listening is also key in finding the best solutions</h4><p>Listen to your colleagues. Hear them out and discuss solutions. If you don’t understand what the other part is trying to say, then ask questions humbly. And try to do so in a most open way that you don’t understand from your perspective but that you find the solution interesting. In that same manner, don’t dismiss something that you don’t understand.</p><h4>6. Do not be overly critiqueful of yourself and especially not others</h4><p>We might in this article go over being zen mode soon, but joking aside. Being zen is a nice introduction to this part. We usually work with quite complex domains and problems. Which means that our work will sometimes take a lot of time before we produce something. So patience is important, towards you because you need to give yourself time to learn and understand the problem. And the same applies to others, you need to synchronize ideas, understand each other and face the problems together. Do pick some fights, but not all and have a stomach for conflict, but remember that you are most times working as a team. It is most often counterproductive to be overly critiqueful, and this most often happens because of stress and deadlines. There is not much use in pushing it and putting out solutions to problems faster, rather breathe and think.</p><h4>7. Remember that done is better than perfect</h4><p>A mistake that we all have found ourselves doing is often believing we have got the full understanding of a problem, developed it, then presented it to the users only to find out that we need another iteration of work. The faster you can achieve this the better. It is all about failing fast, the faster we fail the faster we learned something new and we have expanded our problem set. So in conclusion take some time to breathe between tasks, think about a good solution, try to understand the problem well, develop it and present it as early as possible to others.</p><h4>8. Adapt your language to who you talk to</h4><p>Don’t use your language or technical expertise in order to impress others, rather try to adapt to situation and whom you’re talking to. Don’t beat yourself up over that someone doesn’t understand you. Try to express yourself in other ways or try to learn other ways to formulate yourself. Or even jump up to draw on a board to illustrate what you are trying to say. Communication is really important in what we do, probably about 50% of what we do.</p><h4>9. Get some actual skills</h4><p>This should then be about 50% of what you otherwise do as a software developer: Developing code or making something technical. Studying books, articles and then going hands on are all good ways to learn and acquire some skills.</p><h4>10. Be proud of your work</h4><p>Be proud of all the stuff you need to think about. The complex domains and problems that you need to translate through your brain and then out into code as a product. Our work is one of craftsmanship, be it some artful CSS or a well crafted backend API.</p><p>That’s it! Happy coding! And I am happy to get some input on this article! Reach me on Twitter <a href="https://medium.com/u/27dfe33a0471">Kristoffer Eckhoff</a> or comment below. Thumbs up multiple times if you like the article, thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e394973902d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The .Net Core 2.2 framework roadmap and some of my views]]></title>
            <link>https://medium.com/@Doff3n/the-net-core-2-2-web-framework-roadmap-and-some-of-my-views-what-we-can-expect-to-see-8c51f71b834b?source=rss-27dfe33a0471------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c51f71b834b</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[dotnet-core]]></category>
            <dc:creator><![CDATA[Kristoffer Eckhoff]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 21:34:53 GMT</pubDate>
            <atom:updated>2018-07-01T16:02:54.466Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*bqzcMnWHRdgGFUEHpeHZOA.png" /></figure><p>.NET Core is a cross-platform, high-performance, <a href="https://github.com/dotnet/core">open-source</a> framework for building modern, cloud-based, Internet-connected applications. I have been working with <a href="https://github.com/dotnet/core/releases/tag/1.0.0">.NET Core</a> since the first 1.0 release, and have seen it maturing since. There have been some ups and downs from a software developer point of view, such as the project.json to csproj migration, poor support among related libraries you would want to use with .NET Core and some API changes along the way. But whilst not forgetting that all along the way there was some pretty awesome performance, always clean uses of the API, pretty neat and clean middleware piping and built in dependency injection possibilities.</p><p>.NET Core 2.1 is already out and provides the following features:</p><ul><li><a href="https://docs.microsoft.com/en-us/aspnet/core/signalr/?view=aspnetcore-2.1">SignalR</a> — Add real-time web capabilities to your ASP.NET Core apps.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/mvc/razor-pages/ui-class?view=aspnetcore-2.1">Razor class libraries</a> — Use Razor to build views and pages into reusable class libraries.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-2.1">Identity UI library &amp; scaffolding</a> — Add identity to any app and customize it to meet your needs.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-2.1">HTTPS</a> — Enabled by default and easy to configure in production.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/security/gdpr?view=aspnetcore-2.1">Template additions to help meet some GDPR requirements</a> — Give users control over their personal data and handle cookie consent.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/testing/integration-testing?view=aspnetcore-2.1">MVC functional test infrastructure</a> — Write functional tests for your app in-memory.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/web-api/index?view=aspnetcore-2.1#annotate-class-with-apicontrollerattribute">[ApiController]</a>, <a href="https://docs.microsoft.com/en-us/aspnet/core/web-api/action-return-types?view=aspnetcore-2.1#actionresultt-type">ActionResult&lt;T&gt;</a> — Build clean and descriptive web APIs.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/fundamentals/http-requests?view=aspnetcore-2.1">IHttpClientFactory</a> — HttpClient client as a service that you can centrally manage and configure.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-2.1#transport-configuration">Kestrel on Sockets</a> — Managed sockets replace libuv as Kestrel’s default transport.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-2.1">Generic host builder</a> — Generic host infrastructure decoupled from HTTP with support for DI, configuration, and logging.</li><li><a href="https://docs.microsoft.com/en-us/aspnet/core/spa/?view=aspnetcore-2.1">Updated SPA templates</a> — Angular, React, and React + Redux templates have been updated to use the standard project structures and build systems for each framework (Angular CLI and create-react-app).</li></ul><p>According to this <a href="https://github.com/aspnet/Announcements/issues/307">roadmap</a> .Net Core 2.2 will further expand on the 2.1 release.</p><ul><li>APIs &amp; Services</li><li>Server improvements</li><li>SignalR</li></ul><p><strong>API Controller conventions</strong></p><p>It looks like there will be further improvements and an even more convention based scheme when building web APIs: “In 2.1 we added controller specific conventions that make Web API development more convenient with the <a href="https://docs.microsoft.com/en-us/aspnet/core/web-api/index?view=aspnetcore-2.1#annotate-class-with-apicontrollerattribute">ApiController attribute</a>. In 2.2 we want to expand on this concept to provide metadata for API Explorer and provide a better end-to-end API documentation experience”.</p><p>This is nice since currently the controllers I write are quite decorated, so I hope to see less decoration and a litte bit more convention. And I like the idea of analyzing code with conventions over attribute declaration, it is pretty much just boilerplate anyways. With these conventions the roadmap also announce that a feature where code will generate Open API documents is planned. And that these will be better by default, since the code will either follow the conventions or have attributes allowing generators to create better documents.(And tooling will be better)</p><p><strong>API client generation (C# &amp; TypeScript)</strong></p><p>In many projects I have been doing this: “Once you have an API with rich metadata and done exploring and testing it, then you need to go and write some client code to call and make use of your API. We are going to build an experience for generating this code based on the same data and documentation described above.”. From the conventions the .Net core teams envisions that they could also generate API clients from CLI or tooling</p><p><strong>Routing system(Dispatcher)</strong></p><p>A new routing system will be introduced. And we can expect improvements to the performance of routing and dispatching for MVC and other scenarios. And a more integrated way of configuring CORS it seems, instead of writing a custom pipeline middleware.</p><p><strong>Authorization Server</strong></p><p>We can expect a simple to use OpenID Connect based authorization server integrated into .Net core it seems. With support for a range of different and broad covering scenarios: web site to API, SPA to API, native application to an API or, for distributed applications API to API. The roadmap also points out that a lot of this should be “simple to use”, “make the code you need to plumb in trivial”, “getting as close to zero configuration as you can”. Which all sounds nice. This has been a little bit of a hassle, and I hope to see some well documented and modern use cases for SPAs for instance using the <a href="https://github.com/IdentityModel/oidc-client-js">oidc-client</a> library. This feature will be directly competing with IdentityServer 4 and this has spun up some discussion which has spun up some discussions in recent days.</p><p><strong>Server Improvements</strong></p><p>A health check feature is planned. HTTP/2 is announced to be added in Kestrel &amp; HttpClient. And a plan to run ASP.NET Core applications in-process in IIS seems to be set, giving a significant performance boost.</p><p><strong>SignalR</strong></p><p>Expands on the previous release it seems, now allowing customers using Java or C++ to connect to SignalR servers, and the <a href="https://azure.microsoft.com/en-us/blog/azure-signalr-service-a-fully-managed-service-to-add-real-time-functionality/">Azure SignalR Service</a>.</p><p>And as always bug fixes.</p><p>We can expect the release to be done, alongside <a href="https://github.com/aspnet/Announcements/issues/308">a small release of EF Core 2.2</a>, by the end of the year.</p><p>If you have been sitting on the bench waiting for the library to mature I would say that there is no more waiting. Now with .Net Standard support since 2.0 there should also be a wide range of library support.</p><p>Did I miss something? Hit me up on twitter at <a href="https://twitter.com/Doff3n">Doff3n</a>. I am always eager to discuss and learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c51f71b834b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frontend Web-app battles — Tech predictions for 2017 #tech2017]]></title>
            <link>https://medium.com/@Doff3n/frontend-web-app-battles-tech-predictions-for-2017-tech2017-22e548d633f1?source=rss-27dfe33a0471------2</link>
            <guid isPermaLink="false">https://medium.com/p/22e548d633f1</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kristoffer Eckhoff]]></dc:creator>
            <pubDate>Fri, 31 Mar 2017 11:13:24 GMT</pubDate>
            <atom:updated>2017-03-31T11:13:24.176Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a tech survey of the current state of the Art in the field of Web Apps development, somewhat influence by my own experiences this last year. It is a follow up post to my previous article called <a href="http://www.linkedin.com/pulse/frontend-battles-tech-predictions-2016-tech2016-eckhoff?trk=mp-reader-card">Frontend Web battles — Tech predictions for 2016 #tech2016</a> where I compared a lot of framework and tools early in 2016.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxLC26O5aOOi-1eOr5YlJg.png" /></figure><p>Much have happened in 2016. After node.js and io.js settled their differences and merged back together this became the year of Javascript fatigue. One developer broke Node, Babel and thousands of other projects in 11 lines of JavaScript by pulling a package from npm in protest, demonstrating that more power now lies in the open source domain compared to previously in traditional corporates.</p><p>Looking back now and then it is interesting to see the development, a lot more has changed than I anticipated, even when I anticipated that there would be a lot of change with the innovation speed in the JavaScript world</p><p><strong>Gulp vs. npm scripts &amp; Webpack</strong></p><p>Last year I wrote about Gulp vs grunt where I concluded that Gulp was gaining grounds on grunt. Now in 2017 it is really interesting to see that Gulp has not only made grunt irrelevant, but Gulp is becoming irrelevant too in favor of npm scripts in combination with Webpack. With npm scrips the tasks that you would normally put in your Gulpfile are now executed from packages through npm commands. The commands are really just wrappers around other commands, but it even so makes for less configuration than setting up and configuring a lot of Gulp. It also hides away implementation details and I would argue that it makes it easier to update your tooling because you update packages (and sometimes some configuration) rather than updating your gulp script with the latest tooling.</p><p>With all the JavaScript fatigue in 2016 we now luckily as a result have a lot of tools available. npm scripts with Webpack is the defacto standard(For now) for setting up bundling, testing and linting of you code. You can bundle all your JavaScript, HTML5, icons, fonts and Sass into one bundle with Webpack, and you can also lint your JavaScript, HTML and Sass, in addition to generating fonts from icons. All with npm scripts and bundling them with Webpack where you used to use gulp(or grunt) to build and Browserify to bundle your files. Webpack can also spin up a dev server for you running on the node.js platform, where you can write your code, save and the browser will “hot reload” the new code into view. In addition to doing minification and transpilation of Sass to CSS3 as well as ECMAScript to JavaScript.</p><p><strong>Angular vs. React vs. Aurelia</strong></p><p>Angular 2.0 was released in September 2016 and has since then gained some adoption. I still have my finger on React, I prefer React’s cleaner approach in favor of Angulars framework approach where you have to learn a lot of Angular specific syntaxes. React has improved so much since 2016 and especially with ECMAScript 2017. Writing modern React in 2017 feels like writing object oriented code, with import, classes, annotations, asynchronous programming async/await and other language features, with added neat functional programming features like map, filter and reduce. It will take some time before Angular 2.0 has been proved, at least for me.</p><p>I also want to mention Aurelia. Aurelia is kind of a spin-off off Angular. One of the main developers is Rob Eisenberg that jumped ship on Angular 2 and instead is creating this framework. Aurelia is a framework like Angular, where you create HTML with specialised Aurelia notation that renders dynamic HTML. ECMAScript(Or higher level languages like TypeScript) is supported out of the box. Aurelia in my opinion seems to be more explicit in the way the dynamic HTML is rendered, instead of using ng tags and other angular notation the HTML code is more self-explanatory in Aurelia.</p><p>Nevertheless I still prefer React. I personally like the react philosophy better: Seperating JavaScript and HTML is not a seperation of concerns but rather a seperation of technologies.</p><p><strong>Sass vs. Less</strong></p><p>Sass is now the de facto standard when it comes to developing Stylesheets. Bootstrap 4 is adopting Sass in its next version and leaving Less behind, and so are many others. The Sass community has more momentum than ever now so we can more or less(pun intended) officially declare Less dead and say that Sass has won.</p><p><strong>.NET Core vs. node.js server</strong></p><p>Microsoft is doing a lot of interesting stuff this last year. I am from the Microsoft world so I prefer .NET and C# for backends and for creating REST Apis etc. I would argue that Microsoft technology is becoming very relevant for everyone with the release of .NET Core. .NET Core is a general purpose development platform maintained by Microsoft and the .NET community on <a href="http://github.com/dotnet/core">GitHub</a>. It is cross-platform, supporting Windows, macOS and Linux, and can be used in device, cloud, and embedded/IoT scenarios. The community has also recently been porting the platform to ARM(Raspberry Pi, Chromebook) and Android. And lots of work is being done in the .Net core community on Docker.</p><p>Which sums up Microsoft’s new mantra:</p><blockquote>Any Developer. Any App. Any Platform.</blockquote><p>.NET Core has made .NET simpler to work with, yet powerful. It is possible to create everything from a static fileserver serving your Web app to go more in depth with hooking yourself up on the request pipelines or creating robust Web API’s. Going even further there are <a href="http://osoft.com/webdev/2017/02/14/building-single-page-ap">JavascriptServices</a> in .NET Core where you can setup everything from Webpack, HMR, Server-side prerendering and other dev middlewares.</p><p>Performance is also great in .NET Core. Requesting plaintext on ASP.NET Core hits 1,822,366 RPS. As comparison node.js is at 467,246RPS.</p><p><strong>ECMAScript vs. TypeScript</strong></p><p>With Babel you have the possibility to “transpile” ECMAScript to JavaScript, meaning you can write ECMAScript and it is transformed into JavaScript which is supported by your browser. Webpack helps in that it uses Babel and packs the JavaScript and serves it readily bundled to your browser.</p><p>ECMAScript has as mentioned before in this article improved a lot in the last year and is starting to look a lot like TypeScript. The only favor of using TypeScript as I see it now is that it is typed, and maybe the fact that you get the possibility to create interfaces for your classes. If the only reason that you are using TypeScript is because you feel more comfortable in Visual Studio and that the fact that Visual Studio 2015 has limited support for ECMAScript you should reconsider using it and wait for the new Salsa JavaScript engine for Visual Studio 2017 which supports newer ECMAScript.</p><p><strong>Git vs. Github pull requests</strong></p><p>I have been using Git and Github for a while now. I only have one thing to say here for now. If you are not using Pull request yet, this is the first thing that you need to take from this article and implement in your team. Github offers a great way of doing Pull requests, both for private and public repositories. In addition there is Visual studio team services and multiple other tools for handling pull requests.</p><h3>This is a follow up post to my previous article called <a href="http://www.linkedin.com/pulse/frontend-battles-tech-predictions-2016-tech2016-eckhoff?trk=mp-reader-card">Frontend Web battles — Tech predictions for 2016 #tech2016</a></h3><p>Did I miss a crucial battle? Contact me on Twitter <a href="http://twitter.com/Doff3n">@Doff3n</a> or comment below! I love to hear you input on anything in this article, and I am always eager to learn and discuss. Maybe my views are different than yours? Visit my Website for more information about me: <a href="http://keckhoff.com/">keckhoff.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22e548d633f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>