Pinned Tweet
My main aim is to understand the logic behind JavaScript. I just don't want to write code, I want to write solutions 🙏
Eworld Tech🍁 retweeted
One lesson my facilitators @blessingpeters_ and @Eworld_Tech at @FutureforgeL keep reminding me of is PRACTICE.
Frontend dev. requires patience. Your code won’t always work and you won’t understand everything immediately.
Make mistakes, troubleshoot, correct them & try again.
Eworld Tech🍁 retweeted
Very tired of seeing AI generated tweets (yes, I still call them tweets). The patterns in the text are so obvious & I can’t take the content seriously as soon as I spot them.
A lot of them come from real accounts with people I’ve followed for a while, and before AI their tweets were fine. Better, in fact.
Eworld Tech🍁 retweeted
Crashes throw. Jank doesn't.
🎉 Finally live: Keyframer inspector, like Sentry but for motion. The line of code behind every dropped frame.
🔍 Inspector, on your desk
📈 Motion Vitals, in production
⚡ One command to set it up
React Native, iOS, Android, Flutter. Open-source SDKs (MIT).
The best chat UX trick is a lie that comes true: show the message as sent the moment someone taps, then confirm with the server and quietly roll back if it fails.
2
94
If your mobile app needs a second request just to render the first screen, the problem is the API payload, not the client. We stopped adding loading states and asked the backend to send what the screen actually needs.
1
71
Context and effort solve different problems. Context gives it the facts, effort gives it room to reason with them. Simple tasks need neither the extra tokens nor the wait.
Using High for AI is a skill issue. There is no reason you should be going above medium, except you do not understand how to provide enough info in context.
1
47
Today's plan: one small fix. Today's reality: three files, two refactors, and a bug that was there all along.
1
67
Before adding stickers to our app, I read the GIPHY terms. A beta key allows 100 calls an hour for the whole app. Read the limits before you build the feature.
2
102
Bottom sheet + keyboard + toggling inputs in React Native is a trap. Switching an input's props never behaved. Mounting and unmounting it did.
4
85
Rewrite day 1: "this is a mess." Rewrite day 3: "this is a mess that's holding up the whole building." 😂
Halfway through a rewrite, you realise why the previous engineer made those decisions.
That part you wanted to simplify has three other services depending on its behaviour.
I think rewriting someone’s code can change your opinion of them pretty quickly.
3
138
Eworld Tech🍁 retweeted
Halfway through a rewrite, you realise why the previous engineer made those decisions.
That part you wanted to simplify has three other services depending on its behaviour.
I think rewriting someone’s code can change your opinion of them pretty quickly.
Some mornings, motivation doesn't show up. The right track does. A few bars in, the work starts, and so does the healing.
Our app never sends big uploads through our own server. It asks the backend for a presigned URL, uploads straight to S3 in chunks with progress, then tells the backend it's done.
Our giving flow runs on Stripe for most currencies and Paystack for NGN, so people can give from anywhere without the app caring which processor sits underneath.
2
78
Fixing chat in our React Native app taught me that the best fix is a test written first, and the best UX is offline-first, where messages are already on screen before the network even answers.
2
95
Chat bugs don't crash your app, they quietly rot, so I tested every broken case before fixing it and am now making chat offline-first so messages show up before the network answers.
2
85









