There are companies where the use of the ternary operator in code is explicitly forbidden.
I read it in an article written by a computer science teacher, who used to work as a developer for several software companies.
Ternary is hard to understand, it makes difficult to review the code. And it's a very important aspect.
These were exceedingly hard to do. I would suggest that before anyone even tries them that you read all of the various comments and questions and answers for each task.
I think a major part of why these are so hard is that they are not explained well. I find it all but impossible to figure out what it is they are looking for. The Conditions are so unclear, even to the point of being obtuse.
This has got exceedingly more difficult in a very short space of lessons. Enjoying it but have nearly thrown my mouse across the room on a couple occasions lol.
For example.. the if(ternary operator) has made my brain feel like sludge. So many null/not nulls (if not null/null)..Nullll = maybe false?.. or is it true?... urrghh.
It's basically a nested if statement used for short-hand notation. Although it is not a fun time for code readers because it's so complex for being that compact. Comments are needed for sure. I explained it more thoroughly below \/
Actually, this code is just a very-short hand way of making sure the objects are the same even IF they are null. The name of the Human object can be null or have a value. This line of code checks if the name if NOT null. If it is not null, the if statement reads the OPPOSITE (!) of whether or not the name of human1 equals human2's name. If the names are not the same (equals is FALSE) then the if statement is ACTIVATED and "return false;' is executed. In the other scenario, when name IS null, it checks if the human2's name variable is NOT null. If the second name is NOT null then the names do not match because one is null and the other is not.
Help for : Stranger things
1. Look at the equals() and the hashCode() methods.
2. Try to understand what they do.
3. If you dont understand (like me) than look at the same methods in the previous 4 Tasks. Basically it should be almost the same code.
4. (Optional) If you found the errors, try to understand the code again.
Tip for the CodeGym task:
The requirements are VERY HAZY.
(1) In the SAVE, they want you to firstly check if there's anything in the users LIST.
Only save if : if (!users.isEmpty()) { all your save code }
(2) Before saving it, save the first line as the size of the users LIST
outputStream.write(String.valueOf(users.size()).getBytes());
Also read this, to know how many times to load it, in the LOAD method
(3)Then, for each field, save to lines. Line 1 = whether the field is null or not, Line 2 is the field value itself.
(4) Remember to flush() when exiting your SAVE loop (for some stupid reason. Don't understand why the write in ANY language would need a flush afterwards. It's not supposed to be a toilet.
When you READ/LOAD, do the same:
Each statement that reads a value, should first read the line that says if the value is null or not (that you saved). Then after that, read the line after, which has the value, and set your user object's value by calling the corresponding method in User class.
Remember to close the reader.
This was not a very clear or nice task, to say the very least. I really enjoyed the course up to this level. This level can be improved a lot, but let's move on!
• writer.flush(): This function forces all the data stored internally in the writer buffer to be "released" to the target source (String, console output, File). I once was printing to the console a text from writer and the result was an empty string. Very strange. Then I called the flush() method and voila, finally had all my data printed. (copied answer from previous lessone).Hope this helps.
hi Manish, thanks, but it changes nothing to my statement: it's stupid that any coding language would need a flush() method to print if the primary print() just refuses to print ?
The 2002 task took me so much time. Ill give you a hint.
If you want to convert a date.toString() to date, use this.
Date date = new Date();
String s = date.toString();
DateTimeFormatter dtf = DateTimeFormatter.ofPattern("EEE MMM dd HH:mm:ss zzz yyyy", Locale.ROOT);
Date birthDay = Date.from(ZonedDateTime.parse(s, dtf).toInstant());
Good luck ;)
GO TO FULL VERSION