Logesh Paul > Recent Status Updates

The major weakness of all education system is that they neither teach nor encourage the habit of DEFINITE DECISION

Six of these principles; DESIRE, DECISION, FAITH, PERSISTENCE, THE MASTER MIND and ORGANIZED PLANNING

These important changes usually begin in the form of a DEFINITE DECISION in the minds of a relatively small number of people.

Genuine wisdom is usally conspicious through modesty and silence

If you are influenced by the opinions of others, you will have no DESIRE of your own.

Men are paid, not merely for what they know, but more particularly for `What they do with that which they know`

when writing any text in your code — whether comments, logging, dialogs, or test data — always ask yourself how it will look if it becomes public. It will save some red faces all around.

"a lie can travel halfway around the world, while the truth is putting on it's shoes"

10,000 hours is a lot: about 20 hours a week for 10 years.

you have to have a minimum amount of natural ability to get started in a sport or profession. After that, the people who excel are the ones who work the hardest.

Deliberate practice means practising something you are not good at.

"It takes elite performers a minimum of 10,000 hours of deliberate focused practice to become experts"

Comments should say something code does not and cannot say.

If it was hard to write, it should be hard to read. So write comments

Make your function short and focused on a single task. The old 24 line limit still applies.

Functions should have few parameters (four is a good upper bound)

Instead of simply correcting mistakes in code, the purpose of code reviews should be to share knowledge and establish common coding guidelines.

Getting designs fast becomes the central push of engineering firms.

Take construction as an example, if you get the design ready the implementation is simple and can be estimated; Code is no different.

"A Quitter never wins - and - A Winner never quits"

Temporary defeat is not permanent failure. It may only mean that your plans have not been sound. Build other plans, Start all over again.

He met with temporary defeat ten thousand times before his efforts were crowned with success. (Thomas A. Edison)

Henry Ford accumulated a fortune, not because of his superior mind, but he adopted and followed a PLAN which proved to be sound.

The entire universe consists of but two elements — matter and energy.

Through the combination of energy and matter, has been created everything perceptible to man, from the largest start which floats in the heavens, down to and including man, himself.

The Imagination is literally the workshop wherein are fashioned all plans created by man. The impulse, the DESIRE, is given shape, form and ACTION through the aid of the imaginative faculty of the mind.

It has been said that man can create anything which he can imagine.

Check your code first before looking to blame others.

"Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth"

Caring for our own code is one thing. Caring for the team's code is quite another. Teams help one another and clean up after one another.

"Try to leave this world a little better than you found it"

You might simply improve the name of one variable, or split one large function into smaller functions. You might break a circular dependency, or add an interface to decouple policy with detail.

- Avoid the temptation to rewrite everything.
- Many incremental changes are better than one massive change.
- New technology is an insufficient reason to refactor.

Beautiful code is simple code. Each individual part is kept simple with simple responsibilities and simple relationships with the other parts of the system. This is the way we can keep the system maintainable over time, with clean, simple, testable code, ensuring a high speed of development throughout the lifetime of the system.

"The beauty of style and harmony and grace and good rhythm depends on simplicity" — Plato

- Make sure code formatting is part of the build process
- Use static code analysis tools to scan for unwanted antipatterns
- Do not only measure test coverage but automatically check the results

Spending an hour watching users is more informative than spending a day guessing what they want.

Get the user to talk through his or her progress. Don't interrupt, Don't try to help. Keep asking yourself, "Why is he doing that" and "Why is she not doing that"