ah okay that makes sense, m3o is basically a microservices framework then? Pull the pieces you need (basic authentication, service communication etc) and all you need to add is your business logic?
Designing tests for open book seems to be a good way to
a) make cheating in effective, (no need to sneak in a formula sheet when everyone has it)
b) More like the real world, I always have google at my fingertips, it is just how efficiently I can use google and my existing knowledge to solve a problem
Perhaps you can explain this part from the post you linked which is perplexing me:
> AppDomainAffine, therefore, would be a more appropriate name. Unusual perhaps, but that's because of the common drift toward the mechanics of things and away from concepts (because the mechanics are usually much easier to get for techies)
What issues have you had on the first Gen ryzen cpus? I have been running 6 of them on my home lab (true a small sample size) and I have had no issues with them