Mastering Reflection

Reflection allows your code to See itself. You can inspect types, find methods, and even execute code on objects you've never seen before. It is how tools like Entity Framework and JSON.NET work.

1. Custom Attributes

Attributes are "Metadata" that you attach to your code. By using Reflection, you can find all classes with a specific attribute (e.g., `[AutoRegister]`) and automatically add them to your DI container at startup. Architect Tip: This eliminates the need for giant, manual configuration files.

2. Performance Warning

Reflection is slow. It requires the CLR to search through internal tables. To fix this, use **Caching**. Reflect on the type ONCE, find the method you need, and store a **Delegate** to that method in a static dictionary. Subsequent calls will be nearly as fast as direct code.

4. Interview Mastery

Q: "What is the difference between 'Early Bound' and 'Late Bound' code?"

Architect Answer: "**Early Bound** is normal code. The compiler knows exactly what method you are calling at compile time. **Late Bound** is when you use Reflection or `dynamic`. You don't know what you are calling until the app is actually running. Early Bound is faster and safer, while Late Bound provides maximum flexibility for building highly extensible plugin systems."