Archive for the ‘software’ Category

Google Calendar *.*’s Wishlist

April 21, 2006

Google Calendar has worked for me. I was not a Gmail user, but Google calender has forced me to shift to Gmail. The following are a few of my wishes of features in Google Calendar. (But i know Google people dont listen to me. Like in 'Mark All Read' feature of Google Reader. )

* Configurable duration of the day (eg. show only 7am to 10pm). This will fit the full calendar in my screen (no scrolling needed.)

* A public/shared view of the calendar. Will help me publish my busy/non busy hours.

* Previous 2 days and next 4 days view [ numbers should be configurable ]

* Integrate with Gmail/GTalk/GToolbar more closely

– from calendar give links to associated mail

– from gmail show calendar agenda in sidebar

* To-Do lists

* Set to-date equal to from-date by default if not available (eg. while adding event from mail)

* New entry / edit event details should also be popup ( like the event info popup )

* Multiple days (but not full day) event should be shown like single day event streteched across multiple days. (The current way of showing it in full day events is stupid.)

* Upload a file associated with an event

* Cell phone notification service in india and should be synced with a cell phones calendar πŸ™‚ (like Active Sync in Outlook)

* Should avoid being classified as "web based email" in websense!

| google calendar internet wish web | diggit


*.links 1

April 19, 2006

Use Academic search launched by to search for journals and publications.

Another way to access websites. Use Hostname to IP address and get the ip address of the website then use IP address to decimal calculator to get a decimal equivalent and then visit the website in this fashion http://3477384427

Tips: Developing High Traffic Web to make it handle millions of hits.

Top 10 Best Designed Blogs, looks like we might have to work very hard to compete.

Make your web better and more attractive using Top 10 CSS tutorials

How can you save your installation by using Windows Xp's Rebuild command

Rumours say that Oracle is set to launch own version of linux

Have a look at the screen-shots of new Yahoo! homepage.

Wanna know who is ignoring you using yahoo stealth settings, here is a hack for you.

chk out Aishwarya Rai in her first Hollywood movie trailer The Last Legion.

Dhoomk2 on Dalip Singh aka Great Khali, the first real WWE wrestler from India. Gaurav also shares his views and achievements of a labourer from Punjab, then a policemen, a Mr. India and now a WWE wrestler.

and a must watch trailer of Titanic 2: The surface, superb job of editing. πŸ˜‰

| live ip web blog design css trailer |

google calendar

April 13, 2006

google has released google calendar

with a rich features list –
– search support
– ‘quick add’ which i first saw in 30boxes and instantly liked it
– invitation handling.
calendar sharing looks useful. a group of people can edit same calendar.
gmail integration gives it the unmatched advantage. but it isnt as cool as one in zimbra.
event publishing looks cool too.
– draging,resizing(steps of half hour) of event
– the most important feature of google calendar is going to be Calendar Data API (coming soon…)

i am in search of a good calendar from years, and was never satisfied with anything availabe. i have tried almost every calendar available. all sucked big time including one from yahoo. recently released kiko and 30boxes are good, but couldnt make me a customer. i guessed google will acquire one soon. sad for them, google has come up with its own. hopefully google competitors will need one soon and they might get lucky.

i used php icalendar so far. hope google calendar will change something.

Bug Tales

April 8, 2006

Being a software developer is painful at times, not only we need to clean our own filth (read bugs) but others as well.

The coding we do is merely some 10-20% of total work and most of the time its providing support doing enhancements and fixing bugs.

Fixing bugs is the most common phenomenon in the industry the bigger the company [you can blame any particular company, but its same for everyone] the larger is the bug pool. Like entropy of the universe, the total bug count of the software industry keeps on growing. [ I know its bitter but its a truth.]

All the modern programming languages are designed in such a way to either minimize the bugs

or in case of some errors how to find them easily, so those of you who dont like the TRYing CATCHing and THROWing of Java, C++,C# better get used to it, because its for your own good.

Using log files is a good programming practice, it surely helps in saving a lot of time.

There is a dearth of good programmers in the earth. Mediocracy prevails through out the software industry[ the growing count of bugs is a proof].

Software engineering is a pain in the a$$ but it really saves your a$$ in the long run.

Anyway, you can always learn SE fundas, what this article is really is about bugs. What do you do when even after applying all the best practices [read software engineering] you get a bug in your module? Its very simple, you will have to fix it πŸ™‚

Fixing bugs is an ritual in itself, it involves lots of steps. A typical bug cycle goes like this [its not complete but you can get an idea].

1. Customer/Developer/QA/ notices a bug

2. Assigns it to the relevant team, from there it comes to the actual developer, some one like me

3. The developer has to provide a Resolution for the bug. He tries to reproduce the bug at his location and sees

  • If its a duplicate bug
  • or if he needs some more information [ if its a customer bug, the communication with the customer is mostly through the Support team]
  • or If it has to be deferred [that is fix it later]

4. Once its sure that the bug is there, the question comes, do we really need to fix it [ya there are times, like when a release of the product is at hand, its not really feasible to fix the bugs, usually these decisions had to be taken in the knowledge of higher authorities, i.e. managers]

5. Once its sure that the bug fixing has to be done, the developer provides the necessary fix, [that may or may not include code changes ].

6. Once the developers are done with their work, the bug is assigned to QA guys.

7. QA has to verify the bug, verfication means whether the original steps of reproducing the bug are still able to reproduce the bug or not. If not then the is the bug is understood to be fixed.

8. Once the fix has been verified its QA team's responsibility to close the bug.

9. Now the work doesn't stop here, there are several other steps involved before releasing this fix in the actual product. The fix could be related to any particular version of the product, based on that there could be various internal patches[ a structured bundle of the fixed files ].

10. Only after the thorough testing of fix, the patch is ready to be released, which is, it can be directly given to the customer or it can be bundled along with several such patches and included for the next release of the product.

This entire cycle of the bug is managed by the bug reporting tools. Usually all the product companies have there own bug reporting tools. Others mostly use bugzilla or a variant of it. I would suggest all the students reading this post to have a look on bugzilla.

Reporting a bug is also an art, a bug without a proper bug report is very difficult to understand hence the fix gets delayed. Here is a very good article about this.

There is also a nice pdf [4 pages only πŸ™‚ ]on bug tracking basics by software testing and quality engineering magazine. It will help you to know some of the very common FAQs like what's the difference between a Developer and a QA.

Office 2007 UI preview

April 6, 2006

Have a look at the new UserInterface of Office 2007 from the video

new user experience involves

  • The Ribbon inplace of menubar and toolbar 
  • Contextual tabs
  • Galleries
  • Live preview
  • Customizable quick access
  • Mini toolbar

Microsoft, Office 12 | digg it