eatthoselemons
eatthoselemons on Hacker News
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?
Does that mean that you could run m3o on k8?
(sounds like m3o is a microservice framework?)
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
I feel like this hits the real problem, figure out a better way to prevent cheating and a better cheat will be made.
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)
How is this different from K8's? It just looks like k8 with a little extra boilerplate for microservices (built in key-value store etc)
That is funny we heard the same thing from a high up at HP
Do you think that gitlab will ever add inline diff comments? I don't know if it would even be feasible to add to gitlab
ah okay that makes sense
I was thinking it was opposite of that which made no sense
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)
how is 'AppDomainAffine' not a concept?
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
Why do you like power9? What advantages does it have over x86?