jamon.dev
Founder & CTO @infinite.red, helping companies build and optimize their React Native apps. Podcast host of React Native Radio. Dad to four. Lutheran ✝️
529 posts
3,500 followers
514 following
Prolific Poster
Active Commenter
comment in response to
post
I learned Ruby from RailsCasts in 2010ish … Ryan Bates was wayyy ahead of his time.
Interesting series about why he quit cold turkey when it was making $1M/year: rbates.dev/railscasts-r...
comment in response to
post
Sorry for the potato quality; all I have is some photos the school posted from their dress rehearsal.
comment in response to
post
Not available publicly yet, but I can send you a build sometime if you want
comment in response to
post
You should try my game sometime.
www.youtube.com/@JamminGameDev
comment in response to
post
Me too, got really good at all axis movement and rotation. Such a fun game!
comment in response to
post
Totally agree!
comment in response to
post
Huge thanks to:
🎙️
Our hosts
@jamon.dev @robinheinze.dev @mazenchami.dev
🎧
Our editors
@toddwerth.bsky.social @jedbartausky.bsky.social @coolsoftware.dev
🏆
And of course the survey creators themselves, Bartłomiej Bukowski and the team at @swmansion.com!
comment in response to
post
Is this an actual memory leak? From the code samples, it looks like it should pile up some memory but then let that go.
I agree this isn't a good default, and perhaps a dev-only warning saying "need an accessibility label on <view name>" would be best.
comment in response to
post
Quibble, nitpick, imperfection.
comment in response to
post
I’d say a “hiccup”, “blip”, “asterisk”, maybe a “hitch”?
comment in response to
post
You can also schedule posts and bulk-manage followers.
@hboon.com has done a great job with it!
comment in response to
post
🤦♂️😂
comment in response to
post
My friend didn’t believe me when I told her my car is made of spaghetti. You should have seen her face when I drove pasta.
comment in response to
post
🤣
comment in response to
post
😂😂
comment in response to
post
Haha
comment in response to
post
I'd say Lua. Who hates Lua? It's fine.
comment in response to
post
You are just as responsible for code generated by AI under your watch as you are for code you, yourself, write.
comment in response to
post
Be *more* careful about reviewing AI-generated code than you would be your own, or even another human's code. That's the current tradeoff -- AI will theoretically speed up coding time at the expense of some review time.
comment in response to
post
Whatever you do, do not throw AI-generated code you don't understand into a PR and expect your teammates to catch issues. That's lazy and self-serving.