Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -248,7 +248,7 @@ A common guideline in programming is the **90/10 Rule** (or 80/20 Rule), which s

### 5. **Examples of Premature Optimization Pitfalls**

- **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck.
- **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck. <--- not yielding?
Copy link

Copilot AI Oct 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The inline comment '<--- not yielding?' is unclear and appears to be a draft note rather than proper documentation. Consider either removing it or expanding it into a clearer explanation about when loop unrolling doesn't yield performance benefits.

Suggested change
- **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck. <--- not yielding?
- **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck. This often does not yield significant performance improvements unless the loop is a proven bottleneck and the compiler cannot optimize it automatically.

Copilot uses AI. Check for mistakes.
- **Complex Caching Mechanisms**: Adding caching layers or memoization in parts of the code where there’s little measurable impact on runtime.
- **Avoiding Abstraction**: Writing overly specific code (e.g., using inline code instead of functions) to reduce “function call overhead” when the real bottleneck lies elsewhere.

Expand Down
Loading