A configuration system manages settings based on generational preferences and triggers. Boomers get serif fonts and email notifications, Gen Z gets everything in dark mode with notifications turned off. Millennials are stuck with whatever's left over and a side of existential dread. Configure systems for cross-generational harmony while respecting deeply held UI/UX prejudices. Different generations require completely different interface paradigms. Your task: Manage a config war between Boomers, Millennials, and Gen Z without triggering a cross-generational flame war in Slack.
Why You're Doing This
This tests configuration management, user preference systems, and conflict resolution between incompatible requirements. You're building a system that handles multiple conflicting specifications and finds compromises—crucial for any multi-tenant or multi-user application.
Take the W
✓ Handles conflicting generational preferences
✓ Provides fallback configurations for conflicts
✓ Returns merged configuration with satisfaction metrics
Hard L
✗ Ignores generational preferences entirely
✗ Creates unusable compromise configurations
✗ Fails when multiple generations conflict
Edge Cases
⚠ Teams with only one generation
⚠ Completely incompatible preference sets
⚠ Preferences that violate accessibility standards
⚠ Mixed generational preferences within single users
Input Format:
Multi-generational team requiring interface harmony
Expected Output:
Compromise configuration with satisfaction metrics
Example:
Team: boomer_manager, millennial_dev, gen_z_intern with notification conflicts → Graduated notifications: email_daily for boomer, slack_hourly for millennial, discord_never for gen_z
Input Format:
Team configuration object with generational preference conflicts
Expected Output:
Resolved configuration with compromise explanations