Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated README.md #46

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,24 +6,24 @@
![](https://img.shields.io/badge/Communication Channel-Slack-blue.svg)
![](https://img.shields.io/badge/Twitter-juiiocesar-blue.svg)

Game is a native workspace that contains a basic architecture for game development on iOS, OSX and tvOS. That allows the developer to share code between these platforms
Game is a native workspace that contains a basic architecture for game development on iOS, OSX and tvOS. It allows the developer to share code between the mentioned platforms.

##Coding Style
We are following the [Github's swift style guide](https://github.com/github/swift-style-guide)
The [Github's swift style guide](https://github.com/github/swift-style-guide) is being followed.

##Clean code
Please remember this points every time you write code

* Bad code does too much – Clean code is focused
* The language you wrote your code with should look like it was made for the problem
* It should not be redundant
* Reading your code should be pleasant
* Can be easily extended by any other developer
* It should have minimal dependencies
* Smaller is better
* It should be expressive
* Use descriptive variable names
* Never Cut-and-paste code
Please remember the mentioned points every time you code.

* Bad code does too much – Clean code is focused.
* The language you wrote your code with, should look like it was made for the problem.
* It should not be redundant.
* Reading your code should be a pleasant task.
* Can be easily extended by any other developer.
* It should have minimal dependencies.
* Smaller is better.
* It should be expressive.
* Use descriptive variable names.
* Never Cut-and-paste code.
* Omit needless code!

##Contributing
Expand Down