4 ms·
The only reason this is a problem is if you try to achieve the stated conditions independently. If you envision the complete solution (a stack of blocks) you bu
by phkahler 9y ago
The only reason this is a problem is if you try to achieve the stated conditions independently. If you envision the complete solution (a stack of blocks) you build it immediately by placing C then B then A.
This seems similar to how people tend to focus on short term goals at the expense of longer term ones. Similarly, it's hacking vs architecture in software. You can fail by doing to much of either one.
- crowbahr 9y agoYes, obviously you could give the program the goal of "Stack blocks in order A:B:C" but that's not the point of the conundrum here. Imagine they are 30 different goals all of which need to be aligned in slightly odd ways to achieve the ultimate task. You're having to prioritize pieces in non-linear fashion to slowly build up the base as you're solving individual steps that seem entirely tangential to the overarching goal. You might have to take 4 or 5 steps back sometimes to achieve 1 step forward. That's the problem here. It's not this simple 3 block solution: that's only used to get you to wrap your head around the simplest possible complexity.
- hood_syntax 9y agoI feel like the goals are framed incorrectly relative to the context. What's most important is not that B is above C, and A is above B, but that C is on the bottom. If framed that way, you can work backwards from the base case.
- CarolineW 9y agoThat feels trivially like saying: "If you can identify the crucial part of the challenge then it's easy." The problem then becomes one of identifying the crucial part of the challenge. If framed that way, your comment doesn't really help.
- totalZero 9y agoIt's more like saying you need to use inference to identify constrained parts of the solution.