In this article we are going to demonstrate how we write interview questions for our programming tests so hopefully you can learn from our techniques and build your own interview questions.
What matters to us most is developing high-quality questions. We’ll explain in detail how we do this.
Ok, let’s jump right in!
We divide the whole process of building a test into three parts:
(HINT — The last is the most important.)
Need to hire C++ developers? Not confident you have the resources to pick the best ones? Don’t worry – we’re here to help you!
We’ve assembled a team of expert C++ programmers who have worked hard to produce a collection of premade C++ interview questions you can use to bolster your interview process.
These C++ programming questions are your secret weapon for face-to-face interviews with prospective hires: answers, explanations, follow-up questions, code snippets. Even if you’re not a C++ guru yourself, these questions will let you conduct an interview like one, helping you find the master developers your project demands!
So here are the questions and answers:
Looking to hire a Java developer? We’re here to help!
We’ve brought together a team of highly skilled Java experts to create a set of ready-made Java programming questions you can use in your interview process.
These Java interview questions have everything you need for a face-to-face interview with prospective developers: possible right and wrong answers, explanations, and even follow-up questions. You don’t need to be a Java expert to find the best Java programmers for your company – just use the resources we provide and interview with confidence!
So here are the questions and answers:
I think we can all agree:
Hiring a programmer can be an extremely daunting task.
Especially if you can’t program.
How do you know what to do? What questions to ask? What steps to take to hire a software engineer that fits your business?
I know:
It’s overwhelming.
But it doesn’t have to be:
With our list of actionable tips, technical hiring will no longer be a headache and…
…you can double your chances of securing that dream software developer.
In today’s post, I will show you 24 of the best tips that’ll help you hire great programmers for years to come.
When building modern and socially-aware web applications, the related problems of user authorization and authentication arise repeatedly. The rich API ecosystem offered by the Web to developers is to some extent complicated by questions of security: How do we make sure our users are who they say they are? How do we ensure they have authority to access a particular resource, like a profile or a photo album?
OAuth2 is an authorization protocol that solves these problems, enabling secure access to third-party APIs (like Google Maps’ or Twitter’s) in your own applications. This tutorial discusses the use of OAuth2 in a small example application that will make use of a Google+ API.
Throughout this tutorial we will be referring to a tiny demo application called “Logonoff”. The only things we can do with it are log in, look at some data, and log out, and it looks like this:
The application makes use of a JavaScript library called hello.js that presents a unified API for interacting with a number of OAuth providers, such as Google, Facebook, Twitter, Github, and more. We chose to use hello.js because it is popular, versatile, and simple.
If you want to run Logonoff on your system, you can download the code and follow the instructions on Github.
Continue reading…
Angular 2 reached release candidate status a couple of weeks ago. As Angular 2 is making its way to a final release, now is a good time to take a look at the framework, what it does and what the main differences with Angular 1 are. In this tutorial, we will go through different examples and build a small sample traffic light application using Angular 2 to illustrate some of those new concepts. Let’s get started with components.
MongoDB is a schemaless document store that is easy to learn and quick to prototype with. Spring Boot and Spring Data make it even easier to get a simple application up and running. With a little bit of configuration and minimal code, you can quickly create and deploy a MongoDB-based application.
Elasticsearch is a highly-scalable document storage engine that specializes in search. Elasticsearch comes with reasonable default settings, but it will also easily scale to being able to search hundreds of millions of documents with sub-second latency. As you’ll see in this tutorial, the JSON-based nature of Elasticsearch, along with its simple REST API, make it easy to learn.
Elasticsearch is written in Java, so it should work on any operating system that can run Java. If you don’t have Java installed on your machine already, click here to download and install it. We’re going to do this tutorial with version 2.3.1 of Elasticsearch.
Elasticsearch is really simple to get up and running – you can have a one-node cluster running in just a few minutes with the following steps:
bin/elasticsearch if you are using Linux or OS X or bin/elasticsearch.bat if you are using Windows.
AJAX is an important part of many Rails applications. It allows for making client-side changes without the need to reload the page. In this tutorial, you’ll see a very simple example of how to send a JavaScript response from the server and some of the more interesting things that can be done.
For this tutorial, we’ll be using AJAX to toggle between showing and hiding a menu of download options, which prevents them from cluttering up your screen when they aren’t needed. To get the code on GitHub, click here.
First, let’s outline what the mini app should do.
Celery is an asynchronous task queue. It can be used for anything that needs to be run asynchronously. For example, background computation of expensive queries. RabbitMQ is a message broker widely used with Celery. In this tutorial, we are going to have an introduction to basic concepts of Celery with RabbitMQ and then set up Celery for a small demo project. At the end of this tutorial, you will be able to setup a Celery web console monitoring your tasks.
Let’s use the below graphic to explain the foundations:
The Broker (RabbitMQ) is responsible for the creation of task queues, dispatching tasks to task queues according to some routing rules, and then delivering tasks from task queues to workers.
The Consumer is the one or multiple Celery workers executing the tasks. You could start many workers depending on your use case.
The Result Backend is used for storing the results of your tasks. However, it is not a required element, so if you do not include it in your settings, you cannot access the results of your tasks.