Ask HN: Do you always go for low hanging fruits first?
1•alganet•8h ago
Comments
WantonQuantum•8h ago
That's a pretty broad question. What sort of context are you asking about?
For example, if I'm starting a new development project or task, I will solve the difficult problem first in order to reduce risk early.
On the other hand, "low hanging fruit" generally means "things of value that are easily obtained" and therefore would usually be what you'd do first unless there's some reason not to.
On a personal level, there may be opportunity for growth and development for avoiding the easy wins and doing something more challenging.
alganet•7h ago
I'm asking in a problem-solving context.
The "low hanging fruit" therefore, has no immediate value. It's just a smaller part of the problem that is more obvious and easy to reach. It could set up some movement in a virtual progress bar, but doesn't achieve any goal.
WantonQuantum•8h ago
For example, if I'm starting a new development project or task, I will solve the difficult problem first in order to reduce risk early.
On the other hand, "low hanging fruit" generally means "things of value that are easily obtained" and therefore would usually be what you'd do first unless there's some reason not to.
On a personal level, there may be opportunity for growth and development for avoiding the easy wins and doing something more challenging.
alganet•7h ago
The "low hanging fruit" therefore, has no immediate value. It's just a smaller part of the problem that is more obvious and easy to reach. It could set up some movement in a virtual progress bar, but doesn't achieve any goal.