{"comment":{"url":"https://api.github.com/repos/dotnet/corefx/comments/9155147","html_url":"https://github.com/dotnet/corefx/commit/3251c1cae5860785cfb716d3822d11149a88e0fa#commitcomment-9155147","id":9155147,"user":{"login":"sharwell","id":1408396,"avatar_url":"https://avatars.githubusercontent.com/u/1408396?v=3","gravatar_id":"","url":"https://api.github.com/users/sharwell","html_url":"https://github.com/sharwell","followers_url":"https://api.github.com/users/sharwell/followers","following_url":"https://api.github.com/users/sharwell/following{/other_user}","gists_url":"https://api.github.com/users/sharwell/gists{/gist_id}","starred_url":"https://api.github.com/users/sharwell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sharwell/subscriptions","organizations_url":"https://api.github.com/users/sharwell/orgs","repos_url":"https://api.github.com/users/sharwell/repos","events_url":"https://api.github.com/users/sharwell/events{/privacy}","received_events_url":"https://api.github.com/users/sharwell/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"3251c1cae5860785cfb716d3822d11149a88e0fa","created_at":"2015-01-05T15:46:29Z","updated_at":"2015-01-05T15:46:29Z","body":"The most important style convention for a developer to accept for themselves is the willingness to **observe** the existing conventions in surrounding code and **preserve** the conventions in code they add. In addition to differences that exist between projects, it is common to find differences even within a single project. By conforming to existing styles, you gain the following advantages:\r\n\r\n1. Differences in style start to \"fade away\", so your focus stays on the relevant semantics of the code you are working on.\r\n2. Your code will be more easily accepted by project maintainers, regardless of the project you are working on.\r\n3. You won't need to spend as much time deliberating styles/conventions for a project.\r\n\r\nAs a developer, you will frequently encounter situations that are problematic for the long-term viability of a project. But you don't want to be the developer that causes a situation to become problematic.\r\n\r\nAs a final note, discussions of style transcend individual projects. Be willing to provide feedback/rationale for your preferred style convention, but try to reserve them for cases where you are specifically asked to provide feedback or the style cannot be inferred from the project you are working on."}}