I like solving problems when programming is the source of trouble, or with programming as the troubleshooting tool. Favorite tools: SQL and .NET. A long history of IT projects in finance and banking.
No discussion? Strange. So I leave one thought. It's practically useful e.g. in estimation. When we try to estimate "the most real value", we fail almost everytime. But there is one simple trick closely related to the described principle: instead of estimating one value, we can estimate the worst, "the real" and the best value. It's sometimes boring, sometimes it slows us down, but it's our shield anyway. Thank you, Thomas!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
No discussion? Strange. So I leave one thought. It's practically useful e.g. in estimation. When we try to estimate "the most real value", we fail almost everytime. But there is one simple trick closely related to the described principle: instead of estimating one value, we can estimate the worst, "the real" and the best value. It's sometimes boring, sometimes it slows us down, but it's our shield anyway. Thank you, Thomas!