Writing a novelWrite a novel
To write good code is like writing a novel.
As I thought about their observation, I came to the conclusion that there are many resemblances between a computer scientist who writes a piece of software and a novelist. Writing a novel, writers must enter the heads of their people. The reason I use the term "grow" is that it is seldom for a novelist to fully understand the inner life of a person at the beginning of a novel; the personages develop throughout the writing world.
While you may think you know the client of your application from the very first moment, it is more likely that your perception of that client will evolve over the years. Authors are writing. You' re a writer. They' re writing as much as they do because they know that it's better to get words on a page because they know that most of their work is erased or revised during the work.
While it can be very enticing to begin processing once a phrase or section is on the page, it interrupts the author's stream and keeps him from writing even better work. Their first attempt should focus on getting the source text onto the display and working as planned.
Later, you can go back and factor in as soon as you discover that you have a double-coded message or that your power is becoming a problem. In the course of the years you will develop as a developer and you will begin to write clean and succinct source on the first one. It is better to have an unpleasant piece of coding that works at the end of a working days than a few "perfect" rows of coding that you can't show to anyone.
Authors always stress that they have to be in a daily routines and writing every single pen. Irrespective of whether this tag is working on a work, writing poems, writing in a magazine or any other kind of focussed writing. We also have to practise regularly as a programmer to become better.
It doesn't matter whether you want to learn a new programming style or extend an application with new functions, it is important to write regularly. If you get your mind to think about some coding today, it will be much simpler to produce more coding again later. Work on a programme every day this fortnight will make it easy to find clean problem solving in the coming few days and even more.
I am sensitive to authors; often they spent month or years writing a tale just to get letter of refusal from editors or hard criticism from reviewers for their work. Moreover, the history completion trial is full of obstacles. We often work on a project that feels endless and wishes we could move on to something new.
Sometimes we have the feeling that we are working on an insoluble coding issue, or that the source text we can type is of horrible pasta-style. While there is no simple answer to any of these issues, it is important to celebrating the small triumphs and not just the long-term success.
If you think you're writing pasta today, you' re building some self-esteem by looking at a passpaghetti written in the year ago - now, which was a real pasta number.