andrewingram

10 ms·

91.
by andrewingram 3y ago
It doesn’t solve it, but it lets you build a system that solves it for all future queries going forward. Think of it as a platform for taking endpoint specifications (ie GraphQL queries) and satisfying them efficiently. You have to build th
92.
by andrewingram 3y ago
The oil vs water thing resonates. Given that tenures are relatively short these days (1-2 years), it's pretty easy to just wait it out -- especially if the other person has issues with other people too. I do feel like too many of my ex
93.
by andrewingram 3y ago
I'm really good at other people's interpersonal problems, I'm a natural mediator. Less good at my own.
94.
by andrewingram 3y ago
With algorithmic questions, the life preservers often throw me off more than they help. I had one which was actually wrong, i.e the path I was going down was correct _and_ simpler. More commonly though, if I'm struggling, I'm norm
95.
by andrewingram 3y ago
I just want to figure out how to come up with a good answer for "Tell me about a time when you had a conflict with a colleague." (used as an example in the post, but not in any detail). It seems to be the question that anecdotally
96.
by andrewingram 3y ago
Linear waited nearly a year to announce a round, presumably because they did two in quick succession and didn't want to waste the PR opportunity of the second one.
97.
by andrewingram 3y ago
Kinda, by all accounts the original motivation was to solve the proliferation of endpoints. Everyone was already writing per-screen endpoints to solve the network requests problem (which, contrary to what many believe, wasn't magically
98.
by andrewingram 3y ago
By wrapping the code that loads data with code that checks whether the current (i.e. requesting) user is allowed to load that data. I don't really understand the problem, how is this any more difficult than any other API paradigm?
99.
by andrewingram 3y ago
Reminds me of the thing where apparently every guy adds two inches to their height on dating profiles, whereas I deducted an inch because of poor posture. Apparently I was born with no guile (probably an exaggeration), which means in a worl
100.
by andrewingram 3y ago
I think it's good to challenge received best practices like this - even if in this case the alternative seems to hinge on something that most teams struggle with even more -- writing sufficient good tests. I favour a less automated sol
101.
by andrewingram 3y ago
Horizon: Forbidden West is an amazing technical achievement, I just wish I had found it more enjoyable, instead it was "fine". Elden Ring coming out 2 weeks later kinda made me forget all about it - it gave me a feeling I haven&#x
102.
by andrewingram 3y ago
Yeah. A pervasive poor abstraction can be painful, but in my own experience most misguided abstractions tend to be somewhat superficial and easy to unwind. It does worry me to see so much rhetoric in the wider programming community encourag
103.
by andrewingram 3y ago
My take is that all this WET/DRY wisdom makes people think about abstractions in the wrong way -- it makes us debate them in term of when, rather than what and why. In my mind, the point of abstraction is to transform models such that
104.
by andrewingram 4y ago
The vast majority of React’s core team still works for Meta, and I think the sentiment that a small handful of “famous” hires amounts to acqui-hiring the team is frankly a little insulting to the rest of them.
105.
by andrewingram 4y ago
In both cases (this page, and the one you mention) I think you’re inferring the wrong context — which is reasonable because it’s a legitimate inference. I think the context is “for this use case”. Neither are saying never use Redux or useEf
106.
by andrewingram 4y ago
You're right, i'll redact/edit. Hm, this doc page is exceptionally confusing. Edit: So it's kind of interesting, this test (and the functionality behind it) exists specifically to make sure you can't rely on it havi
107.
by andrewingram 4y ago
https://react.dev/learn/separating-events-from-effects#decla... > Here, onConnected is called an Effect Event. It’s a part of your Effect logic, but it behaves a lot more like an event handler. The logic inside it i
108.
by andrewingram 4y ago
There aren't any function-scope variables used here, so an empty dependency array is correct.
109.
by andrewingram 4y ago
He looked at 128 random useEffect calls in the codebase, and determined that roughly 50% of them (59 calls out of 128) were unnecessary.
110.
by andrewingram 4y ago
[Edit: this is all wrong, see comment tree] It makes it so that the same instance of a function is used for all renders, but that it always points to the data closed over by the latest render; it eliminates a whole class of scenarios that n
111.
by andrewingram 4y ago
I've only been in situations where pay-cuts were offered a couple of times. In both cases equity was offered. In the more recent case, equity was offered with instant vesting, and there was a commitment to repay the deducted pay in ful
112.
by andrewingram 4y ago
A couple of neat tricks you can do with this: * Declarative streaming with slots: https://enamel.pages.dev/ * A countdown timer without client-side JS: https://dash.deno.com/playground/how-to-crash-a-br
113.
by andrewingram 4y ago
Temporal is an implementation of a paradigm I got interested in back in 2019. I wasn’t at one of those companies that had heard about Cadence, so when I was searching around to see if anyone had actually already built this idea I’d come up
114.
by andrewingram 4y ago
I've been using the beta of Temporal's Python SDK with Django, and aside from some minor teething issues, it's very nice.
115.
by andrewingram 4y ago
I had the same idea a few years ago. We had a chat-bot we used for onboarding, and I considered trying to reimplement it in Ink. Didn't get the chance in the end, but still interested in the idea.
116.
by andrewingram 4y ago
Can be, sure. But SQL, whilst very capable, isn’t the language I’d reach for in order to define my entire business logic layer. Sometimes these transforms are fairly involved and pull in things from multiple data sources and APIs, yes these
117.
by andrewingram 4y ago
Generally no, they’re not different. For example, the consumer Twitter apps; or when I worked there, Depop. The situation may change if you also add internal tools to the mix, since they’re often operating on a superset of data that the con
118.
by andrewingram 4y ago
Say you have a web app, an iOS app and an android app. And let’s say the model of the data that makes sense for the purposes being the UI for these apps is different from the model that’s used to persist data in the database. It means somew
119.
by andrewingram 4y ago
In a world where you have multiple clients, you want to minimise duplicate work of derived state. Unless your UI-level data model is 1-1 with your persistence layer (rare, in my experience), there’ll need to be a transformation somewhere, a
120.
by andrewingram 4y ago
Personally I wouldn’t advocate for these as I don’t believe it’s a good idea to automatically generate a GraphQL schema based on your database (I haven’t worked on anything in years where this would’ve been a good idea). But YMMV as always.

More ›