Twitter | Search | |
Ryan Yurkanin
Engineer 🧠 average tech blogger and lover of Dark Souls 🌞 he/him
723
Tweets
408
Following
463
Followers
Tweets
Ryan Yurkanin Jul 15
Replying to @cliftonC76
Yeah so adding a way to inspect the end result of calling the function rather than the function itself is probably the easiest way to go
Reply Retweet Like
Ryan Yurkanin Jul 15
Replying to @cliftonC76
If onSaveForm makes an API call you could use something that like fetch-mock that will allow you to inspect that it is being hit after some interaction with the component. You could also pull it out of the component body and pass in everything it needs as arguments.
Reply Retweet Like
Ryan Yurkanin Jun 1
What you could've done: Admitted that it was a terribly timed tone deaf joke, apologized, and learned from the experience. What you've done: Bragged about how much money and impressions it's brought you. Yikes.
Reply Retweet Like
Ryan Yurkanin May 10
Replying to @JoshWComeau
It looks awesome, great work. I love your style
Reply Retweet Like
Ryan Yurkanin Mar 14
Replying to @brian_d_vaughn
Do you take protein by chance? If you're taking it with water you could switch to whole milk or something so you hit your calories for the day If not it might be worth it to take it while you're shut in doors
Reply Retweet Like
Ryan Yurkanin retweeted
RVA JavaScript Conf Feb 18
Everybody likes to talk about hooks! discusses the architectural predecessors of React hooks, and leads us through an example of how hooks can make complex components so much simpler!
Reply Retweet Like
Ryan Yurkanin Feb 13
Replying to @kentcdodds
We have this at Guru and it helps a lot. Mostly playgrounds for editor content, flipping on feature flags, and getting metadata
Reply Retweet Like
Ryan Yurkanin Feb 1
Replying to @hswolff
I always thought it was because the first part of it is a variable declaration. I always say it in my head like: "for x is 0, and less then 10, do this and increment by one" I think thats just because it's all I've ever known not because it makes sense
Reply Retweet Like
Ryan Yurkanin Dec 23
Replying to @boop
the audacity!
Reply Retweet Like
Ryan Yurkanin Dec 23
Being the 35th employee at a company doesn't mean you'll be the 35th most heard voice and that's okay.
Reply Retweet Like
Ryan Yurkanin Dec 23
Learning to care about what matters in software engineering is so hard yet so key. The more experienced I get the more often I find myself saying "I don't care". But when I do care, I *care*
Reply Retweet Like
Ryan Yurkanin Dec 14
Replying to @pamasaur
Enjoy!! Love that part of France 😁
Reply Retweet Like
Ryan Yurkanin Dec 6
Replying to @js_tut
NaN not equaling itself is a mood
Reply Retweet Like
Ryan Yurkanin Dec 4
Replying to @pixelyunicorn
I'm so conflicted
Reply Retweet Like
Ryan Yurkanin Dec 4
Replying to @pixelyunicorn
I want to like this but it's at 69 likes and I feel like it would be wrong to break that
Reply Retweet Like
Ryan Yurkanin Dec 2
Replying to @js_tut
In old code one "effect" could be in state, cDM, cWU, and cDU. If a component has more than one effect it's absolute madness!
Reply Retweet Like
Ryan Yurkanin Dec 2
Replying to @js_tut
Hooks separate state and side effects from components and let you compose them into their own units Each component gets one state and one lifecycle before. Why not organize them by "effect" instead of by component that are attached to? That's what hooks do
Reply Retweet Like
Ryan Yurkanin Dec 1
Replying to @jsjoeio @disneyplus
in love with it right now, can't wait to see what happens
Reply Retweet Like
Ryan Yurkanin Nov 25
When I first started programming on a team, I had to teach myself to speak up Now I'm teaching myself to talk less and listen to others more
Reply Retweet Like
Ryan Yurkanin Nov 20
Replying to @kvlly
At least they labelled their inputs!
Reply Retweet Like