zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

cliss

cask_args appdir: "/Applications"
tap "homebrew/cask-fonts"

brew "mas"

#### LAPTOPS ####
#cask "tripmode"
#### LAPTOPS ####

mas "Boop", id: 1518425043

bpierre

Switch To Vim For Good

NOTE: This guide has moved to https://github.com/bpierre/switch-to-vim-for-good

This guide is coming from an email I used to send to newcomers to Vim. It is not intended to be a complete guide, it is about how I switched myself.

My decision to switch to Vim has been made a long time ago. Coming from TextMate 1, I wanted to learn an editor that is Open Source (so I don’t lose my time learning a tool that can be killed), cross platform (so I can use it everywhere), and powerful enough (so I won’t regret TextMate). For these reasons, Vim has always been the editor I wanted to learn, but it took me several years before I did it in a way that works for me. I tried to switch progressively, using the Janus Vim distribution for a few months, then got back to using TextMate 2 for a time, waiting for the next attempt… here is what finally worked for me.

Original gist with comments: https://gist.github.com/bpierre/0a0025d348b6001394e0

lucasdavila

# see the current limits
$ sysctl -a | grep maxproc

# increase it
$ sudo sysctl -w kern.maxproc=xxxx
$ sudo sysctl -w kern.maxprocperuid=xxx

# run at startup
$ sudo vim /etc/sysctl.conf

correia

//
//  Swift-KVO
//
//  Created by Jim Correia on 6/5/14.
//  Copyright (c) 2014-2015 Jim Correia. All rights reserved.
//
//  Update: 6/17/2014
//
//  KVOContext has gone away; use the same idiom you'd use from Objective-C for the context
//

dabit3

GraphQL

GraphQL Schema

type Customer {
  id: ID!
  email: String!
}

kharrison

//
//  CoreDataController.swift
//
//  Created by Keith Harrison http://useyourloaf.com
//  Copyright (c) 2017 Keith Harrison. All rights reserved.
//
//  Redistribution and use in source and binary forms, with or without
//  modification, are permitted provided that the following conditions are met:
//
//  1. Redistributions of source code must retain the above copyright

danahartweg

#!/bin/sh

EMULATOR="cloud-firestore-emulator"
EMULATOR_TARGET=$(find ~/.cache/firebase/emulators/ -type f -name "$EMULATOR*.jar" | sort -r | head -n1)

if [ -z "$EMULATOR_TARGET" ]; then
  echo "Could not find the firestore emulator. Ending test run."
  exit 1
fi

navsing

//
//  Clubhouse.swift
//  Playground
//
//  Created by Nav Singh on 2/11/21.
//

import SwiftUI

struct Clubhouse: View {

saiday

    func fetchUserId() -> Observable<String> {
        return create{ (observer) -> Disposable in
            Client.fetchUserId() { [unowned self]
                 (userId: String?, err: ErrorType?) -> Void in
                    if let _ = err{
                        observer.on(Event.Error(err!))
                    } else {
                        observer.on(Event.Next(userId))
                        observer.on(Event.Completed)
                    }