hi,
    here I start java easy learning Strating program,where we use Herbert Schildt Java reference BOOK so this first page where proceeding  programming !

Thank  you

Muhammad haroon Khan

Bad Code:

Do we not think enough when coding? Do we jump to the first solution without really considering the problem, without trying to analyze and decompose it and understand the components and orthogonal forces involved? Is that the cause of bad code (together with time press) and the reason why we typically see a “patchvolution” rather than evolution (of design)?

For example I want a certain item on my list shown grayed out because it has been marked for removal or is currently being edited and I therefore add a flag called isDisabled. But if I really thought about it, I would likely call it based on the purpose rather than display, e.g. is Being Edited. And I have often observed that I/we tend to jump to the first acceptable solution without trying to consider other, (radically) different and perhaps better alternatives. That is easily explained with our inborn intellectual laziness and we certainly can agree that we should not over think things and that we need to ship but still, shouldn’t we try to think a little more?

The Clojure community has been very inspiring for me in this regard. There is a strong focus on spending more time on the problem than the solution to really understand it, and on separating the different concerns involved and adressing them separately, as well as on achieving simplicity. One of the manifestation is the strong preference of small, focused, composable libraries over frameworks. F.ex. it took couple of years for Clojure to get support for named arguments – but the result – destructuring – is something much more powerful, that now pervades the whole languages (of course, this is a language, not an app). When you listen to Rich Hickey talking f.ex. about core.async (vs. agents etc.) you see that the man thought deeply about the problem, alternatives, and their pros and cons.

May be we should spend little more time with our problems before jumping to solutions, no matter how much we like to solve things. Perhaps we would end up with a much better code than we typically have, and thus considerably lower maintenance costs.

Ref: Simple Made Easy, The Clojure Philosophy from Joy of Clojure.

Published at DZone with permission of Jakub Holý, author and DZone MVB. (source)

Hackers Can Exploit 94 Percent of Java Users

By Marshall Honorof

FOLLOW US

SHARE

Credit: Oracle

Java is such a ubiquitous system that it's almost impossible to be active online and avoid it. It's a shame, then, that it's also one of the most easily exploitable applications on the Web. If you use Java, then statistically speaking, there is a 94 percent chance that you are open to a particularly nasty hack of one kind or another.
Websense, a company that provides online security solutions, analyzed common security vulnerabilities in different versions of Java. The findings were troubling for those who want to keep their systems safe: Between 60 and 94 percent of Java users are vulnerable to the Cool, Gong Da, MiniDuke, Blackhole 2.0, RedKit and CritXPack exploit kits, bundles of malware that attack Web browsers.
While these hacking tools vary in scope, they all play havoc with the user's computer. Cool (by far the most common kit) sends fraudulent requests to steal credit card information. MiniDuke can copy or delete files from private directories. Others can monitor online activities, share information without permission or further compromise security by downloading additional exploits.
If you have the latest version of Java, you have little to worry about, as only about 5 percent of exploits target it. Most users, however, are stuck on older versions, which are far more open to attack. In fact, more than half of Java users have not updated in the last two years. Oracle, the company that produces Java, offers no support for these archaic versions of the program, making their users into easy prey.
Aside from updating to the most recent version, there are a few ways to stay on top of Java vulnerabilities. While the program is absolutely necessary for a variety of applications from the Adobe Suite to "Minecraft," relatively few websites rely on it.
You can disable Java entirely without losing out on too many online applications. Accessing the "Options," "Preferences" or "Settings" menu section in your browser of choice, then looking for "Plug-ins" or "Extensions" (sometimes located in "Advanced Options") will allow you to turn off Java. [See also: 8 Security Basics the Experts Want You to Know]
More advanced users can micromanage Java applications as well. In addition to disabling Java, most browsers allow users to create exceptions for safe sites that require it. Even though Java is a relatively vulnerable program, most unsafe exploits come from unsafe sites, not Web pages in an average user's everyday routine.
The unfortunate truth is that you can't access everything on the Internet without Java, and you can't be completely safe with it. Nevertheless, you can minimize your risk with a few simple steps, and that will set you apart from 94 percent of more easily exploited users.
Follow Marshall Honorof @marshallhonorof. Follow us @TechNewsDaily, Facebook or Google+.

• America's Top 10 Least Secure Cities
• Five Signs Your PC is Infected
• 2013 Best Mobile Website Builder Reviews