How is anyone making money from courses if dabeaz isn't? He's got the word of mouth going on, celebrity status in the Python world, world-class courses, it doesn't make sense to me. I'm not asking rhetorically, am truly curious about what's going on.
When on Speaker/hands-free mode, it just closes screen. They assume you wouldn't press lock button while against your ear, because it closes the screen automatically. The problem is that there's some bugs that keep the screen open sometimes, or you may use it in a quiet room as if it were on hands-free.
Markets and evolution are both knowledge processes. I think you would enjoy Donald Campbell's essay on evolutionary epistemology from 'The Philosophy of Karl Popper'.
Parent's comment is observing a prerequisite to markets, humans are the only animal with global markets and biological selection happened to produce the kind of creature that can stabilise around markets.
It's also selection that produced the current form of markets themselves. The world could have been otherwise; our current markets are contingent selection products, not analytically necessary institutions, and not guaranteed to be the uniquely best mechanisms for producing abstractions and tools.
Were 8 billion people all working toward more detail? Isn't civilization also the process by which detail is pruned, compressed and made into abstractions small enough for one mind to use?
I usually view it the opposite way from the article's perspective. There's surprisingly little detail we rely on, yet things work out somehow.
There's the Popper observation that any model of reality has zero chance to be true, since our models are finite, yet we're trying to describe a fractal reality. It's amazing how few levels of decomposition we need to go through to get something useful, like the stairs in the article (3 decomposition steps, as compared to thousands). If I were to never interact with reality and rely on pure reason alone, I would expect nothing humans ever do to work.
Abstraction and exploration are unreasonably effective.
Was discussing the content, not the author. Yes, I am challenging vague discourse about echo chambers, since the mechanism behind an echo chamber is selectively listening to some opinions, while dismissing other sources of authority or correction. To see why this is a problem, consider that parent comment is compatible with both:
"Flat Earth is a cancerous echo chamber"
"As I grew older and became better at arguing, I learned to explain why universities teaching that the Earth is spherical are cancerous ideological echo chambers."
> isolating themselves & having their [...] views spread far and wide
> most cancerous developments & the less contentious it becomes
Your comment complains that people cannot articulate their reasons, while making a sweeping, emotionally loaded claim whose reasons are themselves barely articulated.
I'm developing a similar project, I also added scripts to it so it works like an hermetic/replayable system too. Do you use yours for anything cool? Maybe a truth maintenance system of sorts? Do the queries get unwieldy at some point?
I'd like to imagine that the creator heard the 'Einstein zebra puzzle' (the puzzle about different nationalities having different pets and smoking different brands of cigarettes) and just made the pets have different nationalities and smoking the cigarettes directly.
Actual stealing is an even more impressive skill. Usually involves intensively trained sleight of hand, elaborate ruses, a very good understanding of theory of mind regarding the victim's attention, and planned deescalation paths in case you're caught.
This is a pre-AI phenomena. I observe it quite a lot with stuff I did in high school but usually with complex problems. What's generally happening is that you were working with pen and paper through a hard problem. With adult brain, you'd expect just to know the answers, but in reality you're not much smarter than you were at 14, so you need to do the thing properly.
Also if you help little kids with homework, you'll see that some problems are quite difficult as well and require you to actually think, even if it's problems for 10 year olds.
You can go down or right at any point. To go in bottom-right corner, you need n down steps and n right steps. In how many ways can you arrange n things on type A and n things of type B? In C(2n, n). The problem is about modeling, once you model it correctly, you get the definition of combinations.
I'm not sure I'm following you. What does 'duplicate Google Docs' mean? We already have OSS rich text editor (ProseMirror) and CRDT implementations (yjs, automerge). Are you talking about replicating every single enterprise Docs has? Integration with a large suite of other services you control? Replicating the business model too?
'duplicate Google Docs' spans everything from providing the actual service to replicating the world and becoming Google.
Yes! First, you need to get the DOM-level behaviour right (dragging, resizing, cursor focus). That could mean you may use or build primitives like with interact.js, CodeMirror/Monaco (realistically just use, not build), Fancytree. I really like Muuri for layouts. Usually there's also subtle interaction physics going on when building such libs in unexpected places (such as resizing and drag N drop speed curves), which you should tweak to your taste.
For framework, React wants to own and mediate the DOM via virtual tree, which is a major bottleneck when you need direct control over focus/selection/keyboard routing or hardware accelerated canvases. Instead, look at Svelte or Solid.js, as they integrate nicely with imperative DOM-oriented JS libraries and don't require heavy wrappers or indirect references for the 'unfriendlier' DOM nodes like canvases, scroll containers and so on.
If you're building an OS-like UI, you should also care about state and be sure you have direct control over where your data lives. For example, I usually build with Solid.js and a mix of custom object and lifetime code plus Solid stores for reactive surface state.
I usually end up managing object lifetimes because I end up needing to handle messy edge cases around reference vs value semantics and state merging (e.g. keep cursor position sane after a file sync or track focus across multiple windows, especially after refresh)
For text editing, if you use Monaco, it has so many internal lifecycle hooks you want to be aware of and interact with directly, that you'll see that most of implementation will end up outside classic frontend lib fast and I'd rather build the thing instead of bridges and wrappers to talk with a high-level framework.
All in all, you probably want to own a lot of state and behaviour yourself, and add a cooperating framework on top instead of an all-encompassing one.