CodeIsGo.com

Ryan wrote neat article about Node.js bot application. It uses the Twitter API in order to make requests for that Twitter Bot, such as tweeting, retweeting, liking, and more. Bots are a fun way to improve your coding skills through creativity.

The tutorial is divided in 3 main parts:

• Hello, Twitter Bot
• Making the Bot smarter
• Deploying the Bot

It also deals with Tutorial application setup - which you will need in order to connect to Twitter API. And making a request is an asynchronous call. Example code is available for you in GitHub repository.

Randall Hunt published article on how to run your Integrated Development Environment (IDE) in the cloud. One of the first things you learn when you start programming is that, just like any crafts person, your tools matter. A powerful editor and testing pipeline supercharge your productivity.

This article is about AWS Cloud9, an Integrated Development Environment (IDE) for writing, running, and debugging code, all from your web browser.

AWS Cloud9 has all the typical IDE features you would expect:

• live syntax checking, auto-indent, auto-completion
• code folding, split panes, version control integration
• multiple cursors and selections
• also - it’s fast, even for large (100000+ line) files.
• no lag or other issues while typing
• ideal for pair programming

The AWS Cloud9 IDE is truly “cloud native”. The service is provided at no additional charge, and you only charged for the underlying compute and storage resources. When you create an environment you’re prompted for either:

• an instance type and an auto-hibernate time
• or SSH access to a machine of your choice

Also with AWS CodeStar you can easily provision an end-to-end continuous delivery toolchain for development on AWS. Now, with a few simple clicks you can provision a Cloud9 environment to develop your application.

Inian Parameshwaran article about difference between HTTP/2 Push and HTTP Preload. HTTP/2 PUSH is a feature that lets a server preemptively push resources to the client (without a corresponding request). HTTP Preload is a way to indicate to the browser resources it would require while loading the current page.

Both these mechanisms are used to optimize the unused bandwidth of the client to download resources preemptively and are an excellent way to decouple the download with the actual “execution” of the resource.

You will learn:

• How are they similar
• How are they different
• What kind of resources you can push / preload
• Cache semantics
• Resource prioritization

And much more. Excellent article with schemas and chart helping you understand both concepts. Well done!

Detailed article - tutorial from Google Cloud Platform (GCP) engineers about deploying faster. Creating custom images to boot your Google Compute Engine instances or Docker containers can reduce boot time and increase reliability. By pre-installing software into a custom image, you can also reduce your dependency on the availability of 3rd party repositories that are out of your control.

You choose how much software and configuration to include in your custom images - from minimalistic image to a fully-configured image—referred to as an immutable image in this tutorial.

The process of building images has a lot in common with building software: you have code (Chef, Puppet, bash, etc.) and the people who write it; a build happens when you apply the code to a base image; a successful build process outputs an artifact; and you often want to put the artifact through some tests.

In thisT article you will learn:

• Images type including what are foundation images and immutable images
• Architecture and implementation of an automated image building pipeline
• you also get loads if images explaining building process

And as a bonus the complete contents of the tutorial, including instructions and source code, are available on GitHub.

Christopher Ratcliff to the point article about user experience maps. An industry is struggling to agree on one standardised name for the same thing and author tries to find answer why is that.

This article is guide to different experience maps, including:

• Customer journey maps
• Customer experience maps
• User story maps
• Wireframes, workflows and wireflows
• Empathy maps and more …

Article also includes some points from Twitter discussion with UX community with answers when to create each type of map, importance of each etc. You will also find pictures and charts supporting each type of map in this article.

Ilya Bezdelev wrote tutorial how to create a static website publishing platform hosted in the cloud using several AWS services. It will run static website generator Hugo on AWS Lambda, store files in AWS S3 and serve them from AWS CloudFront. This is older (2015) but still very good article.

This tutorial uses content, code snippets and ideas from a number of open source projects.

Project integrates quite a few AWS products:

• S3 input bucket - whenever file is uploaded or deleted event is triggered for AWS Lambda
• AWS Lambda function
• Output S3 Bucket contains your static website
• CloudFront Distribution is a Content Delivery Network (CDN)
• Route 53 is a Domain Name Service (DNS)
• IAM - Identity and Access Management, is a service

Plenty of screen grabs and example code. Very valuable!

Lloyd Chan lengthy blog post about his experience with Rust (rustlang) as a experienced Scala developer primarily. This is very detailed article about his experience with loads of links to external resources and libraries in both Rust and Scala.

Rust’s memory/ownership model is, to me, its main killer feature; it gives you tighter control over the way your program consumes memory while maintaining memory-safety, all without having to ship a garbage collector with the runtime.

You will get loads information on following:

• Type system
• Macros
• Compile-time optimisations
• Syntax
• Interoperability with C
• Async IO

and much more. If you think about exploring Rust and have experience with Scala - this is a must read!

Emad Ehsan put together article about how to get started with Web Scraping in Chrome Headless. Chrome Headless is going to be industry leader in Automated Testing of web applications. Puppeteer is the official tool for Chrome Headless by Google Chrome team.

In this guide author will teach you how to:

• scrape GitHub,
• login to it,
• extract and save public emails of users
• while usin Chrome Headless, Puppeteer, Node.js and MongoDB.

You will get a good idea on Scraping with Chrome Headless and Node.js. Interesting info: Chrome Headless also supports WebGL. The article is detailed and with many screen-grabs documenting each step. And of course the code is available in GitHub repository.

Ariya Hidayat short and to the point post about hosting static web site with Firebase. He decided to abandon WordPress for his blog and switch to Hugo to generate the content and Firebase to host it. How did the authoring workflow change due to this switch?

As a static site generator, Hugo will construct all the HTML files from every blog entry written in Markdown format, based on a certain template. The huge benefit: all those Markdown files can be stored conveniently in a version control system. The ubiquitous git is a natural choice for doing so.

You also get overview:

• How to create an automated build job using GitLab CI
• How to prepare Docker image for in-container build process
• How to create an automated build job using GitLab CI
• Learn about benefits of hosting with Firebase (HTTP/2, free SSL/TLS for custom domain, security)

Using this setup, every single time I push to GitLab, the deployment process is automatically triggered. Usually it takes about a minute for the deploy job to finish. Good read!

Simos Xenitellis wrote an article for digitalocean.com about hosting web application in LXD containers. For many Docker became de facto container solution of choice, but there are different Linux containers available. This article is about LXD which can create and manage these containers. LXD provides a hypervisor service to manage the entire life cycle of containers.

In this tutorial, you’ll use LXD to install two Nginx-based web sites on the same server, each confined to its own container. Then you’ll install HAProxy in a third container which will act as a reverse proxy. You’ll then route traffic to the HAProxy container in order to make both web sites accessible from the Internet.

Article describes how to:

• Configure Linux users and LXD
• Configure and use block storage
• Configure networking
• How to create containers
• How to configure NGINX containers
• Configuring the HAProxy container

And much more. Plenty of code examples will guide you through whole process. Well worth reading!