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.
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.
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.
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.
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.
Being in tech means youโre always learning, even when youโre not trying to ๐
You could be scrolling your phone and suddenly think, Wait, what actually happens when I run npm install?
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.