A description of my image.

Daily Digest, 19 Mar 2025

Published on

 |  Time to Read: 6 mins

#Announcements

#Articles

  • Use Build Insights to identify bottlenecks. Windows Performance Analyzer’s timeline view is incredibly useful for narrowing down slowdowns.
  • Be mindful of force inlining. Excessive inlining can significantly increase compile times, especially when applied deep in the call stack, where it can be hidden and lead to a combinatoric explosion of calls. Also, it can limit the compiler’s ability to make optimization choices, leading to worse runtime performance.
  • Leverage Unity/Jumbo builds. Combining multiple source files into a single unit helped Activision shave one minute off their build time. Checkout our blogpost on Support for Unity(Jumbo) files in Visual Studio, to learn how you can take advantage of this for your builds!
  • Continuously measure and refine. Optimization is an ongoing process, not a one-time fix.

#.NET

#Infrastructure

#Architecture

#AI

There is so much chatter and content coming out for Agentic AI and MCP, it’s a bit overwhelming, but Google’s examples have a practical example which makes it a bit easier to understand:

#Other Interesting Reads