cipas

{
  "vars": {
    "@gray-base": "#000",
    "@gray-darker": "lighten(@gray-base, 13.5%)",
    "@gray-dark": "lighten(@gray-base, 20%)",
    "@gray": "lighten(@gray-base, 33.5%)",
    "@gray-light": "lighten(@gray-base, 46.7%)",
    "@gray-lighter": "lighten(@gray-base, 93.5%)",
    "@brand-primary": "darken(#428bca, 6.5%)",
    "@brand-success": "#5cb85c",

cipas

@mixin circle($width, $border-width, $color) {
	width: $width;
	height: $width;
	border: $border-width solid $color;
	-webkit-border-radius: $width/2;
	 -moz-border-radius: $width/2;
	      border-radius: $width/2;
}

cipas

username: vagrant
password: vagrant

sudo apt-get update
sudo apt-get install build-essential zlib1g-dev git-core sqlite3 libsqlite3-dev
sudo aptitude install mysql-server mysql-client


sudo nano /etc/mysql/my.cnf

cipas

NativeScript vs Ionic Framework vs React Native

Pros & Cons

• Ionic CLI is a delight to work with, there are some aspects of the CLI such as text coloring, file template generators that are better than NativeScrtip’s CLI.
• It’s easier to get started with Ionic if you are coming from a web-development background, as NativeScript uses XML for it’s UI it will be easier for native Android developers to get started with it as XML is used to create UI in Android.
• Both have support for Angular 2, but you can use NativeScript without Angular using plain TypeScript.
• The debugging experience of Ionic is easy and quick than in NativeScript.
• For Ionic, if you wish to use native device features such as camera, file storage, etc you will have to rely on third-party plugins. For NativeScript, you do have plugins that are created by the NativeScript community but you can use native device features if you want right out of the box.
• Ionic has a reach ecosystem of servies and products that you can choose which w

cipas

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

cipas

const array = [2, 9, 1, 3]

const sortedArray = array
        .concat()
        .sort((x, y) => Math.sign(x - y));

cipas

update object

var state = {
    id: 1,
    points: 100,
    name: "Goran"
};

var newState = {

cipas

[alias]
	check = remote show origin
	up = !git pull --rebase --prune $@ && git submodule update --init --recursive
	save = !git add -A && git commit -m 'SAVEPOINT'
	undo = reset HEAD~1 --mixed
	done = push origin
	co = checkout
	cob = checkout -b
	cm = commit -am
	cm4 = "!f() { git commit -am \"$(git branch-name) $1\"; }; f"

cipas

alias status="git status"
alias co="git checkout"
alias fetch="git fetch"
alias save="git save"
alias pull="git pull"
alias push="git push"
alias cm="git add . && git commit -am "
alias stash="git stash"
alias pop="git stash pop"
alias check="git check"

cipas

Your Project Title

Short description of your project

Prerequisites

• Node.js > 12 and npm (Recommended: Use nvm)
• Watchman
• Xcode 12
• Cocoapods 1.10.1