Oddly enough, I just realized I do both

For clarity, this post was more creative writing exercise than technical treatise. Thanks for reading!

For clarity, this post was more creative writing exercise than technical treatise.

That's cool. This type of thing just sparks something in my brain. I learned cursive because it was beat into me. As soon as I could abandon it I did, and for good reason too. My cursive was terrible and dyslexic, and block text was much easier to write and to read.

The other stuff I wrote is secondary to your post, and just a hot take. Thanks for the stimulating article though!

sure?

I was being tongue-in-cheek. Didn't mean to sound like a smartass. Thanks for reading!

I did mention that our clients are enterprise-level.

But I did fail to address a more general decision-making process regarding choosing frontend architecture. If I did (and I probably will soon), I would talk a lot about the egregious initial load times on too many blogs that roll crazy dynamic tools for what should be a completely static site.

Yeah, I’m sorry. Looking back at it, that comment was written in general exasperation with the current state of the web, not really at you in particular.

Your exasperation is absolutely shared. Thanks for engaging

Thanks!

Right?! Yeah, the title should be “A few patterns we implemented lately”. I do have more thoughts specific to practical frontend architecture though, so I guess I’ll just hope you see the next post.

Using Tailwind alongside anything is pretty simple. It just generates stylesheets for you based on what you use. All you need to do is set up the build (so that it knows which style rules to include and which to purge) and then start using Tailwind classes in your markup.

As for “best practices”, I’d say there’s not many problems you’ll run into using something like Tailwind. Any configuration improvements you make probably won’t break anything, but you should still read the docs before you get started.

Ha! Yes. It’s pseudo code though. Please don’t copy and paste it.

Thanks for the positive vibes.

Great question. In fact, that question has more to do with “architecture” than most of my post.

The primary reason we went with Apollo is that it’s flexibility-minded and well-documented, making it easier for new engineers to work with. If everything was ideal, we’d use Relay. Relay’s patterns are better (IMO) but it can be confusing for new folks to use it idiomatically. So, it’s primarily a dev-experience consideration for us.

Specifically, are you referring to JWT with Apollo client on the server-side?

On the client-side, you can just use a link and get the cookie into an auth header that way. On the server-side, you need some way of getting that auth token from the cookie and passing it into the server-side runtime so that you can insert it into the auth header via a link in each server-side Apollo client instance.