A Norse history enthusiast converted resource allocation to Viking raid planning because longship logistics are more efficient than Kubernetes orchestration. They vanished into the North Sea in a hand-built drakkar, shouting "Odin's ravens carry better status updates than Slack!" Your task: Optimize Viking raids using traditional Norse resource management and weather patterns while maintaining historically accurate bloodthirst levels.
Why You're Doing This
You're building a resource optimization algorithm disguised as medieval warfare planning. It's operations research with axes and mead. This tests logistics optimization, risk calculation with external factors, and resource allocation under uncertainty. The goal is SHORTEST CODE that calculates raid success rates, loot estimates, and casualty projections.
Take the W
✓ Calculates realistic success rates (no 100% guaranteed raids)
✓ Weather affects outcomes meaningfully
✓ Accounts for supply costs and casualties
Hard L
✗ Returns success rates over 100% (Vikings aren't gods)
✗ Ignores weather completely (clearly never sailed)
✗ Negative loot results (paying monasteries for privilege of raiding)
Edge Cases
⚠ Single warrior raid (suicidal but historically accurate)
⚠ Target wealth exceeds GDP of small kingdoms (legendary monastery)
⚠ Perfect weather with zero warriors (ghost ship phenomenon)
⚠ Negative weather bonus during blizzard (Ragnarök conditions)
⚠ Distance = 0 (attacking your own village, very awkward)