• Post Reply Bookmark Topic Watch Topic
  • New Topic

certainly a FAQ!  RSS feed

Kevin Jaffe
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
[This is surely a FAQ, but the site's FAQ list doesn't load up properly for some reason (I just see source).]
What's the best way to prepare for the Developer exam?
(I am definitely jumping the gun here, because I'm still studying
to take the Programmer exam, but even now I want to keep my eyes
open for anything that will be important in the Developer exam.)
If this question has been answered a billion times, please
accept my apologies and let me know where I can find those
Rick Fortier
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Alot of people have asked the same question.
The major skills that the assignment will require are:
1. Designing classes
2. RMI or Sockets
3. Swing
4. Threads and thread safety
5. javadoc
6. installation instructions
My two recommendations: Read through a fair number of threads in this forum and see what problems people are having. This will help you know in advance what things you might want to read up on. Secondly, download the assignment. There is no time limit on how long you can take to finish it. So there is no advantage in waiting.
The overriding principle of the assignment is that you recognize each design decision, investigate the possible solutions, determine the pros and cons of each, make a decision, and then document why you chose it.
As in life, and in this assignment there are some conflicting requirements. For instance, you might run up against a problem in which to truly solve you must provide a really deep solution, and alot of code. But one of the requirements is that a junior programmer must be able to maintain your code. And it is also a requirement that a simple solution is preferred.
So part of the assignment is for you to decide which one of these is more important. you should document that you know what the possible solutions are and then weigh them against the other requirements and make a decision.
You might have to make certain assumptions such as "A hacker will not build his own client application and send a command to lock my entire database, or randomly call my lock and unlock function calls." or, "My clients will only access the database using my program.". If you do not make some assumptions then your program will be so bloated, that the tester will have a hard time grading it. Keep it simple.
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!