<?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[devtrails.io - Medium]]></title>
        <description><![CDATA[A collection of helpful guides for software developers. - Medium]]></description>
        <link>https://medium.com/devtrailsio?source=rss----94ee056dfbbb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>devtrails.io - Medium</title>
            <link>https://medium.com/devtrailsio?source=rss----94ee056dfbbb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:23:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/devtrailsio" 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 to Become a Better Software Developer]]></title>
            <link>https://medium.com/devtrailsio/how-to-become-a-better-software-developer-dd16072c974e?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd16072c974e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 06:06:01 GMT</pubDate>
            <atom:updated>2021-02-14T06:50:11.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qwohYdwnhpBRetPz" /></figure><p>Today I would like to share some thoughts on ways a software developers can improve their professional skills and become better at their work. The topics raised here are universal and not specific to any technology stack. Most of them are not even specific to IT, for that matter. These are general advice on how to develop your personal traits, improve collaboration with colleagues and clients, and advance your career as a software developer.</p><p>Some of the things in this article are subjective and reflect my personal experience, while others have been adopted and successfully used by others.</p><h3>Understand the Process End to End</h3><p>A lot of developers think that software development is all about coding, and everything else is just people trying to be annoying and wasting their precious time. This cannot be further away from the truth. Before you get to code a piece of software, it undergoes a process of transformation from a vague idea into a carefully designed solution ready for implementation. And after you pushed your latest changes into Git the software is being tested, deployed, monitored, analyzed and improved on. Coding is just one of the many steps of the process.</p><p>So why does this happen? Frequently, especially when working in larger organizations, different phases of the projects are handled by different teams or even departments. It all starts with the business analysts, who gather requirements. The requirements are then handed over to the designers that produce the mockups for developers. The developers code away and give the results to the QA engineers. If everything is OK, the artifact is sent to the operations teams that deliver it to the end users. This process is treated as a set of discrete steps without any feedback. Because of the lack of communication between the departments, their representatives often don’t really understand the goals of others and this leads to misunderstandings and even conflicts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*uopAQIIDTmn_bOpjP1-7Jg.png" /><figcaption>Often the process of software development is treated as a set of discrete steps with no feedback.</figcaption></figure><p>For many people nowadays this might sound too exaggerated. With the rise of agile methodologies, more companies move away from such a rigid approach towards smaller teams consisting of people of mixed specialty. But even then we see that people don’t really try to understand the work of others. How often have you been irritated with your designers because they want you to implement a custom checkbox that is just too time-consuming? And vice-versa, received criticism, because you forgot to use the correct font.</p><p>A lot of these differences can be overcome by just paying attention to the work of others. Sit down with your designer and explain him, that implementing a custom checkbox takes a while and that there’s a library that offers a different similar checkbox you could reuse. In return, learn the basics of typography and understand why choosing a correct font makes a difference. Develop the same attitudes toward managers, business analysts, QA engineers, support and marketing specialists. Quoting T. Huxley:</p><blockquote>Try to learn something about everything and everything about something.</blockquote><p>By learning something from everybody, you will be able to anticipate their needs, shorten the feedback loop and enable more frequent deliveries. Plus it will earn you a lot of love and respect from everybody else.</p><h3>Understand Your Client’s Needs</h3><p>There’s one important thing that you need to understand about your customers: they don’t understand most of the stuff that you’re doing. Agile, functional programming or non-relational databases is all dark wizardry to them. Even the ones that closely follow your work and are genuinely interested are still mostly in the dark. This has a couple of consequences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ES8_YPPSeqXt93e1Qqa7Q.jpeg" /><figcaption>The face of most clients when talking to software developers.</figcaption></figure><p>Hiring software developers for them requires a certain degree of trust. People often tend to feel uncomfortable about having to pay a lot of money for something they don’t understand. Remember last time you walked into an unfamiliar car repair service and weren’t sure if you could trust them with your ride? Well, your clients have the same feeling. Except there’s no car, there’s just a whole bunch of abstract non-tangible concepts which are supposed to somehow materialize into products and revenue. When working with new clients it’s important to earn their trust. Make sure they understand how you operate and aim to deliver results in smaller but frequent iterations. That way they can see the progress of your work, assess the intermediate results and provide their feedback.</p><p>Often clients tend to come up with their own solutions instead of sharing their problems. Since they have little idea of your capabilities, their solutions are often misjudged, under- or overambitious. Remember the old (and maybe fictional) quote by Henry Ford:</p><blockquote>If I had asked people what they wanted, they would have said faster horses.</blockquote><p>Instead of going with the flow and silently implementing whatever the client wants, it’s sometimes useful to invite them to take a step back and discuss the problem that they wanted to solve in the first place. When combining their domain knowledge and your technical expertise, you’re are likely to arrive at a better solution.</p><p>Keep in mind, that not everybody likes having their ideas questioned and this tactic requires you to have some tact and inspire confidence in the client’s eyes. You will also need to leave your comfort zone and immerse yourself in their business, to be able to understand the problem and suggest a better solution. This can be challenging if you’re are working in complex industries such as finance or health care. But if you pull this off once, it’s likely that next time the client will return with a more open mind.</p><h3>Pick the Right Tools for the Job</h3><blockquote>If all you have is a hammer, everything looks like a nail.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e4nQP3c7U8UThDohaICMRg.jpeg" /></figure><p>Often developers that learn only a single technology rush to apply it to every problem they encounter. Unsurprisingly, this kind of approach leads to sub-optimal results. Instead, when tackling a new problem, pause and think whether the tools at your disposal are really suitable for this kind of work. If you have doubts, investigate a bit and come up with a list of likely superior alternatives. To make it easier, compile a list of questions and assess different options one by one. The questions can be different for each assessment, but it can go along the way of:</p><ul><li>What platforms or devices must it support?</li><li>What are the non-functional requirements, such as performance or memory usage?</li><li>Is buying a license an option, or do you need something free or open-source?</li><li>Does the solution provide everything you need out of the box, or will you need to write something yourself?</li><li>Do you have any other limitation, like company policies, legal considerations or a lack of specialists in your team?</li></ul><p>Answering these questions should help you structure the options in your head and narrow them down to a shortlist of candidates.</p><h4>Experiment Safely</h4><p>So what happens if you none of the things you know are a particularly good fit in your case and you want to try something new? The fact that you don’t experience with something doesn’t automatically mean that it’s out of the question. It just means that you need to consider some additional things:</p><ul><li><strong>Do you have enough time for preparation?</strong> If the timeline of the project is not stressful, you can learn as much as possible before you begin the implementation and pick up the rest along the way. Or at least adopt the “<a href="https://en.wikipedia.org/wiki/Fake_it_till_you_make_it">fake it till you make it</a>” approach and convince the client that you know what you’re doing.</li><li><strong>Identify the things you need to test first.</strong> Take the “<a href="https://en.wikipedia.org/wiki/Fail-fast">fail fast</a>” approach and identify the crucial things that you need to evaluate before you can conclude the experiment. Having doubts about the performance of a system? Build a minimal prototype and run a load test. Uncertain about a particular library or integration with an external service? Implement that separately and then build the rest.</li></ul><p>Keep in mind that going down this road is still risky both for you and your client, and they need to be aware of both the risks and the potential benefits. After all, a two-week investigation that might save months of work in the long run, this sounds like a pretty good deal. Even if the experiment fails, you only lose two weeks. The more trust you have with your client, the more they are likely to agree to something like this.</p><h3>Build on the Shoulders of Giants</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*kpy7gmiapS0xWDlxdtpg5Q.jpeg" /><figcaption>Reinventing the bicycle often leads to weird results.</figcaption></figure><p>IT people often have two common characteristics: we are inventive and we enjoy our work. This sounds like a good thing, but it comes with an awkward side-effect: we tend to come up with our own solutions to problems that have been solved before. So whenever we’re faced with a choice of whether to use a framework, library or service or to implement it on our own, we tend to choose the latter. And this takes us on the futile journey of reinventing the wheel. Some of the common misbeliefs that lead to this are:</p><ul><li><strong>Implementing something yourself is easier than learning a 3rd party solution.</strong> While this may be a perfectly valid reason, it’s important not to oversimplify the task at hand. Often, something seems simple in the beginning but turns out to be much more difficult with progress. Eventually, you could end up spending a whole bunch of time handling bugs and edge cases that someone could have handled for you.</li><li><strong>This solution does more things than I need.</strong> Unless there are specific reasons why this is a bad thing, such as increasing the size of the resulting artifact, adding potential vulnerabilities or considerably slowing down the build, this is not usually a bad thing. You might end up needing it later. On the other hand, adding a whole library to use just one function might be an overkill.</li><li><strong>We can do it better.</strong> Although there are some successful projects that started with these words, this is not usually the case. Quality third part solutions are maintained by teams that have experience and resources devoted to solving this particular problem. To compete with them you need to be able to invest even more. Most projects have neither the resources nor the need to do that.</li><li><strong>Code ownership and long-term maintenance will become a problem.</strong> Some people fear that if you go with a third party solution, you risk that the project at some point might become abandoned or unusable for whatever reason. The risk of product lock-in is real, and you should consider a possible mitigation strategy. If it’s an open-source project, would it be possible for you to fork it and maintain by yourself? Or if it’s a proprietary project, how much would it cost to replace it? Based on these inputs you can make a conscious decision on whether it’s worth the risk.</li></ul><h4>Learn Through Reimplementing</h4><p>There’s another side to this story. Reimplementing something yourselves is actually a great way to learn. While writing your own framework for a production project is almost always a bad idea, creating it as a learning exercise can be highly valuable. What better way to familiarize yourself with the problems that it solves by taking a crack at the same problems. Don’t go too deep into the rabbit hole, a simplified crude implementation will be enough to give you an understanding of the situation.</p><p>While you’re at it, don’t shy away from peeking into the sources of similar projects. Studying the code of open-source projects will allow you to benefit from the experience of more seasoned developers.</p><h3>Work on How You Work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*H12xfmhBOBKXtIG02uE7Qw.jpeg" /></figure><p>Strive for improvements not just in technological aspects, but in methodological as well. Just like properly designed and optimized software, a well-established workflow will allow you to work with fewer effort and stress while producing better results. Establishing an effective and efficient work process is not an easy task and there are numerous books and materials available on this topic. But for a start, consider the following areas for improvements:</p><ul><li><strong>Team and project management methodologies.</strong> Since most of us work in teams, it’s important to adopt a process that improves collaboration and establishes a common work rhythm for everybody. The agile movement in software development has given birth to a number of widely adopted methodologies, such as <a href="https://en.wikipedia.org/wiki/Scrum_(software_development)">Scrum</a> or <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a>. They help organize the overall work structure but don’t cover everything. There are other methodologies that help you make estimates, prioritize issues, improve communication, etc. You’ll need to identify the areas you are struggling with and look for best practices that help address your struggles.</li><li><strong>Personal processes.</strong> Like an orchestra, an effective team must have the same rhythm, but it doesn’t mean that everybody must work in an identical manner. Each person has their own preferences and should work in a way that makes them more productive. For example, a lot of people don’t like to be disturbed for hours when coding, but I, personally, like to work in short one-two hour bursts with breaks in between (a less strict version of the <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">pomodoro technique</a>). I also don’t like to work at home to avoid household-related distractions and prefer to work from an office or a cafe. Find out what works for you and stick to it, but also make sure that your habits don’t create problems for other team members.</li><li><strong>Engineering practices</strong>. A lot of practices lie on the border between technology and methodology and focus on improving the actual development process. For example, <a href="https://en.wikipedia.org/wiki/Test-driven_development">test-driven development</a> and <a href="https://en.wikipedia.org/wiki/Behavior-driven_development">behavior-driven development</a> help keep your code base well structured and tested. <a href="https://en.wikipedia.org/wiki/Code_review">Code reviews</a> help reduce defects in the code and also spread knowledge in the team. <a href="https://en.wikipedia.org/wiki/Continuous_integration">Continuous integration</a> and <a href="https://en.wikipedia.org/wiki/Continuous_delivery">continuous delivery</a> ensure an easier and safer deployment process. Use these practices in combination with other organizational methodologies to achieve maximum results.</li></ul><p>Remember, that there’s no process that will work for everybody, you need to trial it in your own environment. Also, make sure that you understand the process completely and implement it correctly. Seek advice from teams that have already gone through the process and benefit from their experience. Don’t neglect the software and material tools that will help you to adopt a process. Get a real Kanban board and a modern platform for continuous delivery. Adopting a new process will require effort and can even lead to a short-term loss of productivity. Give it some time and then do an evaluation of whether things have improved.</p><h4>Remove obstacles</h4><p>A separate thing has to be said on addressing obstacles. It’s a common mistake to neglect small nuisances that might not seem important but can actually have a toxic effect on your work. Is your product designer sitting in a separate room or building? This means that it takes a bit more efforts to come over and have a conversation and some things will not be discussed. Is writing a new test difficult? Then a lot of things will not be tested.</p><p>None of these things are particularly dangerous by themselves, but they tend to pile up and cause serious consequences. And the nasty thing is, that you often don’t notice them until it’s already too late. Especially when there are always more serious perils to address. Remember the fable about the <a href="https://en.wikipedia.org/wiki/Boiling_frog">boiling frog</a> and the notion of <a href="https://en.wikipedia.org/wiki/Creeping_normality">creeping normality</a>.</p><p>Stay vigilant and fight these things at their roots before they get to you.</p><h3>Focus on the Fundamentals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*raNssSABfnz7ELBs" /><figcaption>Fundamental concepts are the building blocks of your career.</figcaption></figure><p>IT is an extremely fast-paced industry. Every week new tools are released into the market. I’ve already mentioned the infamous “<a href="https://sdtimes.com/softwaredev/is-the-javascript-fatigue-real/">JavaScript fatigue</a>” syndrome in my previous post. A lot of developers have been stressed and felt forced to re-evaluate their JS tech stack with each new project and that drove them nuts. Indeed, always being on the edge can be challenging, but there are a couple of ideas that can make it easier.</p><p>First of all, focus on the fundamentals. Even though new technologies appear quite frequently, new fundamental concepts are much more seldom. When learning something new, make sure you understand the underlying ideas that lead to this implementation. Chances are, these ideas are used in other projects as well, and once you encounter something similar, it will be easier for you to get a grasp of it. For example, modern JavaScript UI frameworks are based on components, and once you understand how to structure a component-oriented application using React, can use this experience when working Angular. In a similar manner ideas of Redux found their way into Angular, and reactive state management from Angular was implemented for React as MobX.</p><p>Take some time to familiarize yourself with the classical books on the topics of common patterns in software development such as “<a href="https://www.enterpriseintegrationpatterns.com/">Enterprise Integration Patterns</a>” by Gregor Hohpe and Bobby Woolf, the famous “<a href="https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612">Design Patterns: Elements of Reusable Object-Oriented Software</a>” by the Gang of Four or different works of Martin Fowler. Although some of the things described in books may be outdated, you can use them to learn how the patterns evolved till today.</p><p>Secondly, don’t rush to learn about every new thing out there. I understand that it’s tempting to follow every new thing that appears on Hacker News, but a lot of these things are just noise. Rather keep an eye out for things that have been circling in the community for some time now and have matured beyond the hype of initial discussions. Don’t give into <a href="https://en.wikipedia.org/wiki/Fear_of_missing_out">FOMO</a>. If you pay at least some attention to what’s going on, no important thing will pass unnoticed.</p><h3>Bonus Tips</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yjalwgh5yLvAjzYA" /></figure><p>We’ve already talked about a lot in this article, but there are a few other points I would like to highlight before we wrap up. These few tips are focused more on your personal traits rather than professional, but I still believe that they have a high impact on your work life.</p><h4>Share the knowledge</h4><p>Often people think that hoarding valuable knowledge will make them indispensable. Having people like this in your team exposes you to the “<a href="https://en.wikipedia.org/wiki/Bus_factor">bus factor</a>” and can put you in a tough spot if such a person were to leave the project. If you are one of these people, consider that in addition to making you indispensable, your expertise also makes you unpromotable and “unvacationable”. You might miss out on other career opportunities in your organization because you are tied up in this role. Instead, share the knowledge with your colleagues, if possible delegate part of your work to them and use this collaboration to build even greater things on top of their work.</p><h4>Don’t blame yourself or others</h4><p>I remember a long time ago we had an incident in one project that was by my mistake. We’ve managed to recover from the incident quite quickly and I remember the client telling me:</p><blockquote>You don’t judge a team by how they perform when everything goes according to plan, but by how they operate when the shit hits the fan.</blockquote><p>No matter how good you are, sometimes things will go wrong and in such moments it’s important to be able to keep your cool and handle the situation with dignity and mutual respect. After the fire is put out, don’t focus on finding the scapegoat. This won’t help you avoid mistakes in the future, but will spear fear and doubt across the company. Instead, come together with the affected parties and do a common post-mortem. Focus on the things that lead to the problem, figure out why it happened and brainstorm on what you can improve your system or workflow to avoid this problem in the future.</p><h4>Don’t be an asshole</h4><p>The developer community is a funny thing. On one side we see a lot of driven open-minded people that contribute to the community by working on open-source projects, giving speeches at conferences or writing articles. On the other side, we encounter people that troll new ideas, disrespect newcomers and demonstrate rude behavior to everyone around them. Don’t be one of those people. Be nice and spread the love.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCWOv2ZfcT4fz7gmdS4YBA.jpeg" /><figcaption>A lot of professional advice can be summed up with just four words.</figcaption></figure><h3>Wrapping it up</h3><p>The best thing about our work is that it doesn’t have a limit. There are always new roads to travel and dragons to slay. Whether you’re just at the beginning of your journey or an experienced professional, keep these things in mind. They should help you find your way and become a better developer with each step taken.</p><p>Do you have different advice to share with others? Feel free to post it in the comments and start a discussion!</p><p>Want to read more on business, people, and IT? Check out other articles at <a href="https://pavelyeliseev.com/">https://pavelyeliseev.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd16072c974e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/how-to-become-a-better-software-developer-dd16072c974e">How to Become a Better Software Developer</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Publishing the Complete “Beginner’s Web Development Guide”]]></title>
            <link>https://medium.com/devtrailsio/publishing-the-complete-beginners-web-development-guide-4b2ad4ecd9f5?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/4b2ad4ecd9f5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Tue, 20 Nov 2018 18:55:22 GMT</pubDate>
            <atom:updated>2018-11-20T18:55:21.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dPoz_K5FkuVJUnuz" /></figure><p>Hey everybody,</p><p>Thank you for the claps and the cheerful comments on the “Beginner’s Web Development Guide” story series that I did some time ago. Just wanted to let you know, that it’s now <a href="https://www.devtrails.io/web-development">available in full at devtrails.io</a>.</p><p>It took some time to make it whole, but I believe that it’s now really ready to help people orientate in the complex world of web development. There are still some things that I’m thinking of elaborating there based on the received feedback, but I will add them along the way.</p><p>In the meantime, I will continue working on new guides and publish helpful stories, so stay with me.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b2ad4ecd9f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/publishing-the-complete-beginners-web-development-guide-4b2ad4ecd9f5">Publishing the Complete “Beginner’s Web Development Guide”</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner’s Web Development Guide Part 4: Cloud Deployment]]></title>
            <link>https://medium.com/devtrailsio/beginners-web-development-guide-part-4-cloud-deployment-82fdcd40d7ef?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/82fdcd40d7ef</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-hosting]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Mon, 05 Nov 2018 06:01:01 GMT</pubDate>
            <atom:updated>2018-11-20T18:57:31.409Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3tkiDAioqlupkh6p" /></figure><blockquote><em>This post is part of a series of posts for beginner web developers. Also check out “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5"><em>Part 1: Frontend</em></a><em>”, “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc"><em>Part 2: Backend</em></a><em>”, and “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-3-platforms-and-tools-46467c4cd033"><em>Part 3: Platforms and Tools</em></a><em>”.</em></blockquote><p>Once you’re done developing your applications, it’s time to deploy it. There are multiple cloud providers that offer all the necessary services to build and deploy your applications, the largest of them being Amazon Web Services, Microsoft Azure and Google Cloud Platform. There are also smaller players that provide more tailored services that can be easier to set up for beginners.</p><blockquote><em>Why clouds?</em> <em>We believe, that deploying an application into a cloud-based service nowadays is the best way to go. Pricewise you might find better offers from local data centers available in your region, but joining a larger cloud provider will grant you access to a lot of modern services and different geographical regions. Unless you have compelling legal or financial reasons to host in a local datacenter, clouds seem like a better alternative.</em></blockquote><p>When we’re talking about application hosting, there are several layers of abstraction you can choose, from <em>infrastructure as a service</em>, meaning virtual machines, disks, and networks, to <em>containers as a service</em>, a high-level abstraction for running containers over a cluster of machines. Lower abstraction levels give you more control over the setup, but also require more work and technical skills to configure, while higher-level services make things easier, often reducing the level of control and transparency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPycRGN5dcQx7K_fLNlWHg.png" /></figure><h3>📒 Infrastructure as a Service</h3><p>Infrastructure as a Service (IaaS) refers to services that allow you to run virtual machines, file systems, and virtual networks. To make onboarding easier, some platforms provide you with pre-configured images of machines built for different purposes, such as an Apache server on Ubuntu or a PostgreSQL server. You can create a VM based on one of those images and then tailor it to your needs, for example, install software, configure networking and setup security and firewalls. Although IaaS gives you the most control over your services, it’s also requires the most efforts to set up. It’s a good choice when you need to host something other than a plain web application.</p><p>Here are some of the popular IaaS services from different providers.</p><ul><li>📒 <a href="https://www.digitalocean.com/"><strong>DigitalOcean</strong></a> is a cloud platform that offers IaaS services in data centers worldwide. Setting up a VM in DigitalOcean is relatively simple, however, it only offers Linux virtual machines. DigitalOcean offers $100 worth of credits for 60 days to try their services.</li><li>📙 <a href="https://aws.amazon.com/ec2/"><strong>Amazon EC2</strong></a> is the Amazon’s IaaS offering and a leader in the overall market share. EC2 offers different kinds of virtual machines with flexible configuration, however, the initial setup can be more challenging. It offers a free 12 month tier for some of the smaller VM types.</li><li>📙 <a href="https://azure.microsoft.com/en-us/services/virtual-machines/"><strong>Azure Virtual Machines</strong></a> is an IaaS offering from Microsoft with a large number of pre-configured images. Microsoft offers $200 worth of credits for one month and 750 hours of small VM’s for 12 months.</li><li>📙 <a href="https://cloud.google.com/compute/"><strong>Google Compute Engine</strong></a> is a service in the Google Cloud Platform that offers $300 credits for a 12 month trial period, an always-free micro VM instance.</li></ul><h3>📒 Platform as a Service</h3><p>Platform as a Service (PaaS) is a type of service for running web applications designed for easier setup. Unlike IaaS, PaaS services provide a complete technology stack to run your application without the need to set up the environment on your own. Some of the other concerns that are usually handled by PaaSes are:</p><ul><li>A user interface for managing, running or stopping your application;</li><li>Basic monitoring and logging capabilities;</li><li>Horizontal and vertical scaling to cope with increasing loads;</li><li>Environment configuration;</li><li>Health checks to make sure your application is running and accessible.</li></ul><p>Some PaaSes have a limited set of languages they natively support, but nowadays most of them support running Docker containers, meaning you can run an application written in almost any technology. PaaSes are usually designed for running web applications, and might not be suitable to run daemons or other kinds of software.</p><p>Some of the popular PaaS offerings are:</p><ul><li>📒 <a href="https://www.heroku.com/"><strong>Heroku</strong></a> is one of the oldest PaaS services out there. It supports running applications written in Ruby, Java, PHP, Node.js, and others, as well as deploying applications in Docker containers. Heroku offers a free tier, however, your application will be put to sleep after 30 minutes of inactivity.</li><li>📒 <a href="https://www.netlify.com/"><strong>Netlify</strong></a> is a service for hosting static websites. It offers a fully fledged free tier with support for automated deployment, HTTPS, redirects, A/B testing, form submission and backend logic using AWS Lambda functions.</li><li>📙 <a href="https://azure.microsoft.com/en-us/services/app-service/"><strong>Azure App Service</strong></a> is an offering from Microsoft Azure. It allows hosting applications written in different languages on both Windows or Linux, as well as running Docker applications. There’s a free shared instance available for the Windows app service.</li><li>📙 <a href="https://cloud.google.com/appengine/"><strong>Google App Engine</strong></a> is a service on Google Cloud that supports deploying applications written in Java, Python, Node.js, Go and PHP and Docker applications. There’s also a limited free tier available.</li></ul><h3>📒 Function as a Service</h3><p>Function as a service (FaaS), sometimes also referred to as <a href="https://en.wikipedia.org/wiki/Serverless_computing"><em>serverless</em></a> computing, is a relatively new concept in cloud computing. It’s designed to deploy simple atomic functions into a runtime without the need to worry about the infrastructure and a lot of operational concerns, such as logging and monitoring. Such functions can be invoked as regular services via HTTP requests, but a lot of platforms also provide the ability to react to various events such file uploads, a message in a queue or a modification in a database. The pricing model of FaaSes is also different. Instead of uptime, you pay for execution counts and consumed resources. This makes it a financially attractive solution for parts of your application that don’t need to be up all the time or need to scale dynamically.</p><p>Functions have their downsides though. The tooling for most platforms is still in its infancy and local development may be not as smooth as with regular applications. The situation, however, can improve as the serverless movement is gaining momentum.</p><p>Popular cases for using functions include simple backend services that can be implemented with a minimal amount of code or post-processing to different events in your applications.</p><p>Most large cloud providers also has a function offering:</p><ul><li>📒 <a href="https://aws.amazon.com/lambda/"><strong>AWS Lambda</strong> </a>offers integrations with other Amazon services such as S3, DynamoDB, Kinesis, SNS, and CloudWatch as well as the ability to orchestrate function-based workflows using Step Functions. The AWS SAM tools allows testing your functions locally before deployment. The free tier offers 1M requests and 400,000 Gb seconds computing power per month.</li><li>📒 <a href="https://azure.microsoft.com/en-us/services/functions/"><strong>Azure Functions</strong></a> is a similar offering from Microsoft that allows integrating with Azure services, such as Blob Storages, Storage Queues, CosmosDB and etc. Azure Functions can be integrated into Logic Apps to form complex workflows. It currently supports C#, F#, JavaScript, and Python as well as Java but in preview. It also offers 1M requests and 400,000 Gb seconds computing power per month.</li><li>📒 <a href="https://cloud.google.com/functions/"><strong>Google Cloud Functions</strong></a> provides similar integrations to Google Cloud services, however, only JavaScript and Python functions are supported at the moment. Local development is supported only for JavaScript functions.</li></ul><h3>📙 Containers as a Service</h3><p>With the rise of containers and Kubernetes as the dominant orchestration platform new “Kubernetes as a service” solutions are rolled out by all the major cloud platforms. Such services are commonly referred to as Containers as a Service (CaaS). Since hosting your own Kubernetes cluster is not a trivial task, deploying to a managed cloud cluster is a better alternative for most cases. Such services offer maintained control planes, upgrades, guaranteed cluster uptime and middleware so you can focus on developing your application.</p><ul><li>📙 <a href="https://aws.amazon.com/eks/"><strong>Amazon EKS</strong></a> provides a managed Kubernetes cluster with control nodes deployed to multiple availability zones to ensure uptime, built-in security features, and the ability to integrate with other AWS services. However, the process of setting up a new cluster is not as straightforward as it could be. There is no free tier available, and you need to pay both for the worker nodes, and a fixed fee per cluster.</li><li>📙 <a href="https://azure.microsoft.com/en-us/services/kubernetes-service/"><strong>Azure Kubernetes Services (AKS)</strong></a> offers a relatively easy initial setup process and a competitive pricing model, that doesn’t charge anything for managing the cluster, but only for node VMs.</li><li>📙 <a href="https://cloud.google.com/kubernetes-engine/"><strong>Google Kubernetes Engine</strong></a> has received a lot of positive reviews from the community, which is to be expected from the company that created Kubernetes. It’s praised for its simple setup and operations. It does, however, offer less integrated services than other platforms.</li></ul><p>The cloud landscape is actively developing and providers are racing to offer new innovative services and competitive pricing. Keep an eye out for new offerings from major cloud platforms but also follow smaller platforms that offer more tailored solutions.</p><p>This completes the four-chapter “Beginner’s Web Development Guide” for now. Hope it helped you find your way around the industry and gave you an idea on which direction to follow next. As a next step, I plan to compose it into a single presentable guide and publish it on <a href="https://www.devtrails.io/">devtrails.io</a> so keep posted!</p><p>If you have any questions or comments, feel free to leave them here or reach out on twitter <a href="https://twitter.com/devtrailsio">@devtrails.io</a>.</p><p><em>Update: you can now read the whole guide at </em><a href="https://www.devtrails.io/web-development"><em>devtrails.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82fdcd40d7ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-4-cloud-deployment-82fdcd40d7ef">Beginner’s Web Development Guide Part 4: Cloud Deployment</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner’s Web Development Guide Part 3: Platforms and Tools]]></title>
            <link>https://medium.com/devtrailsio/beginners-web-development-guide-part-3-platforms-and-tools-46467c4cd033?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/46467c4cd033</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Mon, 29 Oct 2018 06:01:03 GMT</pubDate>
            <atom:updated>2018-11-20T18:57:18.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5z3ij0cufNwWzEyx" /></figure><blockquote>This post is part of a series of posts for beginner web developers. Also check out “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5">Part 1: Frontend</a>”, “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc">Part 2: Backend</a>” and “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-4-cloud-deployment-82fdcd40d7ef">Part 4: Cloud Deployment</a>”.</blockquote><p>Continuing our talk on learning web development, we’ll move away from particular programming languages and rather focus on the environment where web applications are run and developed. This section covers several large topics:</p><ul><li>The basic development tools that every developer needs to be familiar with.</li><li>Since our applications live on the Web, we’ll go through some fundamental topics related to networking;</li><li>The environments where our applications are run.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqFvkuVjoPVqYqb7HW_miQ.png" /><figcaption><em>The color coding of the chart is very simple: yellow (📒) lines show the basic things you need to learn, orange (📙) represent more advanced topics that you can leave for later and grey (📓) are niche topics that you might come in handy in some occasions.</em></figcaption></figure><h3>📒 Development tools</h3><p>From early on to make sure you are comfortable with your development tools so that you can quickly progress in writing code and debugging your application. Every platform you develop for will have a lot of tools particular for that platform, however, there are some that are used by almost all developers. Let’s walk through them.</p><h4>📒 Code Editors</h4><p>The code editor is the home of every software developer. This is where the magic happens. Basic code editors provide the most necessary feature set, such as code highlighting, refactoring and debugging capabilities. There are also more advanced editors, known as integrated development environments (IDEs), that have a wide range of powerful integrated tools and capabilities. Here are some of the most popular code editors.</p><ul><li>📒 <a href="https://code.visualstudio.com/"><strong>Visual Studio Code</strong></a> is a free cross-platform code editor created by Microsoft. It has built-in support for JavaScript, TypeScript, CSS, and HTML, an support for a lot of other languages is available as extensions. VS Code offers syntax highlighting, code completion, code snippets for generating code, refactoring capabilities, and a built-in terminal. It also has an integrated debugger to help you troubleshoot bugs in your application. Although the feature set might not be as wide as in commercial IDEs, it’s certainly enough to get you started.</li><li>📙 <a href="https://www.jetbrains.com/"><strong>JetBrains IDEs</strong></a> — a family of IDEs developed by JetBrains for different platforms. There’s <a href="https://www.jetbrains.com/webstorm/">WebStorm</a> for frontend development, <a href="https://www.jetbrains.com/idea/">Intellij IDEA</a> for Java and <a href="https://www.jetbrains.com/phpstorm/">PhpStorm</a> for PHP and etc. Each of these focus on supporting the corresponding languages, frameworks and tools. Compliment this with even more helpful features, such as integration with version control systems, local change history or running tasks, and you will get a highly efficient working environment. These products are paid for, but the <a href="https://www.jetbrains.com/idea/download/">IntelliJ Community Edition</a> can be used for free.</li><li>📙<a href="https://visualstudio.microsoft.com/vs/"><strong>Visual Studio IDE</strong></a> — is a commercial IDE developed by Microsoft. It comes in three offerings: the free community edition, professional and enterprise. It has support for a wide range of programming languages and different tools for developing and debugging your applications. On top of that, it provides helpful integrations with other Microsoft products and services such as Azure or Azure DevOps. C# and TypeScript are first-class citizens in VS.</li></ul><h4>📒 Version Control Systems</h4><p>Version control systems (VCS) play a key role in every development process. VCS allows you to store a complete history of all your code changes in a remote repository. You can browse the repository to review the change history, compare different versions or rollback to an older version. Multiple developers can push changes to the same repository to collaborate on a project keeping their local codebases in sync. Nowadays VCS are used as the ultimate source of truth for the codebase and are a backbone of modern development processes.</p><p>VCS systems can be used via a command line interface, but there are also different GUI clients available as well as integrations with different code editors.</p><p>There are two popular version control systems:</p><ul><li>📒 <a href="https://git-scm.com/"><strong>Git</strong></a> is by far the most popular VCS. It’s a distributed system, meaning that when a user copies the repository, he or she also gets the full history of the project and can work with it offline. Occasionally users need to publish their changes to the central remote repository and download changes made by others. There are many services proving hosted Git repositories. The most popular of them are <a href="https://github.com/">GitHub</a> and <a href="https://bitbucket.org/">BitBucket</a>.</li><li>📓 <a href="https://subversion.apache.org/"><strong>Subversion (SVN)</strong></a> is another version control system. Unlike Git, SVN allows you to check out only a single branch. To switch to a different branch, you’ll need to download it from the remote repository. Although still used in the industry, Git is much more popular and has much more tools and services built around it.</li></ul><h4>📒 Terminal or Command Prompt</h4><p>As a developer, it’s important that you feel comfortable with using the terminal on OS X or Linux or the command prompt in Windows. Even if you can do most of your work from the GUI, you will still encounter a lot of useful tools that offer only a command line interface. You might also find yourself working with some remote machine that does not have a GUI at all. Make sure that you can do the basic things, such traversing the file system, creating or removing files, viewing their contents and running CLI tools.</p><h4>📙 Shell scripting</h4><p>Once you feel comfortable with using the command shell, you can save yourself a lot of time by automating routine tasks such as deployment, infrastructure provisioning or running development tasks. Depending on your operating system, you should learn how to write either for Linux and OSX using Bash or for Windows using batch files or PowerShell. Often other software comes with a set of such scripts to use it, so being able to read and understand the underlying commands will be helpful as well.</p><h3>📙 Linux</h3><p>Linux is a family of free open-source operating systems built based on the Linux kernel. There are different Linux distributions available, such as Ubuntu, Debian, CentOS, Mint, openSUSE and etc. You can find Linux distributions running on all kinds of devices, starting from embedded electronics and appliances to smartphones and servers. Linux is different from Windows in a number of ways, so if you come from a Windows background, you’ll need to learn some fundamentals, like how the file system is structured, how access control works, how to install software and etc.</p><p>For a web developer, it’s important to be familiar with Linux since it’s extremely popular operating systems to run web servers. There are a lot of books and learning resources available for Linux, however, to really get to know it, you should start using it. You can install Linux as a primary or secondary OS and use it for everyday tasks. Once you start, you will figure out the details along the way.</p><h3>📒 Networking</h3><p>Since we’re talking about web development, networks will play an important role in our lives. The users of your application will access it using the Internet over a cable or wireless networks. You application itself might communicate with other services over a network. To understand how this works, it’s important that you learn some of the basic networking technologies.</p><h4>📒 Protocols</h4><p>A protocol is a set of rules on how applications should communicate with each other. They describe how a connection should be initialized, the order and the format of messages sent. There are several important protocols that are frequently used in web applications.</p><ul><li>📒 <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP"><strong>Hypertext Transfer Protocol (HTTP)</strong></a><strong> </strong>is the underlying protocol of the World Wide Web and defines how browsers or other clients can request resources from web servers. When you enter a URL of a website in a browser, it actually makes one or several HTTP requests to the server to load the HTML, CSS, scripts and other assets. Its counterpart, Hypertext Transfer Protocol Secure (HTTPS) allows encrypting the transferred information to allow for secure communication.</li><li><strong>📙 </strong><a href="https://developers.google.com/web/fundamentals/performance/http2/"><strong>HTTP/2</strong></a><strong> </strong>is a major update to HTTP that aims to improve the performance of web applications. It enables multiplexing, meaning you can transfer different content over a single open request at the same time. The protocol enforces encryption and minimises the protocol overhead by compressing header fields.</li><li><strong>📙 </strong><a href="https://en.wikipedia.org/wiki/Transmission_Control_Protocol"><strong>Transmission Control Protocol (TCP)</strong></a><strong> </strong>is a transport layer protocol that allows to send packages between different applications in a reliable, ordered and error-free way. HTTPS and HTTPS work on top of TCP.</li><li>📙<a href="https://en.wikipedia.org/wiki/Internet_Protocol"><strong>Internet Protocol (IP)</strong></a> is an internet layer protocol that defines how a package must be routed from one host to another. TCP uses IP for routing. There are two major versions of the protocol currently in use: IPv4 and IPv6.</li></ul><h4>📒 Domain Name System</h4><p>The Domain Name System (DNS) is responsible for translating human-readable names of Internet resources into their corresponding IP addresses. Resolving a domain into an address is quite a complicated process under the hood, and you will need at least some basic knowledge on how it works in order to be able to configure your application correctly.</p><h4>📒 Web Servers</h4><p>Web server is a special type of software that is responsible for listening for incoming connections using different protocols and responding with the requested content. A web server can serve static files, such as HTML, JavaScript files or images, run dynamic scripts written in different languages or serve as a proxy for processes running as separate applications.</p><p>Web servers can also play an important part in improving the performance of your application by enabling compression, caching and load balancing.</p><p>These are some of the more popular web servers.</p><ul><li><strong>📒 </strong><a href="https://httpd.apache.org/"><strong>Apache HTTP Server</strong></a> is a free open-source web server developed under the Apache Software Foundation. It’s a fast and powerful web server that can be configured to serve static content, but is also frequently used to run scripts written in PHP, Python and etc.</li><li>📒 <a href="https://www.iis.net/"><strong>Microsoft IIS</strong></a> is a general-purpose web server from Microsoft that is available on the Windows Server operating systems. IIS is a popular choice for companies using the Microsoft technology stack.</li><li>📒 <a href="https://www.nginx.com/"><strong>NG</strong></a><strong>INX</strong> is web server that’s usually used as a high-performance static content server or a proxy for dynamic applications. In contrast to Apache, it cannot serve dynamic content on its own, but can sometimes achieve better performance. NGINX is a free and open-source web server but offers a more advanced paid version called NGINX Plus.</li></ul><h4>📒Network Troubleshooting</h4><p>Sometimes you might find yourself in a situation that your application or web server is for some reason unavailable. Although debugging such cases might be tricky and there can be a lot of reasons for outages, there are some tools you can use to try to diagnose the situation and get to the source of the problem.</p><ul><li>📒 <strong>Ping</strong> is a cross-platform CLI utility that can be used to verify if a particular IP address is reachable. It also measures package loss and the roundtrip time that will give some idea about the health of the connection.</li><li>📙 <a href="https://nmap.org/ncat/"><strong>Ncat</strong></a> is a powerful Linux CLI tool, a Swiss army knife of networking tools, that allows you to send messages using different protocols, scan for open ports, create tunnels and much more.</li></ul><h3>📙 Virtualisation</h3><p>Virtualisation is an important concept in computing that has radically changed how resources are managed. Using virtualisation, we can create separate servers, workstations, files, networks or disks on a single piece of hardware. To the users, all of these resources appear as real physical resources, however, they are really provisioned using software, abstracted from the underlying hardware.</p><h4>📙 Virtual Machines</h4><p>One of the most frequent use cases for virtualisation is the need to run different software or even different operating systems on a single physical machine. These are called virtual machines and provide completely isolated environments with its own memory, disk space and software installed. Virtual machines can be used for development purposes to run different operating systems on your workstation, but more importantly, to run multiple applications on a single hardware server without interfering with each other. Software for creating and running virtual machines is called a hypervisor.</p><ul><li><strong>📙 </strong><a href="https://www.virtualbox.org/"><strong>VirtualBox</strong></a> is a free open-source cross-platform hypervisor currently being developed by Oracle. It supports creating and running virtual machines, as well as sharing resources, such as folders or clipboard, with the host machine.</li><li>📓 <a href="https://www.parallels.com/products/desktop/"><strong>Parallels Desktop for Mac</strong></a> allows you to seamlessly run Windows applications on your Mac. Parallels is convenient if you need to set up a Windows development environment on your Mac or to test something on Windows.</li></ul><h4>📙 Containers</h4><p>Containers is a different virtualisation mechanism to run software, but unlike virtual machines, containers don’t run a complete operating system, but share the same container runtime. This makes them much more lightweight and quicker to start, meaning that you can run many containers on a single machine without wasting a lot of resources. Best practices for containers is to run each piece of your application, such as a backend service, a web server or database, separately from the others, providing more granular control and isolation.</p><ul><li><strong>📙 </strong><a href="https://www.docker.com/"><strong>Docker</strong></a> is the most popular cross-platform container runtime developed by Docker, Inc. With Docker you can create a container image that is needed to run your application using a Docker file. These images can then be published into a registry to be run by others or deployed to a web server. Using Docker you can easily create a clean, pre-defined, disposable environment to develop your application and then use the same image to run it on production. There is a wide range of tools available to manage images and running containers, as well as services that allow you to host containerised applications.</li><li><strong>📙 </strong><a href="https://kubernetes.io/"><strong>Kubernetes</strong></a> is an open-source platform for deploying containers on a cluster of machines. It allows you to define services based on container images and configuration parameters, as well as create virtual storage or network resources. It also provides operational capabilities such as scaling, load balancing and logging. You can host Kubernetes on your own machines, or use one of the cloud-based services. It’s an extremely flexible and powerful platform that is currently rapidly evolving.</li></ul><p>In this chapter, we’ve focused mostly on tools and platforms that can be useful for developers on different platforms. However, when you start working with a particular platform, you will discover a lot of new tools that will be useful in your particular context.</p><p>Next time, we’ll have a look at different cloud deployment options so you could pick a suitable option for deploying your applications.</p><p><em>Update: you can now read the whole guide at </em><a href="https://www.devtrails.io/web-development"><em>devtrails.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46467c4cd033" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-3-platforms-and-tools-46467c4cd033">Beginner’s Web Development Guide Part 3: Platforms and Tools</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner’s Web Development Guide Part 2: Backend]]></title>
            <link>https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/fd466212dbfc</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 05:01:02 GMT</pubDate>
            <atom:updated>2018-11-20T18:57:02.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xA0e9a1sdFYdO6yE" /></figure><blockquote><em>This post is part of a series of posts for beginner web developers. Also check out “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5"><em>Part 1: Frontend</em></a><em>”, “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-3-platforms-and-tools-46467c4cd033"><em>Part 3: Platforms and Tools</em></a><em>” and “</em><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-4-cloud-deployment-82fdcd40d7ef"><em>Part 4: Cloud Deployment</em></a><em>”.</em></blockquote><p>Today we continue our intro to web development. In the <a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5">previous post</a> we started with exploring frontend development, and today we are going to talk about backend development.</p><p>Backend development, also sometimes called server-side development, refers to developing the processes that happen on the server and are usually not visible to the users. A web UI can send requests to the backend asking to render some HTML, save user input in a database, authenticate a user, send an email or process a payment request. Although this part of the application is transparent for the user, it’s in no way less important. This is the heart and brains of your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1DSs5H0UvHru5L1tL9IrMA.png" /></figure><p><em>The color coding of the chart is very simple: yellow lines show the basic things you need to learn, orange represents more advanced topics that you can leave for later, and grey are niche topics that might be useful for special projects.</em></p><h3>Languages</h3><p>Compared to frontend development, the choice of programming languages on the backend is much wider and you are free to one a solution depending on your use case and environment.</p><blockquote>There are many ways to classify programming languages, and we made an arbitrary decision to group them by scripting and compiled languages. Have to admit, though, that this is not completely accurate. Some of the scripting languages are actually compiled on the fly, and some compiled languages could have interpreters. This division, however, serves as a convenient starting point for our analysis.</blockquote><h3>Scripting languages</h3><p>Languages that don’t require explicit compilation before execution are called scripting languages, or interpreted languages. As opposed to compiled languages, they do not produce a binary executable. Rather the code is evaluated and run on the fly. Sometimes, scripting languages are easier to get started with, since you don’t have to write code in a strict manner required by the compiler. This, however, means that errors that could have been discovered during compilation will only become apparent during runtime.</p><p>Some of the more popular scripting languages are:</p><ul><li>JavaScript using the <a href="https://nodejs.org/en/">Node.js</a> server-side runtime. It supports its own set of JavaScript features and provides a set of API’s to satisfy backend use cases, such as working with the file system. Learning Node.js is a great choice since by learning a single language you’ll be able to work both on the frontend and the backend. Node.js has several popular frameworks, such as <a href="https://expressjs.com/">express</a>, <a href="https://koajs.com/">koa</a> or <a href="https://loopback.io/">LoopBack</a>.</li><li><a href="https://www.python.org/">Python</a> is a general-purpose programming language. It’s simple syntax and clear constructs make it quite easy to learn for beginners. Python is widely used for developing applications but has also gained significant traction for doing scientific research and working with artificial intelligence. There are currently two major versions being used: Python 2 and Python 3. One of the popular projects developed on Python is the <a href="https://www.django-cms.org/en/">Django</a> content management system. <a href="http://flask.pocoo.org/">Flask</a> is a popular micro-framework for web development.</li><li><a href="http://php.net/">PHP</a> — another popular programming language for web applications. The language itself has a low entry barrier for beginners but also provides more advanced features for intermediate users. Some of the most popular projects created on PHP are <a href="https://wordpress.org/download/">WordPress</a> and <a href="https://www.drupal.org/">Drupal</a>, with the former being arguably the most used content management system in the world. Notable frameworks are <a href="https://laravel.com/">Laravel</a>, <a href="https://symfony.com/">Symfony</a> and <a href="https://codeigniter.com/">CodeIgniter</a>.</li><li><a href="https://www.ruby-lang.org/en/">Ruby</a> — a scripting language designed to be simple and natural to read and write. The most popular development framework for Ruby is <a href="https://rubyonrails.org/">Ruby on Rails</a>. <a href="https://jekyllrb.com/">Jekyll</a>, a popular static website generator is built on Ruby.</li></ul><h3>Compiled languages</h3><p>Code written using a compiled language needs to be first compiled into a binary file before it can be executed. Although this needs an explicit extra step to be performed by the developer, it also brings additional benefits. The compiler can analyze the code for mismatches and give you early feedback about potential problems. Some compilers can also optimize the resulting bytecode for a particular platform ensuring superior performance. Although compiled languages might have a higher entry barrier than scripting languages, they are usually preferable in large projects due to the additional safety measures and more descriptive code.</p><p>There’s a large selection of languages to choose from.</p><ul><li><a href="https://www.java.com/en/">Java</a> is a high-level object-oriented programming language developed by Sun Microsystems and currently maintained by Oracle. Java designed to be portable between different platforms: the sources are compiled to Java bytecode that can be run on a Java Virtual Machine for any platform. It’s a highly mature language with a lot of different frameworks for developing web applications, the most popular being <a href="https://spring.io/">Spring</a>. Additionally, Java can be used for developing Android applications. Although there are trends in considering Java old fashioned and inferior to other JVM languages, such as Kotlin, it is still one of the most popular programming languages. Java is extremely popular in the enterprise sector.</li><li><a href="https://docs.microsoft.com/en-us/dotnet/csharp/">C#</a> is another high-level object-oriented programming language developed by Microsoft. Originally developed to be used on Windows, it can now be used to build cross-platform applications using the relatively new <a href="https://www.microsoft.com/net/download">.NET Core</a> runtime. One of the most popular frameworks for building web applications using C# is <a href="https://docs.microsoft.com/en-us/aspnet/core/?view=aspnetcore-2.1">ASP.NET Core</a>. C# is popular among companies adopting Microsoft’s technology stack.</li><li><a href="https://golang.org/">Go</a> is a relatively young language developed by Google that’s quickly gaining popularity. It’s designed to be less verbose than Java or C# and based on simple primitives, intentionally leaving out some of the complex constructs that are present in other languages. Go is extremely fast, has a minimal memory footprint and has first-class concurrency support, so it’s a good candidate for projects where speed and low resource consumption are of importance. The library and tool ecosystem around Go is still developing and we’re seeing a lot of interesting projects appear among the community. Go has gained significant popularity in blockchain development.</li><li><a href="https://kotlinlang.org/">Kotlin</a> is a language developed by JetBrains and a close competitor of Java. Kontlin runs on the Java virtual machine, but can also be compiled into JavaScript. It’s designed to be less verbose than Java, adds first-class function support and offers additional safety measures to avoid common errors. Like Java, it can also be used to develop Android applications.</li><li><a href="https://www.scala-lang.org/">Scala</a> is another JVM-based language and an alternative to Java. It has a more concise syntax, additional safety features and makes heavy use of functional programming.</li><li><a href="https://www.erlang.org/">Erlang</a> — a functional language designed for concurrency and high availability. Erlang is popular in applications where high performance and scalability is critical. Popular use cases include image and signal processing or analysis of large amounts of data.</li><li><a href="https://www.haskell.org/">Haskell</a> — another functional programming language that is valued for its powerful typing system and a design that helps to produce clear and reliable code. Since it’s a functional language, it also scales efficiently and offers good performance.</li></ul><h3>Databases</h3><p>An important ability of most applications is to store user’s data. It is usually done using special software called database management systems (DBS). A DBS provides access to underlying data storages allowing allow the applications to store, retrieve and update data. There are different kinds of databases optimized for different shapes and volumes of data. In this guide, we’ll have a look at the two most popular types: relational and non-relational.</p><h4>Relational</h4><p>Relational databases store data in tables, where rows represent entries, and columns — entry attributes. Rows in different tables can be linked using foreign keys to represent relations between different types of entries. For example, if you’re building an online store, you might have a table for storing orders with columns such as “order number”, “client name” and “shipping address” where each row represents a separate order. Information about the ordered items will be stored in a different table called “order items”, with references to the order table.</p><p>Most relational databases use a language called Structured Query Language (SQL) or its dialect to query or modify the data. Because of this, they are often called SQL databases.</p><p>Popular relational databases are:</p><ul><li><a href="https://www.oracle.com/database/index.html">Oracle Database</a> is a database developed by Oracle. Due to its high scalability and powerful feature set, it’s often used by large enterprises. Its less frequently used for small and midsize projects due to its high license costs.</li><li><a href="https://www.mysql.com/">MySQL</a> — a free open-source database developed by a Swedish company MySQL AB and currently owned by Oracle. MySQL can use different storage engines for each table to store and use data differently. MySQL is used for a wide range of cases, however, it is very popular for web applications, especially in the so-called LAMP (Linux, Apache, MySQL, PHP) stack. It also offers several paid editions for large-scale users.</li><li><a href="https://www.microsoft.com/en-us/sql-server">SQL Server</a> also referred to as MSSQL, is a database maintained by Microsoft. It has a number of different editions for handling various workloads and data volumes. SQL Server is a major competitor of Oracle and is popular among Microsoft stack users.</li><li><a href="https://www.postgresql.org/">PostgreSQL</a> — is a free open source database developed by a worldwide team of volunteers. It provides a rich set of features and is capable of handling large workloads.</li></ul><h4>Non-relational</h4><p>Non-relation databases store data in models other than tables. There are different models you can choose depending on your use cases, such as storing key-value pairs, documents, graph relations or time-series. Although non-relation databases have been around for a while, they have recently experienced a surge of popularity due to simpler design and easier scaling.</p><p>Non-relation databases are also referred to as NoSQL databases since most of them use their own query language instead of SQL.</p><p>These three databases are frequently used in web development.</p><ul><li><a href="https://www.mongodb.com/">MongoDB</a> is a free open source document database that stores JSON-like objects. You can store and retrieve these objects and map them to objects in your application. It also has the usual querying and aggregation capabilities. MongoDB is a good candidate for applications where data consistency is not a primary concern.</li><li><a href="https://redis.io/">Redis</a> is an in-memory key-value database often used to temporarily store cached data and transfer messages. Since such data does not necessarily need to be persisted, saving data to disk can either be disabled or delayed, to increase performance. Redis can store different values types, such as strings, numbers, lists, maps etc.</li><li><a href="https://www.elastic.co/">Elastic Search</a> is an open-source text search and analytics engine. It allows you to store text documents and produces a searchable text index. Elastic Search is commonly used for log analytics (particularly as part of the <a href="https://www.elastic.co/elk-stack">ELK stack</a>) and free text document search.</li></ul><h3>Messaging</h3><p>Sometimes server-side components need to trigger jobs that need to be executed in the background. For example, asking for a business-reports may trigger a lengthy process that will generate the report and e-mail it to the user, without the user having to wait for it. To do that we need to be able to send a message to a different component and be sure that it’s processed successfully. If the job fails, it needs to be restarted. Software that provides such functionality is called a message broker.</p><p>The two most popular messages brokers are:</p><ul><li><a href="https://www.rabbitmq.com/">RabbitMQ</a> is a traditional message broker that supports different message delivery models and routing rules. It guarantees that the message will be delivered and processed by the consumer. Failed messages can be stored in the dead-letter queue. RabbitMQ works through the standard <a href="https://www.amqp.org/">AMPQ protocol</a> that is also supported by other message brokers and client libraries.</li><li><a href="https://kafka.apache.org/">Apache Kafka</a> is a stream processing engines, that can also be used as a message broker. Apart from providing most of the standard message broker features, it also offers advanced features, such as being able to re-process messages from history. It also provides greater performance that allows processing high volumes of messages.</li></ul><p>If you endured these two chapters, then you should already have an idea of technologies used for both backend and frontend development. I encourage you to follow the links and do some research before you decide and what do you want to specialise in.</p><p>In the next chapter, we’ll have a look at the tooling that every developer should know.</p><p><em>Update: you can now read the whole guide at </em><a href="https://www.devtrails.io/web-development"><em>devtrails.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd466212dbfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc">Beginner’s Web Development Guide Part 2: Backend</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner’s Web Development Guide Part 1: Frontend]]></title>
            <link>https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/ca59f1877ec5</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Thu, 18 Oct 2018 05:01:04 GMT</pubDate>
            <atom:updated>2018-11-20T18:56:46.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HkIQFcEFekJDVNYU" /></figure><blockquote>This post is part of a series of posts for beginner web developers. Also check out “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc">Part 2: Backend</a>”, “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-3-platforms-and-tools-46467c4cd033">Part 3: Platforms and Tools</a>” and “<a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-4-cloud-deployment-82fdcd40d7ef">Part 4: Cloud Deployment</a>”.</blockquote><p>A few days ago I’ve posted a short essay on why I decided to start the DevTrails project mentioned, that I will begin working on the first guide. Most of my personal background is in web development, so I thought this is a good place to start. It’s also one of the largest segment of the industry with high demand both in startups and in the enterprise sector. This guide will start with the very basics, so I feel that it might be more interesting for beginners, but intermediate developers might discover something new as well.</p><p>For beginners, it’s easy to get into web development because there are many languages with relatively low entry barriers, a lot of free open-source tooling and many frameworks that simplify development. On the other hand, there is so much to choose from. The difficult part about development is that you need to combine a lot of components together for your application to work. Which UI framework to choose? Where to store your data? PHP, Python, Ruby or something else? How to host your application? I hope this guide will shed some light on this and help you figure out your way around web development and maybe even start a career.</p><p>The guide will we split into several parts and today we’ll start with the first one — Frontend development, and introduce you to the most important languages and tools in this area.</p><h3>Frontend development languages and tools</h3><p>We’ll start with a sort of a map of the frontend landscape that depicts the things you should at least know about to orientate in this area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTugtD0bF1g4_eEWzYiaxg.png" /></figure><p><em>The color coding of the chart is very simple: yellow lines show the basic things you need to learn, while orange represents more advanced topics that you can leave for later.</em></p><p>Frontend development, also known as UI development, refers to creating web user interfaces, the parts of the application that the user sees and interacts with. Frontend development stands firmly on three pillars: HTML for markup, CSS for styling and JavaScript for logic and interactions. Although these three technologies stood the test of time, the underlying tools and frameworks change constantly. This section will give you a starting point to start the exploration of the frontend ecosystem.</p><p>Frontend development is also tightly related to web design and user experience and the border between the two can be different in each company. In general frontend developers focus on technical issues, while web designers are concerned with aesthetics and user experience.</p><h3>HTML</h3><p><a href="https://developer.mozilla.org/en-US/docs/Web/HTML">Hyper Text Markup Language (HTML)</a> is a markup language that allows you to structure the information that is displayed to the user. Its the An HTML document consists of elements each represented by an HTML tag, such as a heading, a paragraph of text or a text input field. HTML documents can also link to other documents using hyperlinks. Each tag carries its own type of content, has a certain appearance and attached behavior. Once you get a hang of HTML, you will be able to create very simple static HTML pages.</p><h3>CSS</h3><p><a href="https://developer.mozilla.org/en-US/docs/Web/CSS">Cascading Style Sheets (CSS)</a> is a styling language used to describe the visual appearance of HTML elements. It can be used to controls aspects like the positioning of an element, its dimensions, text style or colors, or almost any other visual aspect of a website. Styles are defined as a set of rules that can be applied to a single element of a subset of elements on the page. Recent CSS features allow you to go way beyond basic styling and control more complex visual aspects, such as animations.</p><h4>Preprocessors</h4><p>CSS is a powerful language but it has its constraints when it comes to code reuse, verbosity, and isolation. Because of this, maintaining a large CSS code base can be difficult. To address these shortcomings, a number of solutions have been created by the community. These languages and their compilers are generally referred to as CSS preprocessors.</p><ul><li><a href="https://sass-lang.com/">Sass/SCSS</a> extends the capabilities of CSS to make your CSS code base more maintainable. Some of the features, such as nesting, make CSS less verbose and easier to write, while other such as variable and mixins allow for code reuse. It also supports importing other SCSS files that allows you to break your code into smaller files. Some popular CSS frameworks such as <a href="http://compass-style.org/">Compass</a> are based on Sass.</li><li><a href="https://postcss.org/">PostCSS</a> is a tool that uses JavaScript plugins to transform CSS files. You can add plugins that perform code analysis, add variable support, optimize code and etc. In contrast to SCSS or Less, which are custom formats, there are a lot of plugins for PostCSS that emulate the upcoming standard CSS features.</li><li><a href="http://lesscss.org/">Less</a> is a preprocessor with a feature set similar to Sass. Despite their similarity, there are a number of differences in the underlying implementations. Although being popular in the past, a lot of developers are now moving away from Less in favor of Sass or PostCSS.</li></ul><h3>JavaScript</h3><p><a href="https://developer.mozilla.org/en-US/docs/Glossary/JavaScript">JavaScript (JS)</a> is the most used programming language for developing user interfaces for the web. It allows you to add custom behavior to your websites, such as reacting to user events, loading data from web services and showing or hiding elements on a page. It also allows you to interact with the browser through various APIs. You can use it to both add separate interactive elements to your website or create complex web applications.</p><p>Another term that you may encounter related to JavaScript is ECMAScript which is actually a language specification for JavaScript. In most cases, they can be treated as synonyms.</p><h4>Frameworks</h4><p>JavaScript is a powerful language, but if your looking to make a complex application, using it without a framework will result in masses of complex boilerplate code. To make it simpler, there are a number of frameworks out there that help with the basic functionality such as HTML manipulation, data loading, overall application architecture and etc. The three most popular frameworks at the moment are React, Angular and Vue.js.</p><ul><li><a href="https://reactjs.org/">React</a> is a library for building user interfaces developed by Facebook. React is based around creating components, such as a button or a side menu, that can render HTML based on input parameters. React components are written using an extension to JavaScript called <a href="https://reactjs.org/docs/introducing-jsx.html">JSX</a>, that allows you to conveniently combine JavaScript code and HTML. Components can be composed together to create complex UI elements and whole applications. React is not a framework per se, it only provides the view layer, however, its rich ecosystem of tools and libraries has everything you’ll need to create complex applications. React is easy to start with, but with time you are expected to learn new libraries to fill the missing gaps.</li><li><a href="https://angular.io/">Angular</a> — a component-oriented “batteries included” type of framework developed by Google. Angular applications are usually written in TypeScript. It provides most o the things you’ll need to build a web application including a CLI tool to bootstrap, develop and build the project as well as libraries to manage forms, data loading, routing, etc. Although it does provide most of the things out of the box, it has a higher abstraction and complexity levels, and the need to learn TypeScript as a primary development language makes the initial learning curve steeper.</li><li><a href="https://angular.io/">Vue.js</a> is a framework designed to be modular and incrementally adoptable. You can start using it as a view layer and add additional libraries as you need them. In contrast to other frameworks, the most important libraries are maintained by the core Vue.js team.</li></ul><p>You might also encounter other frameworks out there that have a smaller community or are getting superseded, such as <a href="https://www.emberjs.com/">Ember.js</a> or <a href="https://angularjs.org/">AngularJS</a>.</p><h4>TypeScript</h4><p><a href="https://www.typescriptlang.org/">TypeScript</a> extends JavaScript to add static type checking and the latest ECMAScript features, such as async/await, classes or arrow functions. As a result, TypeScript compiles into vanilla JavaScript. Having static type checking in place means that the compiler will notify you when you are trying to use a function or variable in a manner that does not match its signature. This also gives code editors the ability to provide better code navigation and refactoring capabilities. Typings are optional, so you can introduce them gradually in your existing JavaScript project. Using TypeScript makes it much easier to work on projects with larger code bases.</p><h4>Component Libraries</h4><p>Component libraries are collections of components that can be used to assemble your application. Some of them implement the most common components such as buttons and drop downs, while others also provide utilities for creating complex responsive layouts. Although each of them has its own distinctive visual style, they can usually be customized to match the design and branding of your project. Most of them are available as plain CSS and JavaScript, however, they are often ported to work with other popular JavaScript frameworks. Some of the more popular libraries are:</p><ul><li><a href="http://getbootstrap.com/">Bootstrap</a> is a powerful framework for creating responsive web applications. It comes with a large set of components as well as utilities for creating layouts and a theming engine. You can add user interactions to components, such as a dropdown, minimal knowledge of JavaScript. There is also a wide selection of ready-made website themes built with Bootstrap.</li><li><a href="https://semantic-ui.com/">Semantic UI</a> is another popular UI library with all kinds of components and a theming engine. However, to make the components interactive, you are expected to write some JavaScript code.</li><li><a href="https://material-ui.com/">Material UI</a> — a popular implementation of <a href="https://material.io/design/%20for%20React">Google’s Material Design</a>. It provides a set of components as well as guidelines on how your application should look and feel like according to Google. There are other implementations available for <a href="https://material.angular.io/">Angular</a> or <a href="https://getmdl.io/">vanilla JavaScript</a>.</li></ul><p>Some other honorable mentions include <a href="https://ant.design/">ant-design</a>, <a href="https://foundation.zurb.com/sites.html">Foundation</a>, <a href="https://bulma.io/">Bulma</a> and <a href="https://github.com/pure-css/pure/">Pure</a>.</p><h3>Frontend tools</h3><p>The frontend ecosystem is known for its large arsenal of helpful tools each designed for their own purpose. Since there are so many of them, there’s no way we can cover everything in this guide, so instead, we’ll focus on several that are important to get started with.</p><h4>NPM</h4><p><a href="https://www.npmjs.com/">Npm</a> actually means two things:<br>1. A software registry that contains thousands of open-source libraries and tools that you can install and use in your project.<br>2. A CLI tool that allows to install, update and remove packages from the registry.</p><p>Using npm allows you to install libraries that will be used by your project and document them in a JSON file. Storing this file together with the code base means that you can explicitly declare the dependencies of your project and quickly install them on different environments. You can also use it to publish your own libraries and share them with other developers.</p><p>The npm CLI tool also allows you to run scripts that can be used to execute tests, compile code or perform code analysis.</p><p>An analog to npm is <a href="https://yarnpkg.com/">Yarn</a>, that offers some performance improvements and better support for library development and is compatible with the npm package registry.</p><h4>Webpack</h4><p><a href="https://webpack.js.org/">Webpack</a> is a popular module bundler. It allows you to merge different kinds of assets, such as JavaScript code, CSS styles, HTML templates and even images into bundles that can be more effectively loaded by the browser. When using Webpack, you split your code into modules. Each module can import other modules. Webpack then analyses the import graph and bundles resources together. Apart from bundling, Webpack uses loaders and plugins to transform bundled code, e.g. perform compilation, code analysis or minification. Webpack can be tricky to start with, but it’s the cornerstone of most of the modern build setups.</p><p><a href="https://rollupjs.org/">Rollup.js</a> is sometimes used as an alternative to Webpack.</p><h4>Chrome DevTools</h4><p><a href="https://developers.google.com/web/tools/chrome-devtools/">Chrome DevTools</a> is a rich set of tools available in the Chrome browser. It can be used for a wide range of debugging cases, such as browsing the source code or HTML elements, tracking network requests and measuring the performance of different parts of your application. It allows you to edit pages on the fly which can be useful to quickly test a small set of changes. Having a firm grasp of this tools will save you countless hours of debugging. You can also use it to look under the hood of other web pages and see how they work. Similar tools are also available in other browsers.</p><p>This should be enough to get you started on frontend development track. Don’t worry, this is just the tip of the iceberg. If you feel that this is something that you want to learn in more detail, then you will have a whole lot of interesting stuff waiting for you.</p><p>In the <a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-2-backend-fd466212dbfc">next chapter</a>, we’ll do an overview of backend development and see what we have on the server-side.</p><p><em>Update: you can now read the whole guide at </em><a href="https://www.devtrails.io/web-development"><em>devtrails.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca59f1877ec5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/beginners-web-development-guide-part-1-frontend-ca59f1877ec5">Beginner’s Web Development Guide Part 1: Frontend</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevTrails and the three perspectives of learning]]></title>
            <link>https://medium.com/devtrailsio/devtrails-and-the-three-perspectives-of-learning-5d31df7f83f5?source=rss----94ee056dfbbb---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d31df7f83f5</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Pavel Yeliseev]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 18:23:04 GMT</pubDate>
            <atom:updated>2018-10-17T05:55:11.032Z</atom:updated>
            <content:encoded><![CDATA[<h3>Three Perspectives of Learning Software Development</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*blkMwifYa4yej0B2" /><figcaption>“trail signage selective focus photography” by <a href="https://unsplash.com/@camille_couvez?utm_source=medium&amp;utm_medium=referral">Camille Couvez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>They say that doctors need to learn all their life. With great respect to doctors, I believe that this statement extends to software developers as well. The ever-increasing demand for complex software is continuously driving innovation and with every day we see new tools, platforms, and practices appearing to address the new challenges. As a software developer, I have to spend a considerable amount of time on research and development that will allow me to stay up to date today and remain competitive on the market tomorrow.</p><p>A good example of this is JavaScript, an ecosystem that has produced a staggering amount of new projects in recent years. We’ve seen the rise of different frameworks that made creating new applications much easier, adoption on new platforms, from backend to mobile and desktop, a plethora of new tools and libraries and a rapidly growing developer community. For some people keeping up with the constantly shifting landscape proved to be challenging, giving birth to the term “JavaScript fatigue”. Especially for beginners.</p><p>I’m personally familiar with the uncomfortable feeling of starting learning something new and not knowing where to begin. You start with the basics and often you soon find yourself with more questions than answers. Occasionally, you stop and ask yourself if you are heading in the right direction, trying to figure out your next move. Here are several personal stories I would like to share to help illustrate my point.</p><h3>The Rise of JavaScript</h3><p>It was around year 2012–2013. I was then mostly doing web development on PHP sprinkled on top with some jQuery-driven JavaScript. I was pretty comfortable in that area, however, I realized that frontend development has gone a long long way ahead. This was the time when AngularJS was dominating as the UI framework, and tools like Grunt, Gulp and Bower became increasingly popular. I had some good JavaScript fundamentals from the early days but honestly, this only helped me so far. The real challenge was figuring out how to write complex SPAs. There was a dozen of questions that needed to be answered like:</p><ul><li>Which framework to choose?</li><li>Do I need a CSS processor or a templating engine?</li><li>Which build tool to use?</li><li>What the hell is bower?</li><li>JS is messy, should I use CoffeeScript or TypeScript?</li><li>Is testing JavaScript even a thing?</li></ul><p>Gradually continuing with learning Node.js only multiplied my concerns. Books and online courses where helpful, but they where often outdated and I had to look for information in blogs and GitHub projects. These where up to date, however, the information there was scattered and it was difficult to get a wholistic view of the landscape and understand the role of each tool in it.</p><p>It was a period of intense learning and with some time, effort, and a some exploratory projects, I was able to reach a point where I felt comfortable with calling myself a frontend developer. But then new challenges came.</p><h3>All Hands on Deck</h3><p>We’ve successfully delivered several relatively complex SPAs and with that, our client’s appetite for rich user interfaces grew. We needed to onboard new frontend developers to address the increasing demand. We had a lot of experienced developers in our company with different backgrounds. Some have been doing Java development, even frontend development using GWT, others came from jQuery and a few had experience with more modern framework. The challenge was to understand the gaps in their knowledge, align it with our understanding of the current state of the ecosystem and derive a curriculum that would allow them to become productive as soon as possible.</p><p>We needed a way to quickly introduce a lot of new concepts and often we didn’t have the manpower to organize in-depth training sessions on each topic. Rather we produced overviews of our current tech stack and shared our thoughts on why we need each component. Something in the lines of, “we use TypeScript to make JS more descriptive and maintainable.”, “We use linters to provide assistance to developers”, “We use webpack to bundle the code together.” and etc. After some introduction we shared links to the relevant learning resources and expected our colleagues to do further investigation on their own.</p><p>It might not have been the perfect approach to sharing knowledge, but it worked and we were able to onboard more people to frontend development. Currently we have a community of frontend developers in our company, each doing their own thing and sharing new useful findings with the rest of the company.</p><h3>Above and Beyond</h3><p>When the dust of JavaScript fatigue had settled, it was time to look for new challenges. I’ve started looking into Go as an alternative language for backend development. We had use cases for developing simple micro-services and Go seemed like a good fit. Since I already have prior backend development experience, it’s unfair to say, that it was completely new to me. Of course, I had to learn Go as a language and get a hang of wring idiomatic Go applications, but a lot of the concepts are similar. Like, what do I use for unit testing? Dependency management? Linters? It wasn’t really about learning new concepts, but about finding the implementations for old ones, and since these were similar to other languages, I could reuse my prior experience, and adapt it to new technology. In this context, Go-centric blog posts, newsletters and awesome lists were a good source of information.</p><p>In the same time I am looking at the cloud sector and feel the same uneasy feeling that I had before starting frontend development. It takes time to get oriented in all the services offered by major cloud providers, containers and Kubernetes, Cloud Native projects and etc. Is “cloud fatigue” already a term? A comprehensive, birds eye view map of what’s going on would be highly appreciated.</p><h3>So what am I getting at?</h3><p>During my whole career as a developer, I found great value of guides that provide a high-level overview of what’s currently happening in a particular segment of the industry. Whether it’s JavaScript, Go or cloud technologies, they help you position yourself in the landscape, decide where you would like to be and find your way.</p><p>This is why I started the <a href="https://www.devtrails.io/">devtrails.io</a> project. It’s devoted to sharing experience and trends in the industry in forms of brief but broad introductory guides in a format that was influenced by mind maps, awesome lists, ThoughWork’s Technology Radar and others. We’ll start with web development and see where the journey takes us from there. I believe such guides can be useful for both beginners and experienced professionals so long as that they are kept well structured, not too subjective and up to date.</p><p>I’ll begin publishing the first guides soon and would appreciate your thought on this subject. Do you have similar personal stories to share? What kind of learning materials helped you establish yourself as a developer? Share your thoughts and help others learn from your experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d31df7f83f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devtrailsio/devtrails-and-the-three-perspectives-of-learning-5d31df7f83f5">DevTrails and the three perspectives of learning</a> was originally published in <a href="https://medium.com/devtrailsio">devtrails.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>