kevinelliott

To support my open-source work, consider adding me on Patreon.

macOS 10.15 Catalina Mostly-Automated Setup

An easy to refer to document for regularly setting up macOS 10.15 Catalina.

Controversy

The topic of recipe-based frequent fresh reinstalls of macOS is a controversial issue. Some people are against reinstalling macOS, citing that they have never had an issue with Apple provided upgrade installs.

cellularmitosis

import UIKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

        let window = UIWindow(frame: UIScreen.main.bounds)

mvnrc

kevinelliott

macOS 10.13 High Sierra Mostly-Automated Setup

An easy to refer to document for regularly setting up macOS 10.13 High Siera, in flavor of my previous macOS/OSX setup gists:

• macOS 10.12 Sierra - https://gist.github.com/kevinelliott/7a152c556a83b322e0a8cd2df128235c
• Mac OS X 10.11 El Capitan - https://gist.github.com/kevinelliott/e12aa642a8388baf2499
• Mac OS X 10.10 Yosemite - https://gist.github.com/kevinelliott/0726211d17020a6abc1f

I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. I generally reinstall each computer from scratch every 6 months, and I do not perform upgrades between releases.

wojteklu

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

gfosco

// The before save handler will pass information to the after save handler to disable the
//   after save handler from creating a loop.
// It also prevents client side code from triggering the silent change, by using a different flag
//   that the client should never see.
// It should only be visible in the data browser, won't be sent to a client in an undefined state.
Parse.Cloud.beforeSave('TestObject', function(request, response) {
  handleComingFromTask(request.object);
  response.success();
});