@Timoldland I almost prefer the refinement of the BAIC. Makes the Defender look like a bulky Overfinch or Mandory version. But that’s glancing and to someone where neither are really my taste.
@Dave_DotNet Agree. Too many unit tests assert implementation, especially using Moq and VerifyAll. E2E tests, and I now love snapshot tests, really check system behaviours.
@DamianEdwards@jfversluis Single file MCP servers. Using options and secrets seemed to work just fine, but anything to ease patterns for them would be handy.
@Microsoft365Dev@sebastienlevert Is embedded knowledge go-live in the declarative agents? Microsoft Learn says “This feature is not yet available” in the schema.
@mjovanovictech I always find getting a flag needing an async call a bit inconvenient and the call itself quite verbose. Wish the pattern were simpler.
@phoronix Wow. Ben Adams is legendary for his dotnet performance work some time ago. He seemed to gravitate away from his efforts - everyone deserves a change of scene I guess - then returns with this monumental piece of work. Pretty inspiring.
@Monz_ah Hard disagree. Argos is conveniently in every Sainsbury’s near us. Availability and pricing of branded items, like Samsung TVs is great. Find it far easier to find a brand in stock I trust than on Amazon.
STEP 2: THE NEXT TWO NUMBERS = ENGINE LEVEL
Old school BMW rule (the one enthusiasts respect):
20 / 25 → calm, normal power
30 / 35 → fast
40 / 45 → very fast
50 / 60 → madness
Example:
BMW 330i → 3 Series, fast level
BMW 540i → 5 Series, very fast
@vyrotek It’s the mandatory base library where I contract. But sadly trying to use a state machine library for long lived workflows is painful and verbose, whilst not really solving reliability and scaling. It’s no doubt being misused. I wish I could go back to Azure Durable Functions.