TS perf post

[sachinraja]

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
next-prisma-starter	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 15, 2023 at 3:12AM (UTC)
og-image	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 15, 2023 at 3:12AM (UTC)

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
www	⬜️ Ignored (Inspect)			Jan 15, 2023 at 3:12AM (UTC)

[KATT]

I think @anthonyshew will look at this this weekend 🍿

[anthonyshew]

Sorry, I'm only a week late.

Okay, @sachinraja, I basically rewrote everything like a total jerk. I left you some notes, though, so ctrl+f for TODO and you'll find some things I need more from you on.

Take a look at this new draft and see what creative direction you'd like to take. It does look to me like the first section that I've now dubbed "Automating library performance" can get cut entirely because it's inaccurate. The post is still really interesting starting at the "optimization strategies" header.

Additionally, it sounds like y'all want to come up with a different example for the first bit. My advice is to remember to keep it simple. We can take something that isn't really an actual gigantic perf difference and frame it as "This example isn't actually a ginormous speed difference in and of itself - BUT it does demonstrate the tradeoffs between tighter types and performance." If you can come up with an example that is still accessible, go for it, but I think it's wise to keep that introductory example generally understandable to set up our readers for the incoming thicc dirtiness of The Sachin Show.

[KATT]

hmu when/how I can help to get this out! (@ me on discord as I might miss here :D)

[anthonyshew]

This will be such good content, y'all. 🏆