Dean Radcliffe deanrad

Identity

Name: Dean Radcliffe Role: Software Engineering Manager Organization: Optum (part of UnitedHealth Group, Fortune 5)

Dean manages the mobile and web squads of an enterprise Design System team at Optum. He has 5 junior developers as direct reports across both squads, while senior developers report up to his manager Ari. He sits at the intersection of design systems, front-end engineering, and the growing push to integrate AI into enterprise-scale UI infrastructure. The design system is called Abyss. He works closely with product, scrum, and squad leads to deliver design system components across mobile and web for the broader UHG enterprise. People come to him for front-end engineering leadership, design system strategy, and increasingly for AI integration into developer workflows and end-user experiences. His team includes offshore members. He has a dev background and is actively growing into senior engineering leadership — moving from reading code after-the-fact toward upfront arch

Here are my indispensible git command-line tricks:

gh pr checkout NNNN - Check out a numbered PR to your working tree
gl3 - See the last 3 commits
gco - - Check out the last branch you were on
gco branch-name - Check out a local branch by full name
gbm DateInput - Shows git branches matching a pattern
gco $(gbm DateInput) - Check out the DateInput branch
glb - "Git last branches" - print a list of the most recent branches you've checked out
gro - "Git reset origin" - Does a reset to the remote branch, not merging with local edits

Regarding Logger functions and Uncaught Exceptions from Destinations

If one of the log functions throws an uncaught exception, what is affected? Some possibilities - all of which you'd probably want to avoid - are:

Some of the other loggers wouldn't fire
The code that triggered the log() call would see the exception.
The entire app might shut down

Now, if log destinations are explicitly try/catch wrapped, this is not an issue. But we might forget to do so. An Event Bus could help here. The event bus style of a logger would be: rather than composing multiple functions into a single one, each log destination becomes a bus listener. Let's say we have a dedicated Bus for logging, here's how we can write a log() function that puts a message on the bus for listener destinations to pick up:

LEADERSHIP LAB: The Craft of Writing Effectively https://www.youtube.com/watch?v=vtIzMaLkCaM

My takeaways:

This course is not about writing rules 3:04
Stop thinking about rules and start thinking about readers 3:55
The problems that domain experts have in their writing 4:00
Domain experts use writing to help themselves with thinking 4:51, if they don't do it this way, they can't think to the level they need
The challenge: the way that experts do their writing (to help with their thinking) is different to the way that readers can understand 6:53
The consequences 8:10 - 1. readers need to slow down and re-read many times 2. readers can't understand or misunderstand 3. readers give up

	InputFile ::= { Block } ;

	Block ::= DescribeBlock \| ItStatement ;

	DescribeBlock ::= "Describe:" Whitespace Description Newline Indent { Block } Dedent ;

	ItStatement ::= "It:" Whitespace Description Newline ;

	Description ::= { Character } ;

	Time Sheet (parody of Time Warp)

	In accounting, the books they're keeping
	Over money, they have the power
	So mark time closely, under Capital, mostly
	Reflecting your every hour

	I remember doing the timesheet,
	Fridays, whoa but then!
	The last day of the month fell

	<!DOCTYPE html>
	<html>
	<head>
	<title>TimeHop Your Inbox</title>
	<meta charset="utf-8" />
	<!-- Load dependencies -->
	<script src="https://unpkg.com/[email protected]/dist/bundles/rxjs.umd.js"></script>
	<script src="https://unpkg.com/antares-protocol/dist/antares-protocol.js"></script>
	<script src="https://unpkg.com/[email protected]/dist/redux.js"></script>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.4.2/umd/react.production.min.js"></script>

	const timerMachine = Machine({
	context: {
	elapsed: 0,
	duration: 5,
	interval: 0.01
	},
	initial: "running",
	on: {
	RESET: {
	target: "running",


	// Available variables:
	// - Machine
	// - interpret
	// - assign
	// - send
	// - sendParent
	// - spawn
	// - raise
	// - actions

	const { Omnibus } = require("omnibus-rxjs");
	const fs = require("fs");
	const { join } = require("path");
	const bus = new Omnibus();
	bus.spy(({ type, payload }) => console.log(type, payload));

	const dirPath = "./";

	const jsonMaker = bus.filter(
	({ type }) => type === "png",