Kyle Howells kylehowells

Projects

Runner-Up: Doctor of Credit

Creator: Evan Mullen
Description: Extract structured data about bank deposit bonuses from the Doctor of Credit website.

Prerequisites

Google Chrome CLI entrypoint

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

Panelists:

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

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

Q: What's the best approach to updating my app's UI for the new design?

A:

I think the best approach is to start from either the top down or the bottom up---however you perceive the hierarchy of your application. Focus on the big structural parts, since they tend to be most affected by the design and are often reflected in your code structure. Start there, then focus on the smaller elements.

Follow-up (Mohammed):

What’s the first class way to use PhotoKit to reimplement a high performance photo grid? We’ve been using a LazyVGrid and the photos caching manager, but are never able to hit the holy trinity (60hz, efficient memory footprint, minimal flashes of placeholder/empty cells)

A few things. It sounds like you're using the PHCachingImageManager already, which is definitely recommended.

One kind of specific note there—you want to use that to get media content delivered before you need to display it. So, for example, let's say you're showing a large grid of photos. You can be prefetching before and after, in expectation that the user's going to scroll. Or, if you're in a one-up situation, prefetching left and right so that you know the user is likely going to swipe, and you can quickly deliver those images to the screen and cache them.

Another thing you should really make sure you're doing is specifying the size you need for the grid size. For example, if your app supports showing a smaller grid

Use `var` in `struct` in Swift

TL;DR: Use var for properties in struct as long as it serves as a nominal tuple. In most cases, there is no obvious benefit to using let for struct properties.

Simple Example

Let's start with a simple example:

struct MyStruct {

	// Windsurf Auto Press Continue v13.2 (with added logging)
	(() => {
	const SCRIPT_NAME = 'Windsurf Auto Press Continue v13.2 (logged)'; // Updated name for clarity
	let intervalId = null, lastClick = 0;

	// --- Config ---
	const BTN_SELECTORS = 'span[class*="bg-ide-button-secondary-background"]';
	const BTN_TEXT_STARTS_WITH = 'continue';
	const SIDEBAR_SELECTOR = null;
	const COOLDOWN_MS = 3000;

	import torch
	from safetensors.torch import save_file

	INPUT_NAME = "model_weights.ckpt"
	OUTPUT_NAME = "model.safetensors"

	state = torch.load(INPUT_NAME, map_location="cpu")
	new_state = {}

	for key, value in state.items():

	import SQLite3
	import Foundation

	func main(dbPath: String) {
	// Pointer for database connection
	var db: OpaquePointer?

	// Open database
	guard sqlite3_open(dbPath, &db) == SQLITE_OK else {
	print("Error opening database: \(String(cString: sqlite3_errmsg(db)))")

	"use client";

	/* eslint-disable @next/next/no-img-element */
	import Link from "next/link";
	import { useState, useEffect } from 'react';
	import {
	AppBskyFeedDefs,
	AppBskyFeedPost,
	type AppBskyFeedGetPostThread,
	} from "@atproto/api";