Voice-based interfaces are becoming commonplace. Voice assistants such as Siri and Cortana have been around for a few years, but this past holiday season, voice-driven devices from Amazon and Google made their way into millions of homes.

Recent analysis from VoiceLabs estimates that 24.5 million voice-driven devices will be shipped this year, almost four times as many as last year. As experience designers, we now have the opportunity to design voice experiences and interfaces!

A new interface does not mean that we have to disregard everything we have successfully applied to previous interfaces; we will need to adapt our process for the nuances of voice-driven interfaces, including conversational interactions and the lack of a screen. We will look at how a typical genie in a bottle works, discuss

Finding an awesome developer requires that you are clear on what you’re looking for. Do you want a full-stack or a front end / back end person? Do you need specific skills like knowledge of AI, blockchain, or big data?

Unless you have a specific reason, don’t hire technology-specific. Instead, hire based on fundamental knowledge.

Over the years, I’ve interviewed hundreds of developers. One of my biggest learnings is that there can be no assumptions. I’ve interviewed people with a Masters in Computer Science who had trouble writing a for-loop that iterated through an array.

So the first rule is to hire people who (preferably) have fundamental knowledge, coding experience, and a willingness to constantly learn new languages and skills.

This post assumes that you at least have some working knowledge of Angular reactive forms.

Let’s say this is our structure:

We need to transform this to an Angular form. Our goal is to render a list of skills with a checkbox that will be un/checked based on the selected key from each skill.

Let’s create the form:

Our form is just a group with one key — skills.

The buildSkills() method is responsible for —

Let’s stop for a second and recognize the final structure without the form builder.

Now we can write the HTML.

The code is straightforward. We are just looping over the skills controls and binding each skill to a checkbox.

This is Part 2 of a series of articles for programmers looking to upgrade their skills. Part 1 took us through the very beginning stages where we set out to find the most efficient way to go from zero to an employable developer. Today, we are going to take things a whole lot further.

This article is for all the developers, coders, programmers out there who are looking to make a jump in their career after having had a few years in the industry (or you may be just starting out but would like to see the sort of path you have to go on). This article is for those with a simple desire: You want to be considered a