Skip to main content

An English Language Refresher

Today I have deviated a bit from the original category of my postings. From software programming languages to the english language. Very often while I find that I have forgotten the grammer priciples I learned in school. So I decided to revise them, and thought I'd share the refresher on my blog site. Here goes...
A noun is usually a thing. Nouns are preceded by words such as a, the, my, such, an, some. Some nouns are however difficult to identify. Words such as egoist, asceticism, and misogynist do not come accross as nouns right away. However if we put them in the context of a sentance... "... an egoist", "such asceticism...", "the misogynist...", then the above rule clearly identifies them as nouns. The confusion with these words is that at first glance they seem to be adjectives. "He is an egoist". Egoist is a description of a person 'He'. However because egoist is preceded with a 'an', it is a noun. This law is conistent if you think of sentances like "This is an apple", etc. Such nouns usually end in suffixes like -ness, -is, -ism, -y, -ion, etc.

A verb is usally an activity. It fits into the pattern, "Let us __________". A verb always has a counterpart which denotes the past tense. For example philander is a verb and it's past tense is philandered. Nouns on the other hand do not have a past tense. Verbs often end in suffixes like -ate, -ize, -fy, etc.

This primer will not help you in programming, but will probably help in creating better documentation. Remember software developement goes beyond mere programming :-)

Comments

Suresh S SCJP1.4 said…
hi

your blogis nice.keep pace on it.i have also a blog called diepresse.com (means news) but nobody is posting .please post daily to me ok.i am B.E. CSE graduate help me
3:38 PM
Post a Comment

Popular posts from this blog

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...
Post a Comment
Read more

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other ...
3 comments
Read more

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ...
Post a Comment
Read more