Hiroki Nagasawa pixyzehn

(Summary generated by ChatGPT based on the automatic transcription. Transcript is attached to this Gist)

Panelists:

Host: Shashank
Panelists: Michael, Erik, Richard, Ronan

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Pre-Transformer Models

Debugging the Swift Toolchain

Use these steps to debug components of the Swift toolchain. This allows you to see Swift's source code from the debugger – instead of disassembly. The debugger can also provide some variable names and values. This has been initially tested with libswiftCore.dylib.

These instructions were updated as of Swift 5.2.1.

	#!/bin/zsh

	# Test if the Swift compiler knows about a particular language feature.
	#
	# Usage:
	#
	# swift-has-feature [--swift SWIFT_PATH] [--language-version LANGUAGE_VERSION] FEATURE
	#
	# The feature should be an upcoming or experimental language feature,
	# such as `"StrictConcurrency"` or `"ExistentialAny"`.

	import SwiftUI

	/// A wrapper view that provides a mutable Binding to its content closure.
	///
	/// Useful in Xcode Previews for interactive previews of views that take a Binding.
	struct Stateful<Value, Content: View>: View {
	var content: (Binding<Value>) -> Content
	@State private var state: Value

	init(initialState: Value, @ViewBuilder content: @escaping (Binding<Value>) -> Content) {

	// A fun little game written in SwiftUI
	// Copyright (c) John Sundell 2020, MIT license.
	// This is a hacky implementation written just for fun.
	// It's only verified to work on iPhones in portrait mode.

	import SwiftUI

	final class GameController: ObservableObject {
	@Published var plane = GameObject.plane()
	@Published private(set) var clouds = [GameObject]()

	// Don't forget to prefix your category!

	#import <UIKit/UIKit.h>

	NS_ASSUME_NONNULL_BEGIN

	@interface UIWindow (PSPDFAdditions)

	#if TARGET_OS_UIKITFORMAC

	/*:
	This is a concept re-implementation of the @Binding and @State property wrappers from SwiftUI

	The only purpose of this code is to implement those wrappers myself
	just to understand how they work internally and why they are needed,

	⚠️ This is not supposed to be a reference implementation nor cover all
	subtleties of the real Binding and State types.
	The only purpose of this playground is to show how re-implementing
	them myself has helped me understand the whole thing better