n_e

7 ms·

61.
by n_e 8mo ago
It depends what you're getting out of it. I've signed CLAs because it was more convenient for me to have my PR upstreamed rather than maintaining a fork.
62.
by n_e 8mo ago
I don't get it either. The LLM-generated issue from the above prompt is just the same information written more verbosely.
63.
by n_e 10mo ago
The issue is that the API itself is, I assume, badly designed. Equivalent delete queries in rest / graphql would be curl -X DELETE 'https://api.example.com/users/123' vs curl 'https:/&
64.
by n_e 1y ago
I've been surprised to see that several cycling products have gotten better over time. For example I have bought these bottles https://www.zefal.com/en/bottles/545-magnum.html three times over ten years: - th
65.
How to Load JSON, Avro, Parquet, or Anything Else in PostgreSQL(even.li)
3 points by n_e 3y ago|0 comments
66.
by n_e 3y ago
An analytics database is better (clickhouse, bigquery...). They can do aggregations much faster and can deal with sparse/many columns (the "paid" event has an "amount" attribute, the "page_view" event has
67.
by n_e 3y ago
> Cloud SQL Postgres Although it works and is solid, I wouldn’t say it’s fantastic. My impression is that Google makes limited investment in it to steer customers towards their own services such as Cloud Spanner. - Major versions are 6 m
68.
by n_e 3y ago
You can count to an arbitrary number (until the recursion limit) by using tuples of length N (and go back and forth to number literals by using the type of tuple['length']) e.g. : type zero = [] type Inc<N extends string
69.
by n_e 3y ago
> At places with basically no platform team, no advanced cloud setup etc, I as a dev could understand everything, and deploying mostly meant getting my jar file or whatever running on some ec2 instance. With an ec2 instance, how do you,
70.
by n_e 3y ago
select array_agg(e) from jsonb_array_elements_text('["a","b"]'::jsonb) e; ?
71.
by n_e 3y ago
The biggest advantage of SQL is that it's so common that if you deal with data a lot you tend to know it well enough. Sure, there are small differences between databases but joins/grouping/window functions tend to work simila
72.
by n_e 3y ago
In most tooling, you can write SELECT FROM table, then go back to the select list and have autocomplete work. The situation could certainly be better, but at least this works today.
73.
by n_e 3y ago
> GraphQL doesn't allow for recursive types. It does, this schema works: type Item { id: ID! children: [Item!]! } type Query { root: Item! } GraphQL queries describe the shape of the response, so with this
74.
by n_e 3y ago
I'm very happy with GraphQL. We use it mainly for APIs that are consumed by several clients (web app, mobile app, other services). The main benefit to us is that it's a huge time saver. There is almost no similar/duplicated c
75.
The problem with live validation and what to do instead(adamsilver.io)
1 points by n_e 3y ago|0 comments
76.
by n_e 4y ago
> That’s so weird, I wonder how that works. If I’m the first to make a map or a street or any geographic object in France, it can’t be featured on any other map, unless so license it? A GR isn't a geographic object, it is a sequenc
77.
by n_e 4y ago
Although the problem will be a lot less severe than with remote servers, this is still sub-optimal: - the data passed from one query to the next still needs to move from the database process to the service process and back - the queries wil
78.
by n_e 4y ago
I don't know ActiveRecord either, but it appears so https://guides.rubyonrails.org/active_record_querying.html#j...
79.
by n_e 4y ago
> If Kubernetes does indeed provide the best solution to provide scalability and availability, one can argue that this would result in a decreased demand for dev ops engineers, as they "would just have to use Kubernetes". I&#x2
80.
by n_e 4y ago
In the ecosystem I work in, it's normal to have automated tests, it's normal to have a main branch that builds, and it's normal to be able to develop a full feature locally. Plenty of other things that make coding and deploym
81.
Show HN: Coding Rules: Rules for writing robust, maintainable code(codingrules.dev)
1 points by n_e 5y ago|0 comments
82.
by n_e 5y ago
> I think it looks fine _.chain and .value() could be removed > works fine. - it isn’t possible to tree-shake the package and only include the lodash functions that are used - it isn’t possible to have non-lodash functions in the pipe
83.
by n_e 5y ago
There is no mess. The 99% case is a pretty string. The 1% case is a string with escaped delimiters.
84.
by n_e 5y ago
> Chalk maintainers basically discard the performance improvement as micro-benchmarking (i.e. "doesn't matter in the real world"). Chalk maintainers also say tree shaking doesn't matter in the real world. Chalk’s purp
85.
by n_e 5y ago
> The fact that GraphQL allows all these permutations in the queries is the root of the problem. It's not something which can be solved or optimized within GraphQL. Common ways to solve that are to whitelist the allowed queries or t
86.
React Suspense in One Image(even.li)
1 points by n_e 5y ago|0 comments
87.
GraphQL is a slightly better REST(even.li)
4 points by n_e 5y ago|0 comments
88.
by n_e 5y ago
> Since Go makes errors a return value you have to actively discard the result (by replacing it with a underscore, e.g. `res, _ := getResults()`) or take the time to handle the error. LoadData(&data) Does this function return nothing
89.
NoDeployFriday: Helpful or Harmful?(theengineeringmanager.com)
1 points by n_e 5y ago|0 comments
90.
by n_e 6y ago
I’m talking about the GraphQL or OAS schema. With a REST API, the “resource” type will always have an optional “comments” field, whatever the value of arg is. With a GraphQL API you’ll have the right type depending on your query.

More ›