Principal Engineer building in public (@onehausapp / @mcpscores). Previously CTO @ Illuvium, Principal @ Checkout dot com, Lead Architect @ ClearBank
London, England
Joined July 2016
- Tweets3.9K
- Following1.5K
- Followers1.3K
- Likes2.7K
Pinned Tweet
Hey hey 👋 Lots of new people recently, so let's get to know each other
I'm Stu. I'm a principal engineer who has spent years at places like Checkout and ClearBank. Whilst I'm building my future, I share interesting things and what I learn on the way
What are you working on?
CodeWithStu retweeted
ICYMI: For the 10th anniversary of "Site Reliability Engineering", we’ve rewritten the definitive Google SRE book! 📖
Featuring brand-new guidance on SRE for the agentic era, modern SLOs, and culture.
Get your copy today: goo.gle/SREbook
CodeWithStu retweeted
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
Worth trying?
Introducing Microsoft-Decision-1
Our model for fast decision-making that delivers top performance in latency and quality on structured decision tasks to outperform both LLMs and other decision models.
commandline.microsoft.com/mi…
This looks incredibly useful
llmfit 1.1.17 is out. Mouse support in the TUI, --memory-percent/--ram-percent flags, more honest speed estimates for CPU offload, deterministic
ranking and 40% faster search.
Which LLMs will actually run on your machine, now with better numbers.
github.com/AlexsJones/llmfit
Really starting to like the look of this next update. Onboarding experience is going to be so much nicer, plus the new homepage experience. Going to run with experimental feature flag so we can remove it/change it and force people to the old version if any issues.
What'd you think?
CodeWithStu retweeted
Connector submissions for @Muse are open 🚀
If you have MCP go here -> muse.ai/platform and submit ASAP
I'm CodeWithStu 👋
Principal Engineer building in public (@onehausapp / @mcpscores). Previously CTO @ Illuvium, Principal @ Checkout dot…, based in London 🇬🇧
Looking to meet other builders!
Just put myself on the map 👇
makermap.lol/CodeWithStu?v=i…
xitter.cf/CodeWithStu/status/209…
Over the past month, my releases to my app have improved retention by 25% - still a lot more to go, but we're definitely heading in the right direction
From this great review that Sofi kindly did for me, I started to redesign the homescreen, paywall and browse screens:
1. Homescreen should solve the "What do I do" question, so I've got a quick add now permanently on screen after the schedule, so when it's empty it displays prominently. This guides new and old users on what they should do next, and should also answer the question of what needs doing now
2. I've done away with swiping and gone for a more traditional nav bar at the bottom focusing on the main activities: schedule/shopping/chat
3. The browse household screen has been completely redesigned to be more inline with the rest of the app
4. Both the shopping list and chat now have suggestions to show you what you can do on that screen, with one tap add/chat functionality. Shopping suggestions actually remembers what you type most often too!
5. Trial status is now prominent, but takes up far less real estate and now changes colour when you're nearing expiry/expired to help draw attention.
6. The paywall itself is also a lot less wordy and concise, helping you understand the value quicker
There's still a lot of tidy up and checking to do over the next week, and I need to see how it feels to use day to day. I'll then release it with the onboarding changes under an experimental features flag so that people can try it and give me feedback before it rolls out to everyone.
The major downside is that I have to redo all of the app store screenshots, so I need to look into a tool for doing that so I don't have to reseed data for iOS/Android in like 8 languages again xD Send me your tools you use please!
Earlier today: OneHaus's App Store page. Now I'm going inside the app 📲 @CodeWithStu.
So far the onboarding is pretty nice 🙌
1. Too much text.
Contacts screen: question, subtitle, paragraph. It takes all that to reach the point, so it's hard to know where to focus.
Thread 👇
This just reinforces my decision to move off firebase for my app
github.com/firebase/firebase…
incase anyone has been wondering why their iOS apps are intermittently crashing since today morning 🙃
reminds me of the Facebook swizzling crash incident.
@Firebase pls help
I think i’ve just found a problem that was affecting my users that i possibly wouldn’t have ever found without ai.
TLDR: if you use a cloudflare tunnel you need to use —protocol http2 when you start the process as the default is currently quic, which can cause issues with some hosting.
Not all the time but it was trickling errors for me. Enough that i hit it whilst testing. Gave opus the client and server logs and it said yeah not your code, gimme cloudflare logs and sure enough there was the issue that lined up perfectly.
TIL
I have a retention problem in my house app. So here's the start of me tracking down the issues and fixing them one by one until sessions become way more sticky. Starting off with my north star, weekly engaged households. Goal is to keep this up going up and to the right.
CodeWithStu retweeted
Giving away a free app audit every day!
I’m new here, so this is my way of getting to know you and giving something back.
Every day I’ll roast an app: onboarding + paywall, where the magic (money) happens. 💸
Drop your App Store link below and I’ll tell you what I’d fix first.
