design

IT Product design when left in the hands of the developer tends to include everything the programmer, or the team thereof, is capable of accomplishing. As a result the product tends to have many Swiss Army knife type features, but lacks any real cutting edge, since the development time gets distributed around many small features while the main functionality does not get enough attention to be robust and mature (read fault tolerant, adaptible, portable, et cetera.) The latest technology article on HBR, Feature Bloat succintly discusses this phenomenon and its cures:

Hey there,
I just signed up, thanks Ajay.

I came across this website Threadless, which has a very innovative approach to attract the community to submit t-shirt designs and rewards the best designers upto $2000, $1500 in cash, $300 store credit and $200 as club membership. The designs submitted as vector art, gets scored by the community for a period of 7 days, and the winner is chosen by the community. Really cool concept.

Anyway, I am a fashion designer here in the UK and am looking for someone in India that has links to a knitted fabric supplier.I am also looking for manufacturers with a good reputation, that do European designer clothing in small quanities.

Layout with inbricated tables is obsolete, this is no secret nor revolution!

Using <div> layers associated with CSS is the new integration and layout format for all documents.

This new "fashion" brings it wave of fanatism and most of all incomprehension and wrong usage. To sum it up, people are thinking " all right! I can get rid of all my tables and use <div> instead! ".

Then they have as many div> in their code as they had cells in their tabs, and they think that layers and CSS are no improvement at all.

This is what happens in many cases, <div> are overused, there are too many imbrications and sub divisions just to say " oh, I'm using <div> ... ".

Most modern browsers support the :hover selector for any html element. This is cool, because it enables you to, for instance, apply a mouseover effect to table rows <tr> using only CSS. IE however, with a market share of > 90%, does not natively support :hover on elements other than links <a>, rendering the entire :hover concept useless. Or does it?

IE allows you to look at the stylesheets and each individual rule with javascript. Normally, IE returns UNKNOWN for anything it does not support. This seems to sound reasonable at first, but it's not. For instance, a p:first-child would change into p:unknown, and a a[href] would altogether be molested to a capital UNKNOWN. Now why can't it just return the true selector text?

The biggest conundrum any organisation wishing to add "Knowledge" to its assets and bottomlines faces is that of differentiating between vital knowledge and just plain trash. Huge amounts are spent annually on storing data of all kinds as part of Knowledge. Emails, internal communications, memos, MoMs, you name it, the organisation has it.

All Knowledge pundits agrees that the key differentiator between good, core "knowledge" and just plain chaff thats exchanged within and external to an organisation, is the component called re-usability.

The moment one steps into this domain, Pundits pull out their tablets, indexed and normalized effectively, to come up with as many definitions to "re-usability" as they have for Knowledge.

Recently I have used LG U8110, Nokia 6680, Motorola A1000 mobile phones. But I always find that they dont satisfy every requirement I have. I like some functionalities of one phone and functionalities of another as well. Here is what I would expect from my phone...

I am a real life photography lover, music listener and heavy mobile application user.

So combining features I would like mobile having following: