hansonkd

18 ms·

181.
by hansonkd 2y ago
What? GraphQL is purpose built to solve that in 1 Query. Not doing it in 1 query is on you not the protocol. In practice with REST the frontend engineer didn't want to wait and tried to use the existing REST endpoints, did N+1 API HTTP
182.
by hansonkd 2y ago
Not nearly as often with Graphql and happens less and less as your backend and data models stabilizes. Most of our frontend features now don't have backend changes and we were able to increase the ratio of frontend to backend devs.
183.
by hansonkd 2y ago
A REST endpoint can be analogous to a specific method in code. just as much as a GraphQL field. What people are excited about is that the frontend can request all the data it needs at once and the backend can efficiently serve it. Something
184.
by hansonkd 2y ago
Typically the endpoints clients are multiple frontend developers. If the frontend is blocked for every page they need waiting on the backend to expose data that massively increases the costs of features and reduces the time for delivery.
185.
by hansonkd 2y ago
I guess depending on the context of a simple app one level could be viewed as far. Any more levels and you have now reinvented GraphQL
186.
by hansonkd 2y ago
> if you have to involve a backend team to add restrictions to the graphql endpoints and try to make good educated guesses where those might be, then the idea of frontend not needing backend engineers No because if you dont do that you h
187.
by hansonkd 2y ago
Sorry what are the tradeoffs? I'm not sure where this narrative comes from that GraphQL immediately means that the frontend time will have no idea what they are doing and will induce load on the system. 95% of my nested graphql fields
188.
by hansonkd 2y ago
This is Wrong. GraphQL only exposes what you ask it to. There are plenty of pagination plugins for GraphQL frameworks just as there are plugins to REST framework. GraphQL can be restrictive as REST if you want it to be. The point is GraphQL
189.
by hansonkd 2y ago
Its gross because it is a waste. An engineer had to spend time to make that specific API for that page instead of the frontend consumer using what was already defined and get all the resources with one call and 0 backend engineer needed for
190.
by hansonkd 2y ago
> the back end team can select to serve REST APIs which only permit selecting, filtering, grouping and pagination that they know they can support within defined latency bounds for a given traffic level. Why do you think that they can&#x2
191.
by hansonkd 2y ago
REST APIS suck for nested resources. GraphQL is a huge breakthrough in managing them. Ever seen an engineer do a loop and make n+1 REST calls for resources? It happens more often then you think because they don't want to have to create
192.
by hansonkd 2y ago
I never understood peoples positions that GraphQL all of the sudden the frontend can make any Query it wants and control is out of the hands of the backend. That seems orthogonal to my experiences with GraphQL. GraphQL is a protocol and you
193.
by hansonkd 2y ago
Isn't that selection bias? Maybe a lot more people have used from an early age and you don't notice them because you are only noticing the ones that look different.
194.
by hansonkd 2y ago
I was able to implement this in the ORM layer of Django through a function that would inspect the query and split it if it had an OR under certain conditions.
195.
by hansonkd 2y ago
OR Queries are performance killers because they often force a full table scan. Another alternative to the Or is actually a UNION. A UNION allows you to use two separate indexes and can speed up queries.
196.
by hansonkd 2y ago
TBH part of the BEAM runtime is actually pretty slow. is the problem. * Want something flexible and easy and don't care about performance? Use Python * Care about performance? Use Rust, etc. Just because it is distributed
197.
by hansonkd 3y ago
Is raw code output so large that your editor can't "keep up" really something to optimize for? For me personally I write as little code as possible. you don't get bonus points for number of lines you write.
198.
by hansonkd 3y ago
Websites have spent the last 20 years removing user customizable functionality (think RSS feeds and making API private). While the tech may be possible, I don't see this being a reality without a major reversal in app development philo
199.
by hansonkd 3y ago
A good GenerativeUI product depends on a datasource for the AI to have some working history to make decisions about what kind of interface to show a user. An A/B test needs thousands of samples in some cases to make a determination abo
200.
by hansonkd 3y ago
I disagree with the authors assertion that a simple watermark would solve the issue. I don't see how you can ever enforce something like a "Clean Air act" against AI. AI is a spectrum and thus it will be a gray area. It would
201.
by hansonkd 3y ago
Today in the real world AI can replace very little of designers, programmers, etc. Lots of potential and extrapolation, sure. but hasn't happened. What has actually been produced by AI has been panned as not quite ripe yet. Same with r
202.
by hansonkd 3y ago
Well there is always your AI girlfriend and AI friend group with the AI generated podcast breaking down the episode. (jk, sort of) > Most of the reason people watch TV or movies is for the shared experience that you can discuss with othe
203.
by hansonkd 3y ago
Isn't the Luddite movement an example? The factories that replaced the artisans were only made possible by the work of the artisans forging the way.
204.
by hansonkd 3y ago
Custom AI commercials would be very interesting. Instead of seeing strangers enjoying the benefits of the product, it shows you. A car commercial would show you driving, etc. Commercials and TV episodes could have a basic "story arc&qu
205.
by hansonkd 3y ago
Countdown to when studios licensing this for "unlimited" episodes of your favorite series. There was Seinfeld "Nothing, Forever" AI parody, but once the models improve enough and are cheap enough to deploy, studios will
206.
by hansonkd 3y ago
Sorry, I didn't mean built from scratch and scaled it all the way to unicorn. Rather worked on a unicorn scale app in some capacity. Even if you join a late stage startup and didn't build the foundation, the experience you get fro
207.
by hansonkd 3y ago
Yes, that is how I found the engineers I did find. I wasn't impressed by the applications I got, although who I hired was fun and talented. If I remember they were either engineers who's primary projects were actually erlang, high
208.
by hansonkd 3y ago
The reply's asking if you need 100 devs, might not realize this article was about building SaaS apps. Having worked at multiple unicorn+ SaaS products, the product feature demands are significant. Yes if you have one sole feature that
209.
by hansonkd 3y ago
I love Elixir, but I have to disagree with the principal aspect of this post. As an engineering leader what I look for when picking tooling for SaaS which essentially boils down to two things: 1) How expensive and difficult will it be t
210.
by hansonkd 3y ago
Traveling definitely made me have some empathy towards people playing music in public places. In south america my friends there would be like "wtf" if they got to a beach or park and no one was listening to music. For a lot of peo

More ›