...I've an idea for the rest of where Copilot is used.
848 karma · joined October 26, 2010
https://www.getyarn.io/yarn-clip/0def6aed-0b5b-4856-874a-d97...
One of the talks there was from Qantas Senior Check Captain David Evans, "Teamwork Under Duress" there, which was all about that flight and what happened.
It was an amazing talk, and I have a huge amount of respect for the job that airline pilots do.
Quantization is Q4_K_M (4-bit K-quants, medium)
From Pi, these are the up/down token counts:
Tokens: ↑147k ↓110k R26.5M
Prompt submitted at 18:52:54 BST on Sunday 16th August 2026, and finished at 04:05:27 BST on Monday 17th August 2026.
Last print out from the llama.cpp server logs:
881.42.815.480 I slot print_timing: id 2 | task 110233 | prompt eval time = 2742435.76 ms / 134911 tokens ( 20.33 ms per token, 49.19 tokens per second) 881.42.815.483 I slot print_timing: id 2 | task 110233 | eval time = 6312248.28 ms / 5804 tokens ( 1087.57 ms per token, 0.92 tokens per second) 881.42.815.483 I slot print_timing: id 2 | task 110233 | total time = 9054684.04 ms / 140715 tokens 881.42.815.484 I slot print_timing: id 2 | task 110233 | graphs reused = 114795 881.42.820.381 I slot release: id 2 | task 110233 | stop processing: n_tokens = 140714, truncated = 0
After about 10+ hours of digging, it has apparently found a bug in the Next.js framework, with an example app that replicates the bug, and a fix for now to disable prefetch in the Link component.
I had in my prompt asked it to discover the root cause of the bug and propose a fix, but I did not expect it to dig this deep.
I have tried to cancel a newspaper subscription in the UK a few times, which is only possible by telephone, and they have a serious churn-reduction program in place where I end up getting a major discount on the subscription.
Pi.dev has a feature where you can export the session as a html file and look at it later. I foresee that potentially you could store this in the same Git repository and get the benefit of reviewing how a particular code change came about during a session with an agent.
I guess the next step would be having the coding agent save that session context automatically in a folder in the git repository rather than requiring a human to export it.
This startup also seems to be operating in a similar space to tangled.org - moving code repos into a decentralised hosting environment.
- Unit tests - End to End testing with Cucumber and Puppeteer (or Playwright these days) - Code Coverage analysis - Lint and formatting checks - Tools like knit to remove unused code - Security checking tools like Synk and Socket - Size checking
If you look at what those tools do, they automate aspects of reviewing PRs. The question then becomes - what still gets done manually, and are there ways to automate that.
For me, I find the Pomodoro technique really effective, but there's a key caveat, which is that you try to focus on one thing at a time (which flies in the face of using multiple AI agents working on x number of things at the same time).
Another angle to explore is how much of the process of software development that we do manually can we automate, particularly the parts that still require human input (like code reviews). That may also help with reducing the cognitive load.
sudo pmset -a disablesleep 1
And if you want to revert that, run this:
sudo pmset -a disablesleep 0
Laptop: 13" MacBook Pro, M1 processor, 2020 edition Display: Apple Studio Display
Will buy the game later on, especially as it's only $5 - I guess that's a latte in the US these days?
Later on, I managed to crunch the numbers in the script, and realised I could dump them out and display them in a dashboard alongside the trade activity. So I built that too,
An excel spreadsheet could have done the same job as the dashboard, but the script for conversion was greatly aided by the AI tool. The work otherwise would have been a bit of manual coding and back-and-forth testing.
So when I see monthly budgets in the thousands for developers at some larger companies, I'm curious to learn how they are managing to spend that kind of figure: how much code/documentation are they feeding into their prompts, are they using agent orchestration systems to make the code factory run 24/7, and how much value is coming out the other end versus before?
And, if they are pouring thousands into LLMs per developer, have they considered looking at alternatives like having LLMs running locally on own hardware with their own agent harness?
Those are the kind of questions I'd love to ask - I just wonder how much stuff is truly cutting edge and how much might be wasteful?
I wanted to see if I could build an image editor for isometric graphics using HTML5 canvas, Svelte, Vite, and the. Rather than do all of the skeleton code setup, I figured “why not try and see if Claude can build the app scaffolding?”.
I gave it a prompt and watched it produce the scaffold, along with a few features I outlined in the prompt.
When I booted the app and saw that the features worked and that there had been an element of design to the layout, that was my mind-blown moment. In a period of about 45 minutes, I added some features and had a basic MVP at the end. I walked back home stunned.
That app is available for free at https://babspixel.com
https://www.ft.com/content/a401b0c0-fcc0-4bae-9f57-e8d5c0957...
A SimCity 3000 tile edge was equivalent to 64m, whereas in SimCity 4 it was 16m. The scale of the city in SimCity 3000 was bigger as a result.
Hoping to test this principle of largest possible map sizes out soon.
Today, not a single mention in that email.
I can't help but feel that there is a superficial chasing of trends at play here (adopting the same playbook that Block used earlier).
Question is, where will we all be in 3 years from now?
I've been able to get by with the $20pm Pro subscription and reap great value out of Claude Code.
I feel like it really is about:
- Don't feed it the works of Shakespeare into the context window if all it's working on is a few files. I actually don't have a Claude.md file in my projects.
- I write the prompt as if I was giving instructions to another developer or to myself on how I want to approach a specific coding, with a numbered step plan. I've actually been able to take the details written into a Jira ticket on a work project, feed it into Clade Code, and get really good results from it.
- If you are responsible for the output, then you need to review the output - that does put a natural constraint on the tool's usage, but ultimately it is you who uses the tool, not the other way around.
I feel like that's the thing - you have to find the right cadence, just like with running or driving a car - you need to find the level at which you control the car, at which you maintain a consistent pace, and at which you get code that does what you need it to do and meets the quality threshold you want.