- Are responsibilities well defined?
- Are the collaborations well defined?
- Is coupling minimized?
- Can you identify potential duplication?
- Are interface definitions and constraints acceptable?
- Can modules access needed data—when needed?
<toolSet name="Code Checking"> | |
<tool name="Flake8" showInMainMenu="true" showInEditor="true" showInProject="true" showInSearchPopup="true" disabled="false" useConsole="true" showConsoleOnStdOut="false" showConsoleOnStdErr="false" synchronizeAfterRun="true"> | |
<exec> | |
<option name="COMMAND" value="/usr/local/bin/flake8" /> | |
<option name="PARAMETERS" value="--max-complexity 10 $FilePath$" /> | |
<option name="WORKING_DIRECTORY" value="$ProjectFileDir$" /> | |
</exec> | |
<filter> | |
<option name="NAME" value="Filter 1" /> | |
<option name="DESCRIPTION" /> |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
/** | |
* @brief Mapping functions from Eigen data types to OpenCV | |
* @author Eugene Khvedchenya <[email protected]> | |
* @details This header file contains code snippet for easy mapping Eigen types to OpenCV and back with minimal overhead. | |
* @more computer-vision.talks.com/articles/mapping-eigen-to-opencv/ | |
* Features: | |
* - Mapping plain data types with no overhead (read/write access) | |
* - Mapping expressions via evaluation (read only acess) | |
* | |
* Known issues: |
#include<stdio.h> | |
#include<string.h> | |
#include<stdlib.h> | |
#include<sys/mman.h> | |
typedef void V;typedef int I;typedef double F;typedef unsigned char C,*S;typedef long L; | |
#define O printf | |
#define R return | |
#define I(a...) if(a) | |
#define W(a...) while(a) |
# Type(<scope>): <subject> | |
# <body> | |
# <footer> | |
# Type should be one of the following: | |
# * feat (new feature) | |
# * fix (bug fix) | |
# * docs (changes to documentation) |
# How to encode and decode a file backed up as a series of printed QR codes | |
# Install the required tools | |
sudo apt-get update | |
sudo apt-get install zbar-tools imagemagick qrencode | |
################################################################################ | |
# Convert the file to a base 64 encoded format. Probably not needed as QR codes |
// Named tuple for C++ | |
// Example code from http://vitiy.info/ | |
// Written by Victor Laskin ([email protected]) | |
// Parts of code were taken from: https://gist.github.com/Manu343726/081512c43814d098fe4b | |
namespace foonathan { | |
namespace string_id { | |
namespace detail | |
{ |
by Bjørn Friese
Beautiful is better than ugly. Explicit is better than implicit.
I frequently deal with collections of things in the programs I write. Collections of droids, jedis, planets, lightsabers, starfighters, etc. When programming in Python, these collections of things are usually represented as lists, sets and dictionaries. Oftentimes, what I want to do with collections is to transform them in various ways. Comprehensions is a powerful syntax for doing just that. I use them extensively, and it's one of the things that keep me coming back to Python. Let me show you a few examples of the incredible usefulness of comprehensions.
import json | |
import requests | |
login = '' | |
passwd = '' | |
# connexion | |
r = requests.post("http://leekwars.com/api/farmer/login-token", data={'login': login, 'password':passwd}) | |
token = r.json()['token'] |