cdzombak

collected links on rewriting software (or not)

• Rewrite Code From Scratch has good discussion of reasons to rewrite and reasons not to
• Things You Should Never Do, Part I is the commonly-cited argument from Joel On Software
• Re (tilly) 1: (OT) Rewriting, from scratch, a huge code base has discussion on when rewriting may be a good idea. It seems like there's more conversation in this thread, which I haven't read.
• code quality - When is a BIG Rewrite the answer? - Software Engineering Stack Exchange is a good answer, specifically calling out that the challenges are sometimes organizational rather than technical
• [Repeat yourself, do more than one thing, and... — programming is terrible](https://programmingisterrible.com/post/176

cdzombak

#!/usr/bin/env bash

set -u

NOW=$(date +"%F %T %Z")
OK=
if curl -s https://a2mi.social/api/v1/streaming/health | grep -c OK > /dev/null ; then
	OK="1"
else
	OK="0"

cdzombak

# based on sidekiq.chart.sh by codl <codl@codl.fr>
#
# apt install netdata-plugin-chartsd redis-tools
# put this in /usr/libexec/netdata/charts.d
# chown root:netdata /usr/libexec/netdata/charts.d/sidekiq.chart.sh && chmod +x /usr/libexec/netdata/charts.d/sidekiq.chart.sh

sidekiq_update_every=5
sidekiq_priority=9000

sidekiq_check() {

cdzombak

javascript:!function(){var%20e=window.getSelection().toString(),t=document.title.replace(%22%20-%20Jira%22,%22%22),n=e%3Fe:t,o=%22[%22+n+%22](%22+location.href+%22)%22;(function(e){var%20t=document.createElement(%22textarea%22),n=document.getSelection();t.textContent=e,document.body.appendChild(t),n.removeAllRanges(),t.select(),document.execCommand(%22copy%22),n.removeAllRanges(),document.body.removeChild(t)})(o)}();

cdzombak

it makes sense, and I suspect you’d see something similar on any device with a worn battery (edited)

basically everything battery powered changes clock speeds based on battery voltage level and whether you’re plugged in (_edit:_ also based on workload, so you’re not running at full speed and burning battery power when you’re not doing anything) (edited)

you can’t run a CPU at full speed when the battery voltage is low (edited)

so it follows that when the battery is worn out (and its top voltage is presumably lower), performance is consistently lower

the phone knows about battery age/wear, and takes that into account for the user-facing battery percentage meter

cdzombak

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>KeepAlive</key>
	<dict>
		<key>SuccessfulExit</key>
		<false/>
	</dict>
	<key>Label</key>

cdzombak

//
//  CDZScalingButton.h
//  ScalingButton
//
//  Created by Chris Dzombak on 10/17/15.
//  Copyright © 2015 Chris Dzombak. All rights reserved.
//

@import UIKit;

cdzombak

//
//  FileURL.swift
//  Created by Chris Dzombak on 11/16/16.
//

import Validated

public typealias FileURL = Validated<URL, FileURLValidator>

public struct FileURLValidator: Validator, _FileURL_Validating {

cdzombak

Hello Everyone,

The Swift 3 release is nearing completion, so it is time to look back on the release, learn from what happened, and use it to shape what we (the Swift community) do in the year ahead. Overall, Swift 3 is going to be an absolutely amazing release, and it is impressive how much got done. Thank you to everyone who contributed to making it happen. Instead of diving into a flurry of new proposals immediately, it is important to take stock of where we are, and look at the bigger picture.

Metapoint: this email is ridiculously long and covers multiple topics. Instead of replying to it directly, it is best to start new threads on individual topics that you’d like to discuss. Just tag them with “[Swift 4]” in the subject line.

Swift 3 Retrospective

Every year of Swift’s development has been completely different from the previous one, and I expect Swift 4 to continue this trend. With a goal of learning and improving year over year, here are some observations & retrospective about Swi

cdzombak

protocol ThingDelegate: class {
    var fooString: String { get }
    func foo()
}

class Controller: ThingDelegate {
    let fooString: String
    func foo() {
        print("foo")
    }