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?
9 karma · joined July 27, 2019
(sounds like m3o is a microservice framework?)
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
It should instead be worked on making cheat resistant material
(unfortunately I don't know how to do it but I feel like the later is where the energy/brainstorming should be spent)
I often point people to this blog when asked why I don't use an ide
> 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)
how is 'AppDomainAffine' not a concept?