715 karma · joined December 15, 2013
People expect for a type to contain some logic, but it doesn't have to. e.g. a configuration is a type that contains other types that contains yet other types. But I have never seen it done like that in languages like Java.
1. You can measure productivity in a precise way only in some mindless repetitive jobs e.g. are Twitter employees more productive now that they are in the office. How do you measure that (if you measure it in profits, app quality etc. I'd say that they are much less productive)
2. Each person is different. I may be 10% more productive at home than in the office, and my coworker may be 20% less productive. Why do I have to be in the office because of some stupid statistic?
3. Fine, let's say people who work at home have lower productivity. But working from home enables you to hire people from all over the world as well as people who cannot go to the office for various other reasons. I'm not a big tech CEO, but somehow it seems to me that the best candidate in the world, working at 90% of their capacity will still perform better than the best candidate who happens to live in your city and is willing to travel.
4. Working from home is also linked to a better well-being, which means less turnover, better working environment etc.
5. Most importantly: the fucking planet is dying, because of carbon emissions and you want to just dismiss the obvious and already implemented solution for reducing those by letting people not travel to work, just because of some 10% profit increase.
1. Change the "div" "span" etc. to be just "createElement('div'..."
2. At the "render" function, do "reactDOM.render" instead of "replaceChildren"
As far as "prop drilling" goes, I never understood what is the problem that some people have with it.
If you just put your state in one object its just one more param that you have to pass to components. Do we really need a big-ass framework just because of one extra param.
Also, by passing state explicitly, you get a clear visibility over which component needs what. And it also allows you to restrict which component uses which parts of the state.
https://abuseofnotation.github.io/category-theory-illustrate...
https://abuseofnotation.github.io/category-theory-illustrate...
Otherwise, with solving and creating problems, I was thinking about tech that is overdesigned and crammed with features to the point where it's useless. And also about a particular xkcd comic...
Timeless is probably a bit strong as a word, but actually why not - books, tables and chairs, bottles and plates, have all have been there since the dawn of civilization.
But pretty great to see other people thinking about the same ideas. Do share if you have more feedback.
Also, car's simplicity is only an illusion. Anything is simple when other people fix and maintain it for you.
If we look at the example, the lack of contradiction is one condition, but there is another one - totality.
The sentence "the whole sphere of possible existences, the mortal occupies one part, and the immortal the other." contains the assumption that all objects in the universe are either mortal or immortal, which is questionable e.g. what about the things that are not alive in the first place? e.g. is a chair mortal or immortal?
This issue is not present in the dichotomy between reality and negation e.g. the dichotomy between "mortal" and "not mortal" - here it is easy to sort all possible objects to mortal, e.g. a chair is clearly not mortal. In my view this is the difference between reality and negation.
Happy to read your thoughts on the subject.
For the font, other people complained that it is too non-standard, maybe I have to do a separate version for text.
Didn't know about the drugs.
Otherwise I haven't disabled the reader view, I don't even know how this is done.