|
The third issue of Artistic Programming newsletters is out and is
multiplying fast among the programming community. Have you caught the virus
yet?
A Quick Word
We all have met
programmers who seem to have a magical touch.
They write a complex piece of software and it works the first time it is
run.
When called to fix a peer's bug, they just look at different parts of the
code, change a "<" to "<=" and everything works great.
When searching for something on Google, they plug in a few keywords and the
first article gives the information being searched.
Even in meetings, everybody listens to them.
Everything in life seems to be partial towards them.
Computers, compilers,
team members, managers, even Google seems to favor them.
Life is not fair.
And then, there are many who have to write and re-write their code again and
again to make it work.
They spend nights and nights fixing bugs that seem to exist without any
rhyme or reason.
They spend hours searching for the information on Google and still get
little information.
They spend all their time in meetings, sulking. "Nobody listens to me."
What is the common thread
running behind all of these?
It is not your knowledge of programming language, data structures,
algorithms (or even Google keywords).
It is all about "thinking
skills". An individual with great thinking skills will be very effective and
efficient everywhere.
No other single skill
would elevate your productivity and effectiveness as a programmer as much as
enhancing your skills of thinking effectively as a programmer.
Mysteriously, when you
master it, you will find yourself being productive and effective everywhere
else.
May be, you will get a big
applause in the next team meeting for that suggestion you make.
Who knows, you may be the
winner in the game of bowling the next time your team goes out...
APPLY IT. You
know you have it.
DID YOU KNOW?
In 1990, when Java was still just an
idea, Gosling knew that this new language had to focus on developer
productivity. He concentrated on reliability, object-oriented capability,
and initiating early error checking. As enterprises migrate from C++ to
Java development systems, formal studies—such as IDC's
Java Technology
Pays Positively—are showing that developer productivity has increased
two-fold. According to IDC's study, the productivity has increased because
Java's discipline yields a tighter object-oriented framework and fewer
errors during unit testing. The plethora of available Java development
tools also helps developers leverage the language's power quickly and
efficiently.

"Let us change our traditional attitude to the construction of
programs. Instead of imagining that our main task is to instruct a computer what
to do, let us concentrate rather on explaining to human beings what we want a
computer to do."
Donald Knuth

F-O-O-D For Thot!
Descartes said - I think, therefore I am.
He probably meant to say:
I think __________, therefore I am _________.
Fill it with whatever you want.
I think EFFECTIVE, therefore I am EFFECTIVE.
I think GREAT, therefore I am GREAT.
|