769 karma · joined February 28, 2017
Man, what a trend this has grown to be.
Would you recommend a remote job over a job "on-site"?
"OK, then why is everyone saying it’s hard ? [...]
Another reason is because it used to be hard a long time ago. People got traumatized by how hard it was to not screw up and never reevaluated the situation. Some people today genuinely discourage other people from running their mail server, citing the very real difficulties they faced over a decade ago, far before some of today’s tools even existed."
The escape key being "hard to hit" is exaggerated to say the least, and the F-keys I only use then I debug and need to step through my code. I do other things when developing than stepping through my code.
From the community side of things I highly urge those who are able to, to run a Tor relay. We're strong in numbers, and at least now the learning curve of configuring a relay is not an excuse to not get started. ;)
Thank you for reading. Feedback is greatly appreciated!
Picture that we have two components, a main component "Master" and a subcomponent "Slave". What you seem to be saying is that we should have an interface between the two so that Master uses an "ISlave" interface that the Slave maintains (the developers of the subcomponent) instead of using Slave directly. Dependency Inversion however dictates that you should invert this dependency so that Master dictates which functionality Slave should implement. That is, Master should have an ISlave interface (or an "IDelegation" or similar new name) that Slave (!) is required to fulfil. There is a small but very important difference between the two directions of the dependency arrow. One of the main points is that with Dependency Inversion it is the main component that is in charge of functionality instead of the main component having to work with the functionality exposed by the subcomponent.