Taiwan is a different story. There are quite detailed war simulations built for defending the country. I guess you might mean that russia is one of the “3 big world” powers and their move is the special operations to capture kiev. I stop here

Yes, I meant China, Russia and the US with the "3 big world" powers and yes, I was referring to the war in Ukraine. I am aware that the situation in Taiwan, Ukraine and Venezuela cannot be compared one-to-one. My categorization was not intended to suggest that these 'moves' are the same, nor to make any evaluation regarding good or bad. From the respective perspectives of the 3 world powers, they have been motivated by different interests. The important point is that each of the three will use the moves of the others to justify their own, whether this is correct or not.

- how to prove that humans can argue endlessly like an llm?

- ragebait them by saying AIs don’t think

- …

I do. I’ve researched the optimal distance for a smallish tv screen (which fits between the studio monitor stand). I move the tv closer when watching a film, it stands on hacked together wooden box like thing which has some yoga tools and film magazines in it - it has wheels. Crazy stuff. There is a flipchart like drawing of my daughter covering the tv normally which we flip when watching films.

I also hear that middle management is being cut from all companies. Some kind of management is necessary though, no? Otherwise people will get misaligned an all that. I'm not sure what is the point of the article. I guess a good manager doesn't need a bullet list to be able to function so why this person is writing a new one?

The article is giving me PTSD.

Total nitpick - you say list is commonly understood to be linearly iterated. I’d expect a list to refer to an ordered sequence - default implementation of access and mutation varies wildly between languages. E.g. java code usually defaults to ArrayList, lisps to cons cells, C++ doubly linked list, etc.

Sql has “tuples” for the rows of a result-set which are neither tuples nor lists in the “general sense” and are of a “record” type - names with values.

So what is a list? Depends on the context.

You are saying if promotion makes a person happy it justifies to spend a lot of resources on getting it even if it is harmful for the world (based on unstated ethical framework). GP says it is invalid resource usage - waste of human capital. I think he is hating on the game not the playa (based on unstated ethical framework)

I suspect that much more people can do it than unable to do it (aphantasia)

I have a suspicion that aphantasia - in some cases - is something that can be trained out of. The mind is a powerful thing.

Might be possible but then you lose aphantasia :)

I didn’t know people see things in the real world, like an imaginary cat until I had a dream where I could imagine something purposefully. I woke up immediately, thrown out from the dream image.

I told my wife proudly that I could see something in my dream I wanted to. She told me she can imagine ANYTHING ANYWHERE ANYTIME (painter)

My question is: can you see the cat on the table? If not, sorry pal.

What is the approach? Do you target a subset of sql which you compile onto or you have some runtime dynamic dispatch thing and fight for code reuse with the magic haskell tools?

Question is: do you need that flexibility if you have the backend for frontend? Can you design such a flexible api which makes it possible to iterate faster? If not, you just pay, in the best case, a constant overhead, or worst case, exponential overhead for each request! If you need to spend time optimizing because you have monitoring for slow queries or downtime caused by never terminating queries than most likely you’ve already eaten implementation speed advantage - if it exists at all in the first place.

I always thought it was about developer velocity, in this particular case front-end. With a traditional REST API the front-end team needed to coordinate with the back-end team on specific UX features to determine what needed to be done, which was further exasperated when API's needed to be specialized for iPhone vs. Android vs. Web UI.

GraphQL was supposed to help front-end and back-end meet in the middle by letting front-end write specific queries to satisfy specific UX while back-end could still constrain and optimize performance. Front-end could do their work without having to coordinate with back-end, and back-end could focus on more important things than adding fields to some JSON output.

I think it's important to keep this context in mind to appreciate what problem GraphQL is solving.

I think I understand this, possibly nice for huge client x feature matrix. I don’t have XP in the setup where there is a big separate backend team. In my head there is an alternative implementation: have a separate routing layer (coauthored by backend and frontend). Backend responsibility ends with the service layer. There has to be some domain contract implemented somewhere, question is it is simpler to cut down from a tree or build something on top of components.

This is my read of the history as well.

This is also the motivation that would lead me to advocate for adopting GraphQL for a product. Moreso than a technical decision, it is an organizational decision regarding resource trade-offs, and where the highest iteration or code churn is expected to be located.