Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
andrewingram
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
andrewingram
1y ago
Is there any interop between v3 and v4 schemas themselves? We have an enormous graph of hundreds (if not thousands) of Zod schemas, many inheriting or extending others. It's difficult to envisage us being able to do an incremental upgr
62.
▲
by
andrewingram
1y ago
A fair number of unions, yeah. Which also means some of the tricks for keeping the types small don’t work —- ie taking advantage of interface reuse.
63.
▲
by
andrewingram
1y ago
We use it heavily for backend code, and it is a bit of a hot path for our use cases. However the biggest issue is how big the types are by default. I had a 500 line schema file that compiled into a 800,000 line .d.ts file — occupying a huge
64.
▲
by
andrewingram
2y ago
Yeah, I think both these are true: 1. React is bigger and slower than it needs to be. There are likely better choices today. 2. Most websites will be bigger and slower than they need to be due to the endless September of new devs, and the r
65.
▲
by
andrewingram
2y ago
Came here to make the exact same comment, just being able to specify a border feels a little shortsighted.
66.
▲
by
andrewingram
2y ago
I did a "trial week" at Linear a few years ago, essentially the same thing but for an entire week. Nice to get paid, but even getting paid is stressful if you're used to working PAYE and not having to think about how to do ta
67.
▲
by
andrewingram
2y ago
In recent years my general principle has been to introduce an abstraction (in this case split up a function) if it lowers local concepts to ~4 (presumably based on similar principles to the original post). I’ve taken to saying something alo
68.
▲
by
andrewingram
2y ago
React does have a bunch of legacy baggage holding it back, definitely from a performance angle. But I think a major part of the issue is just the fact that React _is_ so popular, with that comes the inevitability that the majority of people
69.
▲
by
andrewingram
2y ago
I think there are two valid interpretations of the words “local-first”. 1) The outcome of all interactions can be seen locally first, but are sent to a server too. Optimistic updates on steroids, largely done to make software seem faster. L
70.
▲
by
andrewingram
2y ago
Even as a massive GraphQL fan, the GraphQL layer is what made me migrate all my projects away from Gatsby. It just doesn’t portray it at its best.
71.
▲
by
andrewingram
2y ago
It wouldn't surprise me if a lot of those 100k lines were from the interactive playgrounds that are specific to each blog post.
72.
▲
by
andrewingram
2y ago
Interestingly, http://www.donothingfor2minutes.com/ eventually morphed into Calm
73.
▲
by
andrewingram
2y ago
If I were using Remix, I'd probably trigger GraphQL queries from route loaders, one doesn't really obviate the other. Yes, there are challenges with using GraphQL well, but there's no inherent tension between it and the loade
74.
▲
by
andrewingram
2y ago
When you build a GraphQL server, you’re creating a system that outputs page-specific endpoints. They can be generated just-in-time (the default) or at build time (the general recommendation). The engineering work involved shifts from buildi
75.
▲
by
andrewingram
2y ago
That does loosely suggest that something of fizzbuzz-level triviality may be sufficient for first-round filtering.
76.
▲
by
andrewingram
2y ago
We're using JSONPath to annotate parts of JSON fields in PostgreSQL that need to be extracted/replaced for localization. Whilst I'd naturally prefer we didn't store display copy in these structures, it was a fun thing to
77.
▲
by
andrewingram
3y ago
I miss the Spotify 3rd-party apps, I discovered some great music through them.
78.
▲
by
andrewingram
3y ago
One could argue that React’s strict mode behaviour in dev is a guard against this —- as it prevented you from building things that will break with (the then) upcoming functionality.
79.
▲
by
andrewingram
3y ago
Thanks! The original inspiration was a DGR video in late 2021 when he showed the original chinese-language windows-based level viewer. That inspired me (as a Mac user) to seek out the API and level format documentation, then it was a whole
80.
▲
by
andrewingram
3y ago
A few years ago I built a level viewer based on this API: https://www.smm2-viewer.com/ Was quite a fun challenge, some interesting tech at play, and interesting algorithm work to render out the slope tiles.
81.
▲
by
andrewingram
3y ago
More people will get to age 80 if we tackle the causes of aging
82.
▲
by
andrewingram
3y ago
They're illnesses for which age is the biggest contributing factor of whether you'll get sick, and how sick you'll get. Nearly every disease affects you more severely the older you are.
83.
▲
by
andrewingram
3y ago
I think i've mentioned this here before, but a friend of mine (Andrew Steele) is an anti-aging biologist, and has written a book on the subject. He's an excellent communicator, and a while ago did a video examining Bryan Johnson&#
84.
▲
by
andrewingram
3y ago
I have a transplanted cornea too (along with an implanted contact lens in the same eye), took me from being unable to resolve detail at any distance to being pretty much 20/20
85.
▲
by
andrewingram
3y ago
I think I shipped my first production GraphQL server around this time 8 years ago, but by all accounts it was in use at Facebook a couple of years before it was opened up. So overall ~10 years old sounds right, though the released spec is a
86.
▲
by
andrewingram
3y ago
Last time I worked with Expo, the main historical reason for ejecting (custom native modules) was all but eliminated by the config plugin system. We actually ejected at one point, but rolled back that change once we realise the plugin syste
87.
▲
by
andrewingram
3y ago
I don’t think it’s enough to be likeable. That, and “personable” are common words used to describe me, but this particular interview round (eg behavioural questions) are still where I’m most likely to fail a process these days. Feedback is
88.
▲
by
andrewingram
3y ago
Both. I think knowingly misleading people (or allowing them to be misled by omitting key information) is wrong. There are exceptions, but I’m more strict on this than most appear be. As a result, I don’t have a lot of practice at it, and th
89.
▲
by
andrewingram
3y ago
Unfortunately, I’m not good at making things up or embellishing the truth. I’m far more inclined to downplay something than exaggerate. I’m literally someone who took an inch off my height on my dating app profiles because I have slightly b
90.
▲
by
andrewingram
3y ago
For the first production-scale GraphQL servers I built, I just had it dump ascii art representations of the downstream request waterfalls during dev. This was enough to visualise and fix any n+1 issues.
More ›