Andy Williamson wrote:I frequently argue with the lead developer, but he can always resort to the phrase, "well, in my experience its always worked to...," to which I always concede the argument. He should know, right?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Andy Williamson wrote:
-He told me never to use super.clone() when overriding the Object.clone method, suggesting instead that I should use a constructor. (Unless your class is final, a constructor violates the clone contract.)
-He told one developer to write a isGreaterThan and isLessThan method. He must have forgot about the Comparable interface.
-He used java.rmi.RemoteException outside the context of any RMI.
-He wraps all his exceptions into one SoftwareException, thus preventing the caller whose catching the exception from knowing what actually went wrong.
-He told the chief engineer that a List prohibits duplicate objects. (They don't. A Set does.)
-He prefers bug-prone methods like this, "Object objectFromXml(ObjectTypeEnum type, String xml)", as opposed to a safer method like, "<T> T objectFromXml(Class<T> clazz, String xml)".
-His view of good design regularly contradicts nearly everything I've read, including the oft-cited Effective Java by Joshua Bloch.
-Etc.
My material for SCJP (2008), SCWCD (2010), SCBCD (2010). About me
SCJP 6, SCWCD 5, SCBCD 5
That looks like strange advice to me.Lee Kian Giap wrote:Forget about it, . . . in this world money is more important than Java.
Campbell Ritchie wrote:
That looks like strange advice to me.Lee Kian Giap wrote:Forget about it, . . . in this world money is more important than Java.
Obviously you need money, otherwise you won't get your "three meals a day", but money is by no means the most important feature of a job.
SCJP 6, SCWCD 5, SCBCD 5
=
-He told me never to use super.clone() when overriding the Object.clone method, suggesting instead that I should use a constructor. (Unless your class is final, a constructor violates the clone contract.)
-He told one developer to write a isGreaterThan and isLessThan method. He must have forgot about the Comparable interface.
-He used java.rmi.RemoteException outside the context of any RMI.
-He wraps all his exceptions into one SoftwareException, thus preventing the caller whose catching the exception from knowing what actually went wrong.
-He told the chief engineer that a List prohibits duplicate objects. (They don't. A Set does.)
-He prefers bug-prone methods like this, "Object objectFromXml(ObjectTypeEnum type, String xml)", as opposed to a safer method like, "<T> T objectFromXml(Class<T> clazz, String xml)".
-His view of good design regularly contradicts nearly everything I've read, including the oft-cited Effective Java by Joshua Bloch.
-Etc.
No Kaustubh No Fun, Know Kaustubh Know Fun..
SCJP 6, SCWCD 5, SCBCD 5
Lee Kian Giap wrote:In addition to my above opinion, I share my bad feeling in early years of job
Here is one of the example that I share with you, the most simple thing in Java.
My opinion to my senior (even the newbie know this) that using List as a Class is wrong, get what I mean ? See below:
my senior:
my opinion:
I keep argue on this, and a lot of code in the application all using List as Class, you know how difficult to develop it ? how terrible to debug it ? But, do you know that the system use by more than 10 company and more than 50,000 user which doing transaction on that system everyday ? It keep earning money for the boss for every transaction happen on that system.
What response I get you know ?
Senior ask me :"the application got bug ? the application hang ? the application fail ? No, right ? So what's wrong with ArrayList instead of having lot of class file ? I use ArrayList and write all code in JSP without servlet, when user need changes, I change it and deploy immediately, no server restart needed ! You use classes every place, more and more file, every change which need immediate upload need to build and server restart."
Senior continue ask me :"How many yearSSS of experience you have?"
I answer:"1.5 years"
Senior say:"That's why!"
In addition to that, I also argue on the database design, no relational constraint which causes all rubbish data inside there, not using CVS/SVN to manage code ... end up ... I get a warning letter from management level ... said that "Our company don't encourage this kind of attitude ... ... As a junior, job scope is to fulfill ... ..."
At last, I tender resignation letter and leave. I spend one month to get the next job, one month without salary is a difficult feeling for me, I have to tight my belt ... I get pressure from my family
You know what is my senior position now ?
Become a MANAGER earning big salary, so you get what I mean ? Company is setup to earn money from customer, not setup for you to implement best practice.
... ... this is the 2 cents experience of mine ... ...
No Kaustubh No Fun, Know Kaustubh Know Fun..
T. Huy Nguyen wrote:Interesting story, but I keep wondering if you didn't argue with your senior then, for money is more important than Java, would you be where you are today?
SCJP 6, SCWCD 5, SCBCD 5
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Lee Kian Giap wrote:
he can tell you Java is easy "only Create, Read, Update, Delete".
Mike Isano wrote:
Lee Kian Giap wrote:
he can tell you Java is easy "only Create, Read, Update, Delete".
For CRUD applications that statement is correct.
SCJP 6, SCWCD 5, SCBCD 5
Collin Dugas wrote:um, I'd say find a better place to work at.
You have a team of developers working on Java for first time for a critical project where bugs could hurt or KILL people? Either you're bluffing or the place has got some serious issues.
The place doesn't sound fun at all
People here get pretty worked up on language so I'd only say run from there man.
PS : How I hate seeing folks fighting over variable and method names.
Henry Wong wrote:
To be fair, this is told from one point of view -- and even then, nothing jumps out as really that bad.
Cloneable or new constructor, Comparable or not, RMIException for non-RMI, List vs Set, are not only minor; and in some cases even arguable. Architecture, design, etc. is at a level much higher than these -- which seems just like details that can be debated at the code review.
Furthermore, it is actually very good considering that the lead is new to Java.
Henry
arulk pillai wrote:Little knowledge can be dangerous. I am currently working at a place where my manager thinks he is technical and intervenes in technical decision making process If you speak to him for 5 minutes you may think that he knows his stuff, but if you ask a few questions and spend say 15 minutes, you will realize that he is full of hot air. Getting things done is not only all about technical skills, but also about soft skills to to be tactfull, understand the politics, slowly changing things and earning the reputation, etc.
SCJP 6, SCWCD 5, SCBCD 5
Dan Walin wrote:The code will not be 100% exactly right according to standards, but there is a better chance that it is completed on time and meets the user specifications
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |