funmia

• System Design in Software Development

• The Lost Art of System Design - John Sundell, Swift & Fika 2018

• Grokking the Mobile System Design interview

• Mobile System Design Interviews (iOS and Android)

• How to Succeed in a System Design Interview

zthxxx

Note

For every body who using Win10/11 with new Office that you need to know:

to active Office without crack, just follow https://github.com/WindowsAddict/IDM-Activation-Script,

you wiil only need to run

irm https://massgrave.dev/ias | iex

BohdanOrlov

public protocol ViewControllerLifecycleBehavior {
    func afterLoading(_ viewController: UIViewController)

    func beforeAppearing(_ viewController: UIViewController)

    func afterAppearing(_ viewController: UIViewController)

    func beforeDisappearing(_ viewController: UIViewController)

    func afterDisappearing(_ viewController: UIViewController)

codediodeio

// No Security

{
  "rules": {
    ".read": true,
    ".write": true
  }
}

stinger

//: # Swift 3: CGD and URLSessionDataTask
import Foundation
import PlaygroundSupport


//: ### Create background queue
let queue = DispatchQueue.global(qos: .background)

//: ### Computed variable
var time:DispatchTime! {

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

esamattis

/*
        DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE 
                    Version 2, December 2004 

 Copyright (C) 2016 Esa-Matti Suuronen <esa-matti@suuronen.org> 

 Everyone is permitted to copy and distribute verbatim or modified 
 copies of this license document, and changing it is allowed as long 
 as the name is changed. 

hollance

Communicate between objects using channels

When you have two objects A and B, say two view controllers, that you want to have talk to each other, you can choose from the following options:

• NSNotificationCenter. This is anonymous one-to-many communication. Object A posts a notification to the NSNotificationCenter, which then distributes it to any other objects listening for that notification, including Object B. A and B do not have to know anything about each other, so this is a very loose coupling. Maybe a little too loose...

• KVO (Key-Value Observing). One object observes the properties of another. This is a very tight coupling, because Object B is now peeking directly into Object A. The advantage of KVO is that Object A doesn't have to be aware of this at all, and therefore does not need to send out any notifications -- the KVO mechanism takes care of this behind the scenes.

• Direct pointers. Object A has a pointer to Object B and directly sends it messages when something of interest h