> And not when you want to have lots running in parallel, accessing and potentially making "changes" to the same files.
Reading a file is a fast operation these days. Re-reading a file shortly after a read is less than a memory copy.
Making the structure more complicated so that you can avoid reading a file during unit tests is a poor investment of resources - that complexity will haunt down the team forever.
Reading a file is a fast operation these days. Re-reading a file shortly after a read is less than a memory copy.
Making the structure more complicated so that you can avoid reading a file during unit tests is a poor investment of resources - that complexity will haunt down the team forever.