Tim Huckle (@timhuckle) header
Tim Huckle (@timhuckle) profile picture

Engineering Director @AJBell

London
Joined April 2009
Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)Photo by Tim Huckle (@timhuckle)
Tim Huckle retweeted
Replying to @techtoby__
“The models just aren’t there for complex code” - man who used GitHub copilot 2 years ago
1
2
254
19,720
Tim Huckle retweeted
Tired: Two-pizza teams Wired: Two-slice teams @danshipper on the best team structure in the AI-era
178
199
172
2,151
567,293
Tim Huckle retweeted
A US financial services company scoped three infrastructure projects for five engineers across two quarters. Our two-person Velocity Pod delivered all three in one quarter: automated funds movement, an underwriting portal, and investor access. I want to explain what made that possible, because “two engineers using AI” leaves out most of the useful information. The platform was already processing live transactions. Existing code, existing integrations, existing customers whose money had to keep moving. An audit found several things preventing the agents from working reliably. Domain rules weren’t documented clearly. Build and test commands were difficult to discover. Different modules followed different conventions. Recurring tasks had no established procedure the agent could follow. So the agents filled in the gaps themselves. That is a pretty expensive place to let software guess. We documented the architecture, domain terminology, coding conventions, and exact verification commands at both repository and module level. We also packaged recurring procedures into reusable skills. Adding an endpoint or writing a migration now had a documented approach. Every task started with a specification. Tests came before implementation. Every change passed automated verification before merge, with a PR review agent checking against the spec and project standards. All three projects used a shared architecture, so each subsequent project started with a foundation already in place. The result: 60% fewer engineers than planned, half the estimated timeline, and about $200 in AI compute per developer per month. The lesson I’d take from this is that your codebase contains less of your company’s knowledge than you think. Your experienced engineers know which conventions matter, where the exceptions live, and why something was built a particular way. An agent needs access to that knowledge too. Making it explicit is part of the engineering work. That’s what our Velocity Framework was built for.
32
28
12
96
405,518
I was sitting far too close to the City fans on Sunday to let this one rest. No doubt cleverer people than I looking at the future of VAR; but if 30 minutes coding and a LLM can get me the right decision on this and other tests in under a minute then…
If James Alexander Gordon (AI) operated VAR (sound on). Please like and repost.
58
🚨 SECURITY WARNING 🚨 Brevo (formerly Sendinblue) has reportedly been compromised. Phishing emails impersonating CoinTracking, Trezor and BitBox and likely several others in the industry are currently making the rounds. DO NOT: ❌ Click any links ❌ Download attachments ❌ Enter your seed phrase anywhere online Your seed NEVER belongs on a website. Ever. Please warn others.
7
58
14
158
22,503
Tim Huckle retweeted
device_preview 3.0 is out 🎉 Switch your running @FlutterDev app to any device — screen, safe areas, locale, dark mode, text scale — instantly. No rebuild, no simulator. Rebuilt from scratch. One line to integrate. A thread 🧵
11
49
5
377
16,841
Tim Huckle retweeted
Meet Gemma 4 12B! A unified, encoder-free multimodal model designed to bring high-performance intelligence directly to your laptop, and released under an Apache 2.0 license. Bridging the gap between edge efficiency and advanced reasoning. Here is what’s new with Gemma 4 12B: 👇
392
1,691
603
12,157
3,278,078
Tim Huckle retweeted
Flutter Agent Lens MCP Server Agent-first MCP server to debug, profile, and optimize running Flutter apps pub.dev/packages/flutter_age…
2
14
2
133
6,846
🤯 This is scary good for something rendering in real time. Selfie-based liveness checks ask for a fixed set of motions: head turn, blink, close approach to the camera. This demo nails all of them, including the part that usually breaks for synthetic faces (skin micro-texture and forehead wrinkles holding up at close range). Without the side-by-side at the bottom, you wouldn't know it's not Will Smith. Source: Incognia
57
115
27
639
104,051
Tim Huckle retweeted
CloudFlare's post is one of the better written reports on Mythos. Worth a read for both devs and cybersec folks.
Cloudflare's security team spent the last few weeks testing Anthropic's Mythos against fifty of our own repositories. What we learned about offensive AI, why faster patching is the wrong reaction, and what the architecture around vulnerabilities has to look like next. cfl.re/49BRUqW
5
47
677
545,025
Tim Huckle retweeted
A preview for Pro users: a new personal finance experience in ChatGPT. Pro users in the U.S. can securely connect financial accounts, see where their money is going, and ask questions based on the information they choose to connect. Your full financial picture, now in ChatGPT.
1,255
1,545
1,991
24,192
16,762,668
HSBC Apple Pay. Possibly all(?) HSBC UK customers have woken to an email from them confirming registration of their card on to Apple Pay. Contact centre on +30 minute wait times as concerned customers phone in. I’m told the comms were sent in error. @HSBC_UK
1
13
2,938
Tim Huckle retweeted
Jack Dorsey just said the quiet part out loud. "Middle management exists because humans were the only option for information routing. They aren't anymore." I'm running a small team right now. We just hit the point where I can't keep everything in my head anymore. I know this problem intimately. A human can manage 3-8 people effectively. That's it. I'm at that edge right now. The moment you cross it, you need another layer. Another person to route information. Another meeting to align. Another delay. The Roman Army invented hierarchical management 2000 years ago. 8 soldiers → 80 men → 480 → 5,000. Every company still uses this structure today. I assumed this was just how it works. Jack Dorsey just published why that's about to end. The Constraint I'm Living Right Now We're at the inflection point. Small enough that I can still talk to everyone directly. Big enough that I'm becoming the bottleneck. Every decision waits for me to route context between people. I've been watching AI tools for 2 years. Claude, ChatGPT, every new model. I thought the answer was copilots. Give everyone AI assistants to work faster within the existing structure. Block just published something that made me realize I was thinking too small. What Block Is Actually Building They're not giving everyone copilots. They're replacing what the hierarchy does with a "world model." Two parts: Company World Model: How Block understands its own operations. This replaces me. The information I carry in my head, the context I relay between people, the decisions I route. The world model does that. Customer World Model: Block sees both sides of millions of transactions through Cash App and Square. Money is the most honest signal. People lie on surveys, but transactions are facts. That understanding compounds every second. Here's what got me: When Block's intelligence layer tries to compose a solution and can't because a capability doesn't exist, that failure becomes the roadmap. Customer reality generates the backlog directly. No product manager hypothesizing. No guessing what to build next. The system observes what customers actually need. Block normalizes to three roles: - ICs: Build capabilities, models, interfaces. The world model provides the context I currently provide. They don't wait for me to tell them what to do. - DRIs: Own specific problems for 90 days. Full authority to pull resources from any team. Then rotate to new problems. - Player-Coaches: Still build. Still code. Develop people. But don't spend days in alignment meetings because the world model handles that. No permanent middle management layer. Why This Matters to Me I'm at the exact moment where most companies add a layer. Hire someone to manage the growing team while I focus on strategy. Standard playbook. But that just delays the problem. When we hit 30 people, we need another layer. Then another at 100. Each layer slows us down. Block is saying: what if you don't add layers at all? What if the AI becomes the coordination layer? I don't know if Block's execution will work. This could break spectacularly. But the question is too important to ignore. Dorsey asks: "What does your company understand that is genuinely hard to understand, and is that understanding getting deeper every day?" If the answer is nothing, AI is just cost optimization. Cut headcount, improve margins, get absorbed. If the answer is deep, AI reveals what your company actually is. The Uncomfortable Truth I'm Sitting With For 2,000 years, we had no alternative to hierarchy. The question was never whether you needed layers. The question was whether humans were the only option for what those layers do. They aren't anymore. I'm watching this closely. Not because I have answers. Because I'm living the exact problem Block is trying to solve. And if they figure it out, it changes everything. Follow @heyshrutimishra for more on AI reshaping how companies actually work. I'm figuring this out in real time.
41
110
7
906
310,045
Tim Huckle retweeted
I see some weird things but this takes the biscuit. A vulnerability in the Companies House website, that let anyone view the private dashboard of any one of the five million registered companies, see directors' personal details. And modify them.
369
1,504
528
7,129
1,625,573
Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off at AWS
Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking? The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China).
180
707
105
8,531
1,278,341
Tim Huckle retweeted
we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack
8,446
6,393
13,658
50,202
64,580,640
Tim Huckle retweeted
the cybersecurity industry is about to get completely disrupted.. 💀 someone just open-sourced a fully autonomous AI Red Team. it’s called PentAGI. multiple AI agents that talk to each other to hack a target. zero human input.
420
1,357
210
9,156
971,283
Tim Huckle retweeted
Over 1,300 Stripe pull requests merged each week are completely minion-produced, human-reviewed, but contain no human-written code (up from 1,000 last week). How we built minions: stripe.dev/blog/minions-stri….
164
151
157
1,861
1,609,774