Viewing profile — jaredgorski
jaredgorski
HN member- Joined
- Sat, Mar 23, 2019, 3:39 AM UTC
- HN karma
- 137
- Public activity
- 36 items
- HN profile
- View on Hacker News ↗
About jaredgorski
Recent public activity
- comment
-
comment
Comment #31111612
I was being tongue-in-cheek. Didn't mean to sound like a smartass. Thanks for reading!
-
comment
Comment #31110714
Oddly enough, I just realized I do both
-
comment
Comment #31110701
For clarity, this post was more creative writing exercise than technical treatise. Thanks for reading!
-
comment
Comment #31110666
For clarity, this post was more creative writing exercise than technical treatise.
- story
-
comment
Comment #31077289
Maybe you should write a web blog post nobody will read about it
- story
- story
- story
-
comment
Comment #28621853
Your exasperation is absolutely shared. Thanks for engaging
-
comment
Comment #28611005
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 prob…
-
comment
Comment #28606735
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 …
-
comment
Comment #28606721
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 styl…
-
comment
Comment #28606677
Ha! Yes. It’s pseudo code though. Please don’t copy and paste it.
-
comment
Comment #28606663
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 f…
-
comment
Comment #28606564
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 se…
-
comment
Comment #28606244
I see what you mean. By way of clarification, I see route validation and pageload validation as potentially separate. For example, a given route parameter may govern a whole scope …
-
comment
Comment #28606067
Totally. With Next, your page component can export a getServerSideProps function which is used by the Next server to fetch any props necessary for the page component server-side on…
-
comment
Comment #28605914
I’d love to hear more about your experience with that “with-apollo” pattern. I decried it without using it first, but I see the problem as a coupling/cohesion imbalance. What has i…
-
comment
Comment #28605858
I’m with you :) It’s certainly nothing new, but the “buzz factor” impresses people who don’t know what it’s for and they implement it everywhere thinking it’s an improvement. The t…
-
comment
Comment #28605816
“Hey look, the browser loads each new page one at a time instead of loading them all in the initial load.”
-
comment
Comment #28605794
Good! We need to get back to the basics and stop shoehorning React into every application. I regret that my post is yet another React promotion. Not intended: architecture depends …
-
comment
Comment #28605717
Great feedback. I’ve been wanting to write more about most everything you mentioned, but ended up writing about a few interesting patterns we implemented recently. I probably shoul…
-
comment
Comment #28605675
> So, why are you using an SSR framework then? Great question; I should’ve mentioned this more concretely in the post. I would’ve nuked Next completely, but we like the filesystem-…