upvote
I don't remember where I first heard this idea, but using 2 orthogonal axes of simple-complex and easy-hard provide a good framework for evaluating concepts. On this plane I would describe income taxes as easy, but complex. Juggling is simple, but hard.
reply
An explanation can be simple, and holding the entire chain of simple ideas in your head to 'understand' some bigger idea can be difficult.

At some point, you have a body of knowledge, your 'understanding' that satisfies your curiosity (or you get exhausted and move on).

reply
As an example of this, you can have complex code made of entirely simple and easy to understand functions. But the complexity appears in the combination. That complexity can be far higher than were you to have more complex functions in the program. Which this is a common mistake people make that lead to tech debt. A lot of people try to simplify code by making it "understandable" without setting a floor to who needs to understand it and with how much time. If you don't, that floor gets lower each year.

If you can't think of an example of the first case, most machine learning models suffice. Take a simple feed forward ReLU model. It's trivial to understand ReLU. It's nearly trivial to understand the individual neuron. Yet I, as someone who wrote their PhD thesis on neural architectures, would call bullshit on anyone claiming they "really" understand what's going on in a deep network.

reply
For sure. Binary is another example: it's just 1's and 0's, a bunch of on and off states that only make sense when you consider the entire sequence.

And in physics, everything is reduced down to 'simple' forces of nature. A bunch of interactions and relationships that add up, and if you can keep up and perceive it all, you can sometimes stay ahead of all those interactions and imagine how it works through intelligence.

Eventually, you reach a state where you understand enough about the environment to translate ideas from one mind to another through language and your understanding of the world.

And so some will have deeper understandings, and in different areas, and all manner of conflict and resolution arises as people with different understandings try and understand one another.

There's no end in either direction you look, but zooming in always reveal some simple interactions at work.

reply

  > There's no end in either direction you look, but zooming in always reveal some simple interactions at work.
This is why I actually hate the phrase "from first principles". I can't tell you what the first principles are, but I can sure tell you that when someone says that they almost certainly are not starting from first principles and almost surely are (often unknowingly) making major assumptions. First principles are something you need to find, not start with.
reply
You're right, and it's subjective because of priority. First principles should be tied to whatever thinking requires the most concern in the moment.

If you're in charge of budget, you probably put budget before some other minor concern. If you're in charge of delivering a software feature, bug, patch, etc, you probably put something else first. It all depends on when something is due, or if something could jeopardize long-term prospects.

Everyone is on the hook for something. First principles thinking might be: think of your customer, and what they expect. Will whatever it is I'm doing affect them over the long-term? What about short-term?

If there's no clear answer, there's a lot of latitude to do whatever you think is best.

reply
Honestly, I think you're pointing at something important that a lot of people miss. I make the claim that Apple was only successful because of both Steves. Jobs gets all the credit and tech people idolize Woz. Both are critical to the success though, just in different directions.

I actually think this is why a lot of software is going to shit now (even before AI slop). There's supposed to be contention between marketers and engineers (and even contention between types of engineers). If the engineer has too much say you build a great product but make no money and the business flops. If the marketers have too much say you build absolute shit and make money but you also forefeet a lot of potential revenue (opportunity cost). I think currently we've given the marketers too much say. Every time I talk to engineers they ask me where the "value" of something is and there's a constant followup with "no, I understand this helps the user, but how does it make money?" That's not the primary job of the engineer. This also creates problems because if a marketer can't understand the "value" of something then it just doesn't get built. So it shifts the objectives while people don't recognize that there is this baked in bias.

To tie back, I think a lot of arguments come to an impasse because people are working with different priors but assuming the other party has the same priors. It isn't uncommon to see people on HN (or Reddit) arguing what are essentially duals of problems. We just think that because we are using the same language that we're actually communicating. Like you said, there's no clear answer. Most of the problems in the world have no global optima. So how do you solve them? You have to define your constraints. But I rarely see that actually happen, though when it does conversations are really efficient.

reply
As far as simple not being easy, its worth noting that Feynman only really hits his stride in the second half of his answer. That's how hard it is, a genius theorist and genius communicator still took a few sentences to start making it simple when given a backwards question.
reply