CRUD 2

For the conditions -d and -i i use a for(int i = 1; i < args.lenght-1; i++) and the task didn't pass. I changed in i < args.lenght; only like that... and pass, but i don't understand why? If args.lenght = 10 and args[0] = "-d", from 1 to 9 I have the rest of args array. If i loop until i = 10 I am not out of array!?

Why would the code for this and previous task have separate CreateMale and CreateFemale methods, instead of just having a single CreatePerson method that passes the Sex as a parameter? Seems like it would be less code that way.

i wrote my solution, test it once, twice, 15 times, everything worked great. "check solution" and.. no is no good, i pressed "get correct solution", check each method, one by one, all of my methods had the same idea as the "correct" ones, i actually liked mine more (were shorter, cleaner and easier to read), still got error like: "Be sure the args.lenght doesn't change when '-d' is passed " (i checked, it was fine) "Be sure the information are displayed as required when '-i' is passed are as required" (i checked, on my solution were identical with the one in the "correct" one) and 2 more errors that i can't remember and can't see them anymore because "the task was solved already". final was to solve this: copy paste to the "correct" one and move on. because that's what codding is about: providing the code some boss want line by line and not your own solution!

task1711 (CRUD 2) CAVEATS: Validation of requirement 7 is broken. To get past the validator you need to have something like this:

switch (args[0]) {

You will get failed if you instead have something like this:

switch (args.length > 0 ? args[0] : "") {

Requirement 8 is fully in the unmentionable category but it indirectly gives a valuable hint with regard to consistency level that the code has to achieve. I.e. if there is a synchronisation block in every case label of a switch that switches on commands then this implies that the whole argument list of a command should be processed atomically. To get past the validator you need stick a synchronized block in every case branch of the switch statement, regardless of how you actually handle synchronisation in your code. Don't forget the default branch, if you have any. Empty blocks are perfectly fine.

be careful if you have a default branch on your switch statement as it expects EVERYTHING to have a synchronization block, so maybe easier to just not have a default. Took me many attempts to finally understand why failing the last validation, even though my default was only throwing an illegal argument exception and had nothing to do with the other cases checking the arguments..

PRO TIP!!! This task uses the String[] args bit of the main(String[] args) If you want to test this and run code based on th String[] args in IntelliJ do this: 1. Click on the play button next to public static void main.... 2. Select the last option 'Create solution main'... 3. In the Create Run Configuration window look to Program Arguments 4. Set your arguements here for example: -u 0 Washington m "04 15 1990" 1 Smith f "03 19 1987" or -c 0 Washington m "04 15 1990" 1 Smith f "03 19 1987" This took me a LONG time to figure out, hope it helps someone else.

is there a way how to push arguments via codegym compiler?

Is it just me or the instruction for this task is so vague & unclear that you, too, have no idea what they actually expect us to do? ;)