Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Re: Re: Re: Re: OT: JavaJunkies (Javamonks sorta)

by exussum0 (Vicar)
on Feb 05, 2004 at 18:58 UTC ( [id://326844]=note: print w/replies, xml ) Need Help??


in reply to Re: Re: Re: OT: JavaJunkies (Javamonks sorta)
in thread OT: JavaJunkies (Javamonks sorta)

To paraphrase Mr. Wall (I think, "I prefer people stay out of my house because they are not invited, not because I have a shotgun". Public/private can dominate a huge java app, and while occasionally useful for debug, they make tracing painful and the app slower.
Painful? The compiler will usually say, "no, you can't do that." But OOP and security does slow down an app, i totally agree.
Regarding "stupid coworkers", I prefer to either educate them or not work with them. I consider myself a professional, I expect the people who work with me to act like ones as well.
It's the problem with life and rules. People break them if they can be broken. It happens. Not because people are stupid, or malicious, or tricky. Sometimes, people make stupid mistakes. It's the reason people got into the habit of writing, if(1 == x). It's so people won't accidentally lose an equal symbol and create a software bug.

The problem is, when you hire a consultant, someone who has no reason to play nice other than to get the mission done, do you trust him to play nice? What about the developer that's still not seasoned enough to know better. What about the developer who says they don't care? When you have to clean up their messes, it's time lost and sometimes money lost due to "bad software practices."

About swing... I've done the same thing, and have done the "why isn't this thing" working for an hour or two. Swing issues can usually be reduced. Easily. If something isn't aligning right, have the user give you the constraints before hand. Something not aligning right? Change the background colour of the relative widgets and redisplay. You'll easily see where the broken overlap/stretching comes in.

Contrary to popular belief, good C code can be written. It just takes *good* coders. Java allows mediocre coders to appear to be talented because they are hiding behind OOP that allows huge interconnects between hundreds of files. Where a procedural coder can quickly be hit for not having a design, an OO java coder can usually say "of coruse I have design, look, UML!" and the design is often just a bunch of random objects. and that's PC.
The only difference between Java and C in terms of procedural programming is making all your methods static. And the same goop you get with bad object design, can be done with bad procedural design. Look at student's C programs, that's usually pretty ugly.

BUt you are right, it doesn't make good coders. Java is a tool, just like perl or c. It takes good coders to write good code. Giving a person a car with automatic drive doesn't make them a good driver. It just makes it easier to do. But if you want to use a stick, know what you are doing.. 'cause just as it's better if you master it, it's easy to break.


Play that funky music white boy..

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://326844]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having an uproarious good time at the Monastery: (6)
As of 2024-03-28 09:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found