magiconair
At Last I Am Free
Configuration is also an external contract since you don't want to break installations because you want to rename a variable. Therefore, you have to distinguish between argument parsing and the actual runtime configuration and it makes a lot of sense to have that in a single package since you can then test it properly.
Configuration is a complex issue for non-trivial projects. Managing this in one place allows to have one source of truth.
Disclaimer: I'm the author.
If you're doing something that doesn't interest you then it doesn't matter how good the other benefits are since you constantly have to use energy to motivate yourself. Then you won't produce something you're proud of which helps neither you or the company.
Disclaimer: I'm the author.
Disclosure: I'm the author.
Disclosure: I'm the author
We are seeing effects of less effective communication of teams sitting just a few desks apart.
Remote work has great benefits for the remote worker - and having been one I know them as well. The downside is that when you're building something complex the communication overhead is too big.
Another thing is that remote workers in vastly different timezones provide a time window for architectural discussions which can be too short. So they are never there when you need them and can only work alone.
I prefer to give my team members flexibility to run their personal errands and family issues but to have them on-site to have the shortest group communication paths possible.
Found it: (http://talks.golang.org/2012/splash.article)
"As a simple, self-contained example, consider the representation of program structure. Some observers objected to Go's C-like block structure with braces, preferring the use of spaces for indentation, in the style of Python or Haskell. However, we have had extensive experience tracking down build and test failures caused by cross-language builds where a Python snippet embedded in another language, for instance through a SWIG invocation, is subtly and invisibly broken by a change in the indentation of the surrounding code. Our position is therefore that, although spaces for indentation is nice for small programs, it doesn't scale well, and the bigger and more heterogeneous the code base, the more trouble it can cause. It is better to forgo convenience for safety and dependability, so Go has brace-bounded blocks. "