chrisandchips
Joined 9 years ago
Joined 9 years ago
E.G. searching “aluminum” still got both US and UK results, even though the later writes it “aluminium”.
Of course there are examples of situations where this heuristic doesn't apply, but that doesn't mean its a bad idea that we should totally disregard. This kind of thinking has plagued engineering fields for a long time; Don Norman talks about it in "The Design of Everyday Things". Engineering teams get mad when users don't use their products the "right way", when really they just won't admit to themselves that they've implemented bad design. Simpler, cleaner designs and use patterns tends to win as time goes on.
This is a really cool point, no one ever mentioned this to me when I learned about this stuff at university. I wonder though, is there data for this ? Are businesses willing to take the risk and how do they mitigate ?
I'm not sure how popular they are in the wild, but there are a lot of approximation algorithms as well for solving version of these problems that are almost-but-not-quite the same. I wonder if that's just what lots of real-world use cases actually need.
He is presenting the list as "too be finished by X date", which within itself sort of implies trying to do it quickly, or at least that he is taking time into account while reading.
But it's not unreasonable that he make it through this list and enjoy everything. Half an hour a day really isn't much.
Phenomenal and related mini-doc on the subject of reading time and frequency: https://www.youtube.com/watch?v=lIW5jBrrsS0
I should also add, page count is very much so dependant on font size.
it’s nothing more than a decorated version of http://bettermotherfuckingwebsite.com but it does the job and works on mobile without me needing to understand much about css.
I’ve been reading again, before I go to bed, and after months of picking back up the habbit I still only feel half as able to concentrate on novels as I was as a teenager.
I think the value this will bring isn't very high. I personally believe that early programming has less to do with reading the code as natural language and more to do with understanding what the individual constructs achieve. This is purely anecdotal, but I taught programming to a few students in French and the presence of English never came up as a blocker.
Fun story : for the hell of it, I once tried to code an entire project with some friends in French exclusively (that is, mainly variable/method/class names etc). As much as I love my mother tongue, its not always very concise. The whole thing became super bloated. We ended up reverting back to English.