Pinned Tweet
I built an open-source CLI tool called RN Build Doctor to help diagnose build failures and crashes using project configuration and build logs.
If you're still running into similar issues, I'd love for you to give it a try and share feedback on whether its diagnosis is useful.
🔗 lassiecoder.com/#/work/rn-bu…
#ReactNative #Expo
Today is the day to fold your apps 🙌
We wrote a guide you can give to your agents to get started.
On iPhone Duo your status bar and tab bar move into a rail on the side, so 𝚒𝚗𝚜𝚎𝚝𝚜.𝚝𝚘𝚙 is 0 now. This guide from @huntie, @__ubax__, and @chrfalch will help you adjust your apps for the fold:
expo.dev/blog/supporting-iph…
Unpopular opinion: most React Native performance problems aren’t React Native problems.
They’re:
- a FlatList without keyExtractor
- console.log left in production
- re-renders from unstable props
- images that aren’t resized
Fix these before blaming the framework.
#mobileappdev
Me estimating a feature: 2 days
The feature: 2 days
iOS code signing: 1 day
Android build failing for no reason: 1 day
“Works on my machine”: 3 hours
App Store review: 4 days
#devlife
lassiecoder | mobileAppDev retweeted
A week ago I shipped a small tool for something that kept eating my evenings: scrolling through React Native build logs to find the one line that actually broke.
rn-build-doctor crossed 250+ downloads in its first week.
#ReactNative #Expo
A week ago I shipped a small tool for something that kept eating my evenings: scrolling through React Native build logs to find the one line that actually broke.
rn-build-doctor crossed 250+ downloads in its first week.
#ReactNative #Expo
What it does: you pipe in a Gradle, Xcode, Metro, EAS or logcat log, and it points to the real error, shows the lines that prove it, and suggests a fix.
Runs offline. If it doesn't recognize the error, it says so instead of guessing.
npx rn-build-doctor analyze build.log
Shipped 0.1.6 this week after breaking real RN 0.87 and Expo SDK 58 apps on purpose: 'RCTBridge.h' not found, the AGP 9 Kotlin clash, Windows 260-char paths.
Send me a log it doesn't catch, that's how it gets better.
github.com/lassiecoder/rn-bu…
Unpopular opinion: most React Native apps don’t need a fancy state library.
They need fewer network requests.
lassiecoder | mobileAppDev retweeted
I built an open-source CLI tool called RN Build Doctor to help diagnose build failures and crashes using project configuration and build logs.
If you're still running into similar issues, I'd love for you to give it a try and share feedback on whether its diagnosis is useful.
🔗 lassiecoder.com/#/work/rn-bu…
#ReactNative #Expo
PHP, Node.js, GitLab and an Indian certificate authority, all in the same week.
AI is finding bugs that sat unnoticed for years, and attackers are moving within days.
Patching is no longer a 'next sprint' task.
lassiecoder | mobileAppDev retweeted
Datadog shipped an agent that you just tell "book a round trip flight" and it figures out the clicks itself and keeps testing it.
If this actually works I’m never writing a selector again.
#datadog
lassiecoder | mobileAppDev retweeted
Learning a new tool always goes the same way. At first it changes everything, then nothing works, then I realise it was my config all along. A week later I'm writing a thread about it.
#wednesdaythought
Datadog shipped an agent that you just tell "book a round trip flight" and it figures out the clicks itself and keeps testing it.
If this actually works I’m never writing a selector again.
#datadog
Learning a new tool always goes the same way. At first it changes everything, then nothing works, then I realise it was my config all along. A week later I'm writing a thread about it.
#wednesdaythought
lassiecoder | mobileAppDev retweeted
Ravana had 10 heads. My codebase has:
- A ‘quick fix’ from 2022
- Tests that pass on retry
- 47 deps, 12 actually used
- console.log(‘here 2’)
- // TODO: fix later
- catch (e) {}
- if (status === 3)
- utils.js, utils2.js, utilsNew.js
- : any
- A function nobody touches because ‘it works’
Today we burn them all 🔥
Happy Dussehra! 🏹
#Dussehra #DevLife
lassiecoder | mobileAppDev retweeted
A checklist for reviewing AI-written PRs:
1. Read the tests first. Do they test behaviour or mirror code?
2. Look for new deps nobody asked for
3. Check every catch block. AI loves swallowing errors
4. Run it on a real device, not just CI
What would you add?
#AI #CodeReview
lassiecoder | mobileAppDev retweeted






