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

One class to rule them all? no way. #4

Open
topisani opened this issue Mar 9, 2016 · 3 comments
Open

One class to rule them all? no way. #4

topisani opened this issue Mar 9, 2016 · 3 comments
Milestone

Comments

@topisani
Copy link

topisani commented Mar 9, 2016

We should split all buildings into their own files. 'nough said.

@whichonespink44
Copy link
Member

Maybe we should explore ENUM opportunities.

@topisani
Copy link
Author

topisani commented Mar 9, 2016

Java development - a book for pink, by topisani.
Chapter one:
In a healthy java environment, it is more effective to explicitly state when to NOT use enums, than when to use them.

@topisani topisani added this to the 0.0.1 milestone Mar 9, 2016
@whichonespink44
Copy link
Member

2wplor4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@topisani @whichonespink44 and others