lshw -html > sysinfo.html

You may need to install it first… For Debian and Ubuntu users installation is simple..

sudo aptitude install lshw

You can find the detailed information about lshw from the following page: http://www.ezix.org/project/wiki/HardwareLiSter

After putting a little thought into it, for me it comes down to two words, new and challenging… It’s these two words that makes software development so addicting as well as fun.. As developers we are always looking for that high, however we can’t always get it, making it better, making it more efficient keeps us going, with a reward in the final product…

New….. new is obvious, writing anything new is fun because it’s void of the same old structure, new code is fun to write but what’s even better is the underlying framework in a new environment, or better yet something you’re convinced, per google, has never been done; or posted anyway. New could also be a paradigm shift, for instance that first time instead of parsing a Notes view you walked an xml file, or used a new language to walk that same Notes view.

Challenging…. the challenge draws you in, or makes you step back, and look at it, you make notes on paper and then start typing, only to turn away to make more notes. Lately the most challenging things I’ve worked on take more time thinking on the way to work then they do writing. Imagine taking a picture, easy enough, now imagine taking the picture as Ansel Adams would do… On your commute to work tomorrow think about the subject, the angle you want to shoot at and the angle of the sun… and then execute. Which one takes longer? As for the picture, is it rewarding? Now that’s CODING…

So to some up these maybe the reasons why geeks like us just love to code day n night..

Swirl uses algorithms, metadata, and facial recognition software to distinguish between structures, places, people, and even time of day in digital images. For example, if you search for “New Delhi,” you will get sets of New Delhi state maps, and various scenery of the state. As you drill down further into the results, you get to see more tightly refined sets of images based on what you choose.

Clicking on any of the subgroups opens a window into additional “sub-clusters” of pictures categorized by factors such as angle, time of day, and whether an image is a close-up or a panorama.

We can play with Image Swirl at Google Labs.

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. — Antoine

What is a good application? or lets put it this way what defines a good application? It’s not just one thing, of course, there is no magic formula for making a good application.

What makes me love an application or what i think is a good application: the buttons and features should be in the right place. This is one of the reasons why i love applications by Google. Nearly all their applications make sense.

Example: I was working on a Word as well as an Excel document today and I was thinking that wouldn’t it be great to be able to access this document from anywhere. In other words, I wanted to upload it somewhere. The first thing that strikes anyone is to Gmail it to myself so I have a copy in my mailbox, but then I though: I’m sure Google is smarter than that, and they already have a better solution. And they already do, at the top of the page, next to Gmail and Calendar, there is Documents. Which does exactly what I expected it to do. This, for me, is what defines a good application. It’s made by people who already thought of what you want, and implemented it in the most logical and reasonable way. All I have to do is think “where would I put the button if I was a programmer/user of this feature?” and I will find it instantly.
Cheers

A software development cycle is a structure imposed on the development of a software product. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.

I’l  share with you for the first time the details of the cycle. The following are the important steps in the development cycle.

1. Programmer produces code he “positively believes” is bug-free.
2. The product is tested by the testing team and they find 30 bugs.
3. Programmer fixes 15 of the bugs and explains to the testing team that the other 15 aren’t really bugs, they are so called “special features” in the product.
4. Testing team again tests the product and finds that five of the fixes didn’t  work and also discovers 15 new bugs.
5. Repeat steps 2 to 4 ten more times.
6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
7. Users find 250 new bugs.
8. Original programmer, having cashed his royalty check, is nowhere to be found.
9. Newly-assembled programming team fixes almost all of the 250 bugs, but introduce 456 new ones.
10. Original programmer sends underpaid testing department a postcard from Hawaii. Entire testing department quits.
11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
12. New CEO is brought in by board of directors. He hires programmer to redo program from scratch.
13. Programmer produces code he “positively believes” is bug-free.

So all computer science students, learning various kinds of development cycles remember those cycles never comes into use in real world…