581 karma · joined September 26, 2017
{
"user": [
{ "id": 456, "name": "Sita K", "user_id": 123 },
{ "id": 123, "name": "John Doe", "user_id": 123 }
]
}
PS: Co-author here
"Logic programming is considered superior to HTML/CSS even though it isn't. Just like one gender thinks that they are superior to others even though they aren't."
You end up in the "width vs depth" debate if you go along these lines. It is debatable whether it is better to know 60% of all worlds or >95% of one world. (Assumption: It is extremely rare finding people who know >95% of all worlds).
However, I agree with your point that full-stack is the way to go if you are limited on resources (small orgs).
1. In this article, the author says that he does not know streams. Now, when he learns it well, he can write about "How he learned about streams", and a beginner would empathize more with this article rather than some expert ranting about it in their blog. 2. It is inspiring for the readers. It sends a message: "If you master one skill and master it well, you can still add a lot of value to the world. Knowing everything in the field is not really important". 3. Many people write not just for others, but also for themselves. Making your insecurities public is a good way to acknowledge and face them.
Were you following Dan’s tutorial on Redux? Because that is a beautifully made tutorial as well. (https://egghead.io/redux)
If you have tried to build a substantially big app with React alone, you will find yourself lost in passing down the props and callbacks and hoisting variables and what not. You definitely need a state management library where you can CRUD from all your React components. Thats where Redux/Mobx comes into picture, unless you want to write a new one.
I agree that Redux needs a lot of boilerplate though.
You can go through this book that references several research papers.
On the contrary, they kill your knees. Sure one can feel nice about them in their youth, but it is pretty hard to use squat toilets in and after your late 60s.
Moving to a normal chair toilet from a squat toilet (https://en.wikipedia.org/wiki/Squat_toilet) was a hell for me. Chair toilets just don't feel right and comfortable to poop from if one has used a squat toilet all their life. Squatty potty hits a nice middle ground because:
1. It is better than the chair toilet in terms of comfort of bowel movement.
2. It is better than the squat toilet in terms of the extreme stress on the knees
Personally, discipline and honesty towards the code have been the most helpful soft-skill challenges in my programming career.
https://blog.hasura.io/hasura-vs-prisma-9ffc7271eda8
PS: I work at Hasura
[Edit] Also, the GraphQL spec being defined, and the way it is defined, reduces unnecessary documentation, unnecessary decision-making, and unnecessary communication between teams.
https://docs.hasura.io/1.0/graphql/manual/auth/index.html
PS: I work at Hasura
The problem boils down to controlling population and also handling population. If people want to keep buying new houses, there is more demand for deforestation. The agricultural demand for deforestation increases with the amount of food wastage we observe these days. Such incremental improvements in lifestyle could help us save forests.
The very idea that you have to think about logistics before naming your baby is ridiculous.
I figured this out today. And I submitted this Ask HN to find out more such things.
After all the research, I am still highly inclined towards Golang. Since you said "Perl or Go", you seem to have used Golang. How does Perl compare with it?
Otherwise python is the go-to because of the libs.
Thanks for pointing out.
It is a great course for non management majors to get a sense about how operations work. In fact, it is meant for non-management students because the course is originally taught at an engineering institute.
The instructor is a great figure in Operations Research. He is exceptionally knowledgeable and more importantly, clear.
Can you elaborate what do you mean by broken?