Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Android Build a Simple Android App with Java Improving Our Code Simple Refactoring: Using a New Class

Kareem Jeiroudi
Kareem Jeiroudi
14,983 Points

Couldn't we change the method's signature in this specific case to static?

I was wondering why you didn't make both the method as well as field static in this case. For me it doesn't make sense not to do so, because each and every FactReader object will have the same string array, it's not like the array is going to change with some object. So I'd type:

private static String[] funFacts = {...}

and the method's signature would like something like:

public static String getFact() {...}

This would also allow us to use the method using class reference (FactsBook.getFact()), instead of initializing a FactBook object in the activity, if you know what I mean. However, I'm not completely sure how big of an improvement would that be in comparison to non-static field and method. If someone has has an answer to what the difference is, please share it with community.

Santiago Serrano
Santiago Serrano
2,754 Points

I was also thinking about this, hope someone answers