Jimmy Van Veen
banner
jimmyvanveen.com
Jimmy Van Veen
@jimmyvanveen.com
Senior Web Developer at @iracing.com. Posts are my own about whatever I feel like. I love #NASCAR

https://www.iracing.com/iracing-staff-member-profile-senior-web-developer-jimmy-vanveen/
Whoaaaa that’s way better than the local one I have access to in Boston
June 21, 2025 at 5:17 PM
I mean I don't want either
May 23, 2025 at 10:56 PM
That’s great and all, but you still need to care about yourself and your place in the world
May 8, 2025 at 2:25 AM
Is it really debatable that every change to the performance of the cars is geared towards entertainment and not performance?

If we can agree on that then you have your answer.

We want maximum performance, and May the best team(s) win
May 5, 2025 at 2:25 PM
Well he better kick ass
April 25, 2025 at 12:36 AM
Selfishly streaming ergonomics (if they can be improved which I don’t predict) would be very welcome.

Selflessly docs on the whole seems the most benevolent
April 25, 2025 at 12:04 AM
I guess if they stay at js.org then that makes it hard. Trying to think of maybe other ways to handle it.

But I guess so long as the sites link to each other as they do now it's still ok
js.org
April 24, 2025 at 1:56 AM
can you at least coalesce them behind a single domain, using subdomains to host each one?
April 24, 2025 at 1:54 AM
it might not be practical, but my FAVORITE thing @acemarke.dev did with Redux was add the style guide/best practices.

Not sure if a great resource like this exists, is feasible, or anything like that - but this was a godsend to help our team migrate to "modern" redux redux.js.org/style-guide/
Style Guide | Redux
Redux Style Guide: recommended patterns and best practices for using Redux
redux.js.org
April 24, 2025 at 12:24 AM
the well-worn post on X saying "this is the real React 18 release" is a good example of the fear "you're leaving me behind" has (I know we already litigated that).

I'm not trying to say you're actively doing a bad job, just mentioning a fundamental tone that I think would help
April 24, 2025 at 12:21 AM
Here's an example of what you guys do to say what _not_ to do. The fact it fits on one page I think points to what I mean.

react.dev/reference/re...

I think utilizing this more, like "if it's not listed here, we _actively_ support it" but not only is this not very visible, I don't see it discussed
Legacy React APIs – React
The library for web and native user interfaces
react.dev
April 24, 2025 at 12:19 AM
Perhaps being louder about aspects that are TRULY being deprecated would serve you well as a counter balance.

“If we were killing this feature we’d do so the same way we killed (fill in the blank)”

Like createClass still works but is actively discouraged.

Be loud with what you actually discourage
April 23, 2025 at 10:30 PM
Best advice I can give is do not ever say anything new is “ideal” or even hint at “this is what we want everyone to do”

I think we can all handle “here’s a new tool for your tool belt” but any amount of “this should be your first tool of choice always” will make us lose our minds
April 23, 2025 at 10:28 PM
No you shut your mouth Wes lol
April 23, 2025 at 10:23 PM
‘Merica
April 22, 2025 at 4:58 AM
Going to monorepo first then React 19 across the board in the coming weeks for all apps
April 18, 2025 at 2:54 PM
Nice!

By the way I did land that React 18 PR I spoke about back at #EpicWebConf lol

bsky.app/profile/jimm...
🎉🎉 PR Merged 🎉🎉
April 18, 2025 at 2:53 PM
define it and how merely existing there makes it so.

I’ll wait
April 18, 2025 at 1:37 AM
But it’s sad because this place is so hostile. I don’t fit in well.
April 17, 2025 at 10:41 PM
My impact has been better here than over there.

Not that I expect to be in a position to capitalize on it, my impact is so tiny.

It’s just what little impact I have seems stronger here.
April 17, 2025 at 10:40 PM
🎉🎉 PR Merged 🎉🎉
April 16, 2025 at 7:11 PM
React 19 next but before that we’ll migrate to a monorepo.

This should be less intense (I hope)
April 16, 2025 at 4:01 PM