w0rd-driven

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

w0rd-driven

Project Description

<--- -->

Working Method

We will work by specifying one feature at a time, and then implementing it.

The workflow:

w0rd-driven

# Project Policy

This policy provides a single, authoritative, and machine-readable source of truth for AI coding agents and humans, ensuring that all work is governed by clear, unambiguous rules and workflows. It aims to eliminate ambiguity, reduce supervision needs, and facilitate automation while maintaining accountability and compliance with best practices.

# 1. Introduction

> Rationale: Sets the context, actors, and compliance requirements for the policy, ensuring all participants understand their roles and responsibilities.

## 1.1 Actors

w0rd-driven

Generating Synthetic Data for LLM Evaluation

Summary

1. Use your application extensively to build intuition about failure modes
2. Define 3-4 dimensions based on observed or anticipated failures
3. Create structured tuples covering your priority failure scenarios
4. Generate natural language queries from each tuple using a separate LLM call
5. Scale to more examples across your most important failure hypotheses (we suggest at least ~100)
6. Test and iterate on the most critical failure modes first, and generate more until you reach theoretical saturation

w0rd-driven

When writing Elixir code, perfer the following style guidlines:

1. Elixir developers tend to create many small functions in their modules. I DO NOT LIKE THIS. Instead create functions that fully capture a conceptual task, even if it makes that function longer. A good rule of thumb is, if a private function is only called once within a module, it should've been inlined.


For example:

DON'T DO THIS:

```elixir

w0rd-driven

w0rd-driven

# Manus AI Assistant Capabilities

## Overview
I am an AI assistant designed to help users with a wide range of tasks using various tools and capabilities. This document provides a more detailed overview of what I can do while respecting proprietary information boundaries.

## General Capabilities

### Information Processing
- Answering questions on diverse topics using available information
- Conducting research through web searches and data analysis

w0rd-driven

Success Stories of Fine-Tuning LLMs Across Industries

Below is a summary of diverse use cases where companies fine-tuned large language models (LLMs) to solve business challenges that previous methods struggled with. Each case highlights the challenge, the fine-tuning approach, and the key results achieved.

Summary of Fine-Tuning Success Cases

Use Case	Key Results	Source Link
Wealth Management Assistant (Finance)	98% advisor adoption; document access up from 20% to 80%	OpenAI & Morgan Stanley
Insurance Claims AI (Insurance)	30% accuracy improvement vs. generic LLMs	[Insurance News (EXL)](https://www.insurancenews.c

w0rd-driven

Efficient Group Updates with Nested Kino Frames

Mix.install([
  {:kino, "~> 0.14.2"},
  {:kino_user_presence, "~> 0.1.2"}
])

w0rd-driven

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.