Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Java Java Data Structures Efficiency! Queueing

Do ToDo items have to be processed in the order they appear in that list?

If more than one person is working on a project simultaneously, which I assume is the usual scenario, in what order are ToDo items processed? If various classes comprising the solution are developed independently, how are the interfaces and methods of each class determined? That means if in a project person programmer #1 is developing ClassA while programmer #2 is developing ClassB, does each programmer decide the methods and members for his/her class independently?

What if programmer #1 is expecting ClassB to have a method getSongList() but programmer #2 doesn't know that and assigns the method (which provides a list of songs to the calling procedure) songsByArtists()?

When a ToDo item is being processed, are the exact member names, types and methods of the classes that will be coded to perform the tasks required by this item specified by the team as a whole or are those details left to the discretion of the programmer assigned to process that item? Or does each programmer provide documentation about the classes he/she develops to the other programmers and then they adjust their code accordingly to use the method names chosen by the programmer supplying the class?

I guess in essence I'd like to know if a class can be developed truly independently of the other classes being developed by the team.

Thanks!