rajatmohanty

// Playground - noun: a place where people can play

import Foundation
import UIKit

//Implicit inmutable variable
let dojoNinjas = 1
//Implicit mutable variable
var ninjaApprentices = 1500

rajatmohanty

//Original Content : http://yourcodesucksexception.blogspot.in/2015/11/things-ive-learned-while-building-ios.html

xcodebuild -workspace PULPulsate.xcworkspace -scheme PULPulsate -sdk iphonesimulator -configuration Release
xcodebuild -workspace PULPulsate.xcworkspace -scheme PULPulsate -sdk iphoneos -configuration Release
 
mkdir -p ${TARGET_BUILD_DIR}/../PULPulsate${CURRENT_PROJECT_VERSION}
 
cp -r ${TARGET_BUILD_DIR}/../Release-iphonesimulator/ ${TARGET_BUILD_DIR}/../PULPulsate${CURRENT_PROJECT_VERSION}
 
lipo -create "${TARGET_BUILD_DIR}/../Release-iphoneos/PULPulsate.framework/PULPulsate" "${TARGET_BUILD_DIR}/../Release-iphonesimulator/PULPulsate.framework/PULPulsate" -output "${TARGET_BUILD_DIR}/../PULPulsate${CURRENT_PROJECT_VERSION}/PULPulsate.framework/PULPulsate"

rajatmohanty

Code Review Checklist

AMOP Principle

• A — Accessible, is the code accessible?
• M — Maintainable, can the code be easily reasoned about?
• O — Organized, does the naming and file structure of the code make sense?
• P — Performant, are there any performance issues introduced by the code?

rajatmohanty

Instructions for manually symbolicating partially symbolicated Crash Logs in Xcode 7.2:

Create a folder on your computer. I called mine “Crash Stuff” in the example.

We’re going to need 3 things to symbolicate .crash files.

1. The .dSYM that relates to the crash files.
2. The symbolicatecrash script
3. The .crash file that we want to symbolicate

rajatmohanty

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

rajatmohanty

import Foundation
import Alamofire
import RxSwift
import RxCocoa


protocol ClientProtocol {
    func request<Response>(_ endpoint: Endpoint<Response>) -> Single<Response>
}

rajatmohanty

| Title | Description

rajatmohanty

Configure Git to use a proxy

##In Brief

You may need to configure a proxy server if you're having trouble cloning or fetching from a remote repository or getting an error like unable to access '...' Couldn't resolve host '...'.

Consider something like:

rajatmohanty

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

rajatmohanty

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.