#include <benchmark/benchmark.h>
namespace bench = benchmark;
#include <chrono>
#include <ctime>
#include <iostream>
#include <iomanip>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// | |
// main.cpp | |
// test | |
// | |
// Created by Slava Melanko on 12/17/18. | |
// Copyright © 2018 Slava Melanko. All rights reserved. | |
// | |
#include <algorithm> | |
#include <iostream> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Есть 3 типа собеседований: | |
1 проверка уровня англ языка с HR (Human Resource) | |
2 техн собеседование с главным разработчиком, менеджером или же архитектором | |
3 финальное собеседование с заказчиком | |
зачастую они идут в такой же последовательности (бывает что 2 и 3 объеденены в один) | |
если SM (Sales Manager) не уточнил такие пункты как | |
- с кем собеседование и во сколько | |
- какова цель | |
- на каком языке |
Requirements are statements about an intended product which specify what it should do or how to do it. For requirements to be effectively implemented and measured, they must be specific, unambiguous and clear.
- Business
- Business objectives
- Sponsor point of view
- Scope of the project
- User
- User point of view
- User goals
- User inputs and outputs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#include "fields_alloc.hpp" | |
#include <boost/beast/core.hpp> | |
#include <boost/beast/http.hpp> | |
#include <boost/beast/version.hpp> | |
#include <boost/asio.hpp> | |
#include <boost/filesystem.hpp> | |
#include <chrono> | |
#include <cstdlib> | |
#include <cstring> |
- End-user launches a mobile application or visits site, a request will be sent to the ad-exchange
- On the ad-eachange side this request will be futher passed to all the bidders who trade in that ad-exchange
- Those bidders get the information about device, application, user, ad template and etc, and they need to decide if they can place a bid for this particular request, and if so, how much to bid
- Once ad-exchange receives all the responses from bidders it will pick the winner
- Compilers:
- Sources: