Percentage Rounds Overengineered

private static string GetPercentageRounds(double percentage) { if (percentage == 0) return "⚪⚪⚪⚪⚪⚪⚪⚪⚪⚪"; if (percentage > 0.0 && percentage <= 0.1) return "🔵⚪⚪⚪⚪⚪⚪⚪⚪⚪"; if (percentage > 0.1 && percentage <= 0.2) return "🔵🔵⚪⚪⚪⚪⚪⚪⚪⚪"; if (percentage > 0.2 && percentage <= 0.3) return "🔵🔵🔵⚪⚪⚪⚪⚪⚪⚪"; if (percentage > 0.3 && percentage <= 0.4) return "🔵🔵🔵🔵⚪⚪⚪⚪⚪⚪"; if (percentage > 0.4 && percentage <= 0.5) return "🔵🔵🔵🔵🔵⚪⚪⚪⚪⚪"; if (percentage > 0.5 && percentage <= 0.6) return "🔵🔵🔵🔵🔵🔵⚪⚪⚪⚪"; if (percentage > 0.6 && percentage <= 0.7) return "🔵🔵🔵🔵🔵🔵🔵⚪⚪⚪"; if (percentage > 0.7 && percentage <= 0.8) return "🔵🔵🔵🔵🔵🔵🔵🔵⚪⚪"; if (percentage > 0.8 && percentage <= 0.9) return "🔵🔵🔵🔵🔵🔵🔵🔵🔵⚪"; return "🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵"; }

A dark-themed code screenshot shows a C# method that converts a percentage into ten blue or white circle emojis using a long chain of conditional statements. The joke is that a simple percentage-to-progress-indicator conversion has been needlessly overengineered with repetitive if statements. It can be sent as a reaction to excessive complexity, verbose code, or overengineering. EN: A dark-themed code screenshot shows a C# method that converts a percentage into ten blue or white circle emojis using a long chain of conditional statements. The joke is that a simple percentage-to-progress-indicator conversion has been needlessly overengineered with repetitive if statements. It can be sent as a reaction to excessive complexity, verbose code, or overengineering.

• @gentoomemes / 1986 2023-01-17