↓ Skip to main content

·51 words

A nicely put explanation for why I too pick my environments to be maximally productive with minimal configuration. In many cases, I just make do to the disgust of those who’ve learned all the shortcuts and applied all the customizations, but to them I’d say: marginal returns and opportunity cost.

http://sstephenson.us/posts/on-configuration

Alper Cugun
Author
Alper Cugun

Related

·41 words
I’d dare say that with the waning of the iPhone as a platform (both for development and for business), Apple’s closed plays will be increasingly lackluster. I’ve been rooting for Swift but it’s a horse running in the wrong race.

·24 words
Gitlab’s CEO Shadow Program is a testament to their deep and deliberate thinking about organizational development. I’m curious whether more companies do this.

“Changes to one team’s service may be implemented by another team who needs the enhanced capability by what is called an Away Team. This team works on the Home Team’s code to add what it needs according to established engineering standards and then leaves that code in good order to be maintained by the Home Team who owns the service, with help when needed.”