concurrently

Even desktop CPUs have had the ability to run several threads concurrently on a single core for decades.

P2P was easy by desktop app standards, but concurrently with its development, the web started taking over.

Working on the same file concurrently does not guarantee conflicts - working on the same code does.

Or is your work just organized such that no two people are ever working on the same file concurrently?

For example, it's possible for a man to produce many children by impregnating lots of women concurrently.

What you won't find is a single core desktop CPU that has the ability to run several threads concurrently well.

Method calls are asynchronous, can be paused while they wait for events and many objects can be simulated run concurrently.

Except when you have to do things concurrently and have to use locks.

Yes, this was a 100K+ element collection being concurrently used by 1000+ threads.

Yet, that's despite tens of millions to billions of transistors running concurrently.

I personally think that learning both Haskell and Clojure concurrently has a lot of merit.

Also, if your dao tests are the only thing that hit I/O you can safely do all the other non-integration tests concurrently.

The definition of "concurrently" typically means "without synchronization in between".