Re: Top 10 Java Serialization Interview Question
buddy s wrote:
I have shared my experience with Serialization in java in this blog
How good can your experience be if you cannot even spell "Java" correctly,
either in your post or your blog? Jesus Christ, man!
Also, since you it's the top /ten/ questions, then the word "question" in your
posts should be plural: "questions".
I recommend that people avoid your advice. I reviewed your site, and it's
nothing but advice on how to fail the interview. It is a paean of ignorance
and misinformation. It is, in a word, utter crap.
post it contains some of good Serialization questions asked during a
What is a "good Serialization question", please?
senior or mid junior level interview for Java. I hope this would be
useful. Please contribute any question which I have not covered and
worthy to share with community.
Here are some questions and comments:
- Could you please have someone who knows grammar and spelling proofread your
site? From the very first sentence it is utterly painful to read.
- Only a few "commercial project [sic]", according to you, use Java
serialization (only you call it "java serialization") for their "persistence
requirement". Do you know of any that do?
- In big bold letters you proclaim, "Java serialization is the process which
is used to serialize object in java by storing object???s state into a file with
extension .ser ...". That is flat-out wrong.
- You make statements like, "This is most [sic] frequently asked question in
java [sic] serialization interview." Based on what evidence do you say that?
- Why do you give a wrong answer to that?
- What the heck is a "Java serialization interview"?
- "Serializable interface exists in java.lang package ..." Dude! How can you
live with yourself? CHECK YOUR SIMPLE FACTS AT LEAST!
It's in the 'java.io' package, you, you, ... sputter!
- "SerialVersionUID [sic] is a public static final constant ..." Once again,
wrong.
- "... if you don't want any field to be part of object's state then declare
it either static or transient based on your need and it will not be included
during java serialization process." Wow. "based on your need" gives no help
to dispel the impression that you have made 'static' and 'transient' equivalent.
- Your advice regarding version changes is confused and incomplete at best.
For example, the notion that serialization support commits the maintainer to
another public interface is nowhere mentioned.
In summary, if your blog were part of a Java programming job application, you
would not get hired.
I suggest you study in particular Joshua Bloch's advice about serialization in
/Effective Java/, <http://java.sun.com/docs/books/effective/>, to fill in the
gaps in your knowledge.
--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg