Dev4Developer

Intro - D Programming Language - Digital Mars

2011-01-17T19:00:00.000+05:30

Intro - D Programming Language - Digital Mars: "reat, just"

Java Blog

2011-01-12T16:37:00.000+05:30

Java Blog

visit this for bright knowledge of Java.

If Bollywood films were made by Indian IT Engineers then they may be called....

2011-01-12T15:44:00.002+05:30

** Munna Bhi MCSA
** Kal MSN Ho Na Ho
** Love in mIRC
** Tere Nick
** ID Mil Gaya
** Chat To Kero
** Ek Programmer Thi
** Yeh Hack Horaha Hai
** Hum Pyar PC Se Kar Baithe
** Network Ke Us Paar
** Meri Disc Tumhare Paas Hai
** Aao Chat Kare
** C Wale Job Le Jayenge
** Programmer No.1
** Mera Naam Developer
** Hum Apke Memory Mein Rahate Hein
** Do Processor, Baarah Terminal
** Tera Code Chal Gaya
** Har Din Jo Mail Karega
** Debugging Koi Khel Nahi
** Jish Desh Mein Bill Gates Rehatha Hai
** Raju Ban Gaya MCSE ..!
** Client Ek Numbari, C Programmer Dus Numbari
** Login Karo Sajana
** Naukar PC Ka
** 1942 -- A Bug Story
** Kaho Na Virus Hai
** Crash Se Crash Tak
** Haan Meine Bhi Debug Kiya Hai
** Shaheed Hacker Singh
** Password De Ke Dekho
** Terminal Apna , Login Parayi
** Mr. Network Lal
** Terminal Sajaake Rakhna
** Hackers Ka Raja, Debuggers Ki Rani
** Kyonki Mein Debug Nahin Kartha
** Phir Theri Java-script Yaad Aayi
** Hang To Hona Hi Tha !!!!!!!!!!!!

An Overview of RMI Applications (The Java™ Tutorials > RMI)

2010-12-29T17:11:00.000+05:30

An Overview of RMI Applications (The Java™ Tutorials > RMI)

Programming today

2010-10-19T21:25:00.001+05:30

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Java Developer: Java Important Notes

2010-10-04T18:03:00.000+05:30

Java Developer: Java Important Notes: "Previous posted link might not work..... https://docs.google.com/document/pub?id=1enq25nqaXiWkcN10hvtzmm9y7xPvKsvfVjnReIQ0uJ4"

.NET is pronounced like “Doughnut”, only different

2010-09-10T00:01:00.002+05:30

Ron Burk wrote a terrific, funny article “A Brief History of Windows Programming Revolutions” that describes the internal back-and-forth struggle between programming groups at Microsoft in their endless pursuit to eliminate DLL Hell. First there was DDE, then OLE, COM, ActiveX, MFC, ATL, and eventually .NET:

“And that brings us up to date with .NET (pronounced like ‘doughnut’, only different), which is like the Internet, only with more press releases. Let’s be very, very clear about one thing: .NET will eliminate DLL Hell. .NET includes a new programming language called C# (turns out there was a fatal flaw in Active++ Jspresso, so just as well it died). .NET includes a virtual runtime machine that all languages will use (turns out there’s a fatal flaw in relying on Intel CPUs).”

The Simpsons, Copyright © Fox, All Rights Reserved.The serious point behind this funny article is how each of these Microsoft “revolutions” were supposed to be the panacea of Windows development, only to be replaced in a few short years by the next-best-thing.

At least Microsoft has stuck with .NET Framework for 8 years, but the churn continues within the .NET development ecosystem. Remember how WindowsForms was supposed to provide a rich client GUI that ran across all hardware platforms? Turns out it didn’t work so well in a web browser, so Microsoft invented WebForms. And MVC. WinForms also didn’t render well on Linux, so open-source geeks use Gtk# instead. And WinForms is too heavy to run on mobile devices, so Microsoft ejected it from the .NET Compact Framework. But .NET CF is too “old school” for smartphones, so now there’s Silverlight. Are you following me?

In the tech industry, the only constant is change.

Regular expression with php

2010-09-07T22:19:00.000+05:30

Regular expression with php

2010-09-07T20:16:00.001+05:30

"The only thing I like about stones that come in my way is: once I pass them, they automatically become my milestones."

Click it.....

2010-09-03T19:48:00.001+05:30

Special Password

2010-08-26T18:24:00.001+05:30

During a recent security audit, a company discovered that a
blonde employee was using the following password:

“MickeyMinniePlutoHueyLouieDeweyDonaldGoofySacramento”

When the company asked the blonde why she had such a long password, she said the login screen required the password to be at least 8 characters long and include at least one capital.

Programming

2010-08-24T16:24:00.002+05:30

“Don’t worry if it doesn’t work right. If everything did, you’d be out of a job.”
(Mosher’s Law of Software Engineering)

“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.”
(Bill Gates)

“Writing code has a place in the human hierarchy worth somewhere above grave robbing and beneath managing.”
(Gerald Weinberg)

“First learn computer science and all the theory. Next develop a programming style. Then forget all that and just hack.”
(George Carrette)

“First, solve the problem. Then, write the code.”
(John Johnson)

“Optimism is an occupational hazard of programming; feedback is the treatment.”
(Kent Beck)

“To iterate is human, to recurse divine.”
(L. Peter Deutsch)

. “The best thing about a boolean is even if you are wrong, you are only off by a bit.”
(Anonymous)

My Life

2010-08-16T20:45:00.002+05:30

Life is an eternal quest about knowing oneself. It's time to challenge yourself, to rediscover your hidden traits, talents, and tendencies. Several inconvenient questions, which you have swept under the carpet, might resurface.

"Tips 4 Hapy lyf"

2010-08-09T17:11:00.002+05:30

1.Walk for 10-30 min daily.

2.Sit quitely 4 atleast 10 min daily in isolation.

3.Try 2 make lauf atleast 3 ppl daily.

4.Liv wid the 3 'E's (Energy,Enthusiasm n Empathy).

5.Drink green tea n plenty of watr.

6.Read more books dan last yr.

7.Lyf z 2 short 2 waste tym hating sum1.

8.Apreciate ur body n its marvels.

9.Eat Brkfst lyk king,lunch lyk a prince & dinnr lyk begger.

10.Smyl n lauf more often

11.Dnt let an oprtnty 2 hug a frnd.

12.Make peace wid ur past,so as nt 2 ruin ur prsnt.

13.Dnt compare ur lyf wid othrs.U hv no idea of d highways dey hv travelled durin deir lives.

Software Development

2010-07-24T20:51:00.001+05:30

“Good programmers use their brains, but good guidelines save us having to think out every case.”
(Francis Glassborow)

“In software, we rarely have meaningful requirements. Even if we do, the only measure of success that matters is whether our solution solves the customer’s shifting idea of what their problem is.”
(Jeff Atwood)

“Considering the current sad state of our computer programs, software development is clearly still a black art, and cannot yet be called an engineering discipline.”
(Bill Clinton)

“You can’t have great software without a great team, and most software teams behave like dysfunctional families.”
(Jim McCarthy)

Software Developer Salaries

2010-07-19T21:11:00.000+05:30

Language Developer Salary Senior Developer Junior Developer
C++ $85K $90K $52K
Python $84K — —
C# $81K $91K $57K
C $80K $88K —
UI $79K $91K —
Java $79K $84K $54K
LAMP $75K $78K $44K
Ajax $78K — —
Cobol $77K $77K —
SQL $76K $79K $66K
Perl $76K $75K —
Ruby $75K — —
JavaScript $74K — —
Delphi $73K $80K —
VB.NET $71K $83K $52K
ColdFusion $70K $81K $44K
ASP.NET $68K $82K $55K
PHP $64K $73K $44K

Programming

2010-07-15T17:33:00.002+05:30

“Don’t worry if it doesn’t work right. If everything did, you’d be out of a job.”
(Mosher’s Law of Software Engineering)

“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.”
(Bill Gates)

“Writing code has a place in the human hierarchy worth somewhere above grave robbing and beneath managing.”
(Gerald Weinberg)

“First learn computer science and all the theory. Next develop a programming style. Then forget all that and just hack.”
(George Carrette)

“First, solve the problem. Then, write the code.”
(John Johnson)

“Optimism is an occupational hazard of programming; feedback is the treatment.”
(Kent Beck)

“To iterate is human, to recurse divine.”
(L. Peter Deutsch)

“The best thing about a boolean is even if you are wrong, you are only off by a bit.”
(Anonymous)

“Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration.”
(Stan Kelly-Bootle)

Programmers

2010-07-14T17:57:00.002+05:30

“Programmers are in a race with the Universe to create bigger and better idiot-proof programs, while the Universe is trying to create bigger and better idiots. So far the Universe is winning.”
(Rich Cook)

“Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris.”
(Larry Wall)

“The trouble with programmers is that you can never tell what a programmer is doing until it’s too late.”
(Seymour Cray)

“That’s the thing about people who think they hate computers. What they really hate is lousy programmers.”
(Larry Niven)

“For a long time it puzzled me how something so expensive, so leading edge, could be so useless. And then it occurred to me that a computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are, in short, a perfect match.”
(Bill Bryson)

“Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter.”
(Eric Raymond)

“A programmer is a person who passes as an exacting expert on the basis of being able to turn out, after innumerable punching, an infinite series of incomprehensive answers calculated with micrometric precisions from vague assumptions based on debatable figures taken from inconclusive documents and carried out on instruments of problematical accuracy by persons of dubious reliability and questionable mentality for the avowed purpose of annoying and confounding a hopelessly defenseless department that was unfortunate enough to ask for the information in the first place.”
(IEEE Grid newsmagazine)

“A hacker on a roll may be able to produce–in a period of a few months–something that a small development group (say, 7-8 people) would have a hard time getting together over a year. IBM used to report that certain programmers might be as much as 100 times as productive as other workers, or more.”
(Peter Seebach)

“The best programmers are not marginally better than merely good ones. They are an order-of-magnitude better, measured by whatever standard: conceptual creativity, speed, ingenuity of design, or problem-solving ability.”
(Randall E. Stross)

“A great lathe operator commands several times the wage of an average lathe operator, but a great writer of software code is worth 10,000 times the price of an average software writer.”
(Bill Gates)

13 Tips to Comment Your Code

2010-07-13T19:18:00.000+05:30

Following are 13 tips on how to comment your source code so that it is easier to understand and maintain over time.

1. Comment each level

Comment each code block, using a uniform approach for each level. For example:

* For each class, include a brief description, author and date of last modification
* For each method, include a description of its purpose, functions, parameters and results

Adopting comment standards is important when working with a team. Of course, it is acceptable and even advisable to use comment conventions and tools (such as XML in C# or Javadoc for Java) to facilitate this task.
2. Use paragraph comments

Break code blocks into multiple “paragraphs” that each perform a single task, then add a comment at the beginning of each block to instruct the reader on what is about to happen.

// Check that all data records
// are correct
foreach (Record record in records)
{
if (rec.checkStatus()==Status.OK)
{
. . .
}
}
// Now we begin to perform
// transactions
Context ctx = new ApplicationContext();
ctx.BeginTransaction();
. . .

3. Align comments in consecutive lines

For multiple lines of code with trailing comments, align the comments so they will be easy to read.

const MAX_ITEMS = 10; // maximum number of packets
const MASK = 0x1F; // mask bit TCP

Some developers use tabs to align comments, while others use spaces. Because tab stops can vary among editors and IDEs, the best approach is to use spaces.
4. Don’t insult the reader’s intelligence

Avoid obvious comments such as:

if (a == 5) // if a equals 5
counter = 0; // set the counter to zero

This wastes your time writing needless comments and distracts the reader with details that can be easily deduced from the code.
5. Be polite

Avoid rude comments like, “Notice the stupid user has entered a negative number,” or “This fixes the side effect produced by the pathetically inept implementation of the initial developer.” Such comments do not reflect well upon their author, and you never know who may read these comments in the future: your boss, a customer, or the pathetically inept developer you just insulted.
6. Get to the point

Don’t write more in comments than is needed to convey the idea. Avoid ASCII art, jokes, poetry and hyperverbosity. In short, keep the comments simple and direct.
7. Use a consistent style

Some people believe that comments should be written so that non-programmers can understand them. Others believe that comments should be directed at developers only. In any event, as stated in Successful Strategies for Commenting Code, what matters is that comments are consistent and always targeted to the same audience. Personally, I doubt many non-developers will be reading code, so comments should target other developers.
8. Use special tags for internal use

When working on code as a team, adopt a consistent set of tags to communicate among programmers. For example, many teams use a “TODO:” tag to indicate a section of code that requires additional work:

int Estimate(int x, int y)
{
// TODO: implement the calculations
return 0;
}

Tag comments don’t explain code; rather they seek attention or deliver a message. But if you use this technique, remember to follow up and actually do what the message is asking.
9. Comment code while writing it

Add comments while you write code and it’s fresh in your memory. If you leave comments until the end, it will take you twice as long, if you do it at all. “I have no time to comment,” “I’m in a hurry,” and “The project is delayed” are all simply excuses to avoid documenting your code. Some developers believe you should write comments before code as a way to plan out your ultimate solution. For example:

public void ProcessOrder()
{
// Make sure the products are available
// Check that the customer is valid
// Send the order to the store
// Generate bill
}

10. Write comments as if they were for you (in fact, they are)

When it comes to commenting code, think not only about the developers who will maintain your code in the future, but also think about yourself. In the words of the great Phil Haack:

“As soon as a line of code is laid on the screen, you’re in maintenance mode on that piece of code.”

As a result, we ourselves will be the first beneficiaries (or victims) of our good (or bad) comments.
11. Update comments when you update the code

There is no point in commenting correctly on code if the comments are not changed with the code. Both code and comments must move in parallel, otherwise the comments will actually make life more difficult for developers who maintain your code. Pay special attention to refactoring tools that automatically update code but leave comments unchanged and hence obsolete in the same instant.
12. The golden rule of comments: readable code

One of the basic principles for many developers: Let your code speak for itself. Although one suspects this movement is led by programmers who do not like to write comments, it is true that self-explanatory code can go a long way toward making code that’s easier to understand and can even render comments unnecessary. For example, the code in my Fluid Interfaces article shows how clear self-explanatory code can be:

Calculator calc = new Calculator();
calc.Set(0);
calc.Add(10);
calc.Multiply(2);
calc.Subtract(4);
Console.WriteLine( "Result: {0}", calc.Get() );

In this example, comments are not needed and would likely violate tip #4. To facilitate readable code, you might consider using proper names (as described in the classic Ottinger’s Rules), ensure correct indentation, and adopt coding style guides. Failure to comply with this tip may result in comments that seem to apologize for bad code.
13. Share these tips with your colleagues

Although tip #10 shows how we ourselves benefit immediately from good comments, these tips will benefit all developers, especially in the context of team working together. Therefore, feel free to share these commenting tips with your colleagues to create code that is easier to understand and maintain

21 Laws of Computer Programming

2010-07-12T16:42:00.000+05:30

1. Any given program, once deployed, is already obsolete.
2. It is easier to change the specification to fit the program than vice versa.
3. If a program is useful, it will have to be changed.
4. If a program is useless, it will have to be documented.
5. Only ten percent of the code in any given program will ever execute.
6. Software expands to consume all available resources.
7. Any non-trivial program contains at least one error.
8. The probability of a flawless demo is inversely proportional to the number of people watching, raised to the power of the amount of money involved.
9. Not until a program has been in production for at least six months will its most harmful error be discovered.
10. Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
11. The effort required to correct an error increases exponentially with time.
12. Program complexity grows until it exceeds the capabilities of the programmer who must maintain it.
13. Any code of your own that you haven’t looked at in months might as well have been written by someone else.
14. Inside every small program is a large program struggling to get out.
15. The sooner you start coding a program, the longer it will take.
16. A carelessly planned project takes three times longer to complete than expected; a carefully planned project takes only twice as long.
17. Adding programmers to a late project makes it later.
18. A program is never less than 90% complete, and never more than 95% complete.
19. If you automate a mess, you get an automated mess.
20. Build a program that even a fool can use, and only a fool will want to use it.
21. Users truly don’t know what they want in a program until they use it.

Great Computer Quotes

2010-07-09T20:11:00.002+05:30

1.“Computers are useless. They can only give you answers.”
(Pablo Picasso)

2.“Computers are like bikinis. They save people a lot of guesswork.”
(Sam Ewing)

3.“They have computers, and they may have other weapons of mass destruction.”
(Janet Reno)

4.“That’s what’s cool about working with computers. They don’t argue, they remember everything, and they don’t drink all your beer.”
(Paul Leary)

5.“If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.”
(Robert X. Cringely)

Quote of the day

2010-07-09T14:49:00.002+05:30

"One important key to success is
self-confidence. An important key to
self-confidence is preparation."

Online Radio Link

2010-07-08T17:47:00.000+05:30

Online Radio

RadioMirchi Link

Big FM Link

RadioMantra

2010-07-05T21:33:00.000+05:30

Hi Develolpers,
From now I am posting my experience about IT.