roman2ing

One of the most insightful conversation of the recent months for me was this interview of Robert Martin by ThePrimeagen. Robert Martin is one of the authors of the original Agile Manifesto and the author of SOLID principles. They talked about a number of things including SOLID, TDD, Agile, and software development in general. Go was mentioned too.

My personal highlights of the interview

(quotes are heavily cleaned up by me and shortened without altering the meaning)

On developing concrete-to-abstract or the opposite way

Prime: I often find people reaching first for a pattern and an abstraction before the problem is ever solved. What do you think about that? Because I know you're very into the design first and then program kind of approach. <…> A lot of what I would call modern thinking at least “the Go way” of thinking is that you almost do the opposite: that you don't reach for abstraction first you actually try to get the thing itself first out and you allow the abstractions to more naturally

	;; Set package repositories
	(require 'package)
	(add-to-list 'package-archives '("gnu" . "https://elpa.gnu.org/packages/"))
	(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t)
	(package-initialize)

	(eval-when-compile
	(require 'use-package)
	(require 'use-package-ensure))

	if [[ ! -e ~/.zcomet/bin ]]; then
	git clone --depth=1 https://github.com/agkozak/zcomet.git ~/.zcomet/bin
	fi

	if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then
	source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh"
	fi

	source ~/.zcomet/bin/zcomet.zsh