David Bremner dbremner

"Scar Tissues Make Relationships Wear Out"

04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.

This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.

[Laughter]

> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation

Moved to https://github.com/nobssoftware/nocommit

There are three easy to make mistakes in go. I present them here in the way they are often found in the wild, not in the way that is easiest to understand.

All three of these mistakes have been made in Kubernetes code, getting past code review at least once each that I know of.

Loop variables are scoped outside the loop.

What do these lines do? Make predictions and then scroll down.

func print(pi *int) { fmt.Println(*pi) }

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.

	using System;
	using System.Collections.Generic;
	using System.IO;
	using System.Linq;
	using Mono.Cecil;

	namespace ClrToStringOverrides
	{
	internal class Program
	{

	private void EnableStoreTodosAndReminders(RDOStore store)
	{
	//Enable store for reminders
	var reminders = store.Reminders;
	reminders.EnableStoreReminders();

	//Collection some folders we need
	var rootFolder = store.RootFolder;
	var taskFolder = store.GetDefaultFolder(rdoDefaultFolders.olFolderTasks);
	var inbox = store.GetDefaultFolder(rdoDefaultFolders.olFolderInbox);

	object Nullable {
	sealed trait NullableTag
	type Nullable[A] = A with NullableTag

	def nullAs[B]: Nullable[B] =
	null.asInstanceOf[Nullable[B]]

	implicit class ToNullable[A](val a: A) extends AnyVal {
	def `?`: Nullable[A] = a.asInstanceOf[Nullable[A]]
	}

	/*
	Copyright (c) 2024 Orson Peters <[email protected]>

	This software is provided 'as-is', without any express or implied warranty. In no event will the
	authors be held liable for any damages arising from the use of this software.

	Permission is granted to anyone to use this software for any purpose, including commercial
	applications, and to alter it and redistribute it freely, subject to the following restrictions:

	1. The origin of this software must not be misrepresented; you must not claim that you wrote the

	function Set-WinStoreSetting {
	param (
	[Parameter(Mandatory=$true, Position=0)][string]$PackageName,
	[Parameter(Mandatory=$true, Position=1)][string]$SettingName,
	[Parameter(Mandatory=$true, Position=2)][string]$SettingValue
	)

	$settingsFile = [IO.Path]::Combine($env:LOCALAPPDATA, 'Packages', $PackageName, 'Settings\settings.dat')

	# temporary paths

	Rich Hickey on becoming a better developer

	−
	Avatar
	Rich Hickey • 3 years ago
	Sorry, I have to disagree with the entire premise here.

	A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.

	Mastery comes from a combination of at least several of the following: