Oomphing!

Today’s lesson…
Microformats are “Designed for humans first and machines second, they are a set of simple, open data formats built upon existing and widely adopted standards. Instead of throwing away what works today, microformats intend to solve simpler problems first by adapting to current behaviors and usage patterns”
Microformats follow few basic principles
  • Solve a specific problem
  • Start as simple as possible
  • Design for humans first, machines second
  • Reuse building blocks from widely adopted standards
  • Modularity / embeddability
  • Enable and encourage decentralized development, content, services
Reduce, Reuse & Recycle!
 oomph
Oomph – The new playground for Microformats . Oomph is a Microformats toolkit for web designers, developers and users. Its is an amalgamation of applications: an Internet Explorer Add-in built in C++ that finds Microformats on a page; a cross-browser HTML overlay built using JQuery that aggregates Microformats; a set of beautiful CSS styles for Microformats; and a Windows Live Writer plug-in written in WinForms for inserting hCards.
Oomph can be downloaded from Codeplex . So, ready to Oomph?

 

band

Advertisements

Like love, great design requires no explanation

 explanation
For any software, design is crucial to its existence. In this changing era where we find more people tied to desktop computer screen & PDAs than in the park, its time to re-design the experience. The location of visual elements in the UI has a huge impact on how the user interprets information. The closer it is to the user’s thought process, the better experience the user will have. The interface should be intutive. It is always good to expose or display only what is required, and refrain from showing all of the software literature on the user interface. A good design communicates by itself. That’s how its related to human nature, it communicates.
Those who design software are people and those who use software are people; let’s explore the homosapien mind.
I don’t need to know the laws of thermodynamics to use a toaster, or do I?
So next time you design a software, swim in the homosapien mind for a while!

The 209 Becauses

Back again, I just can’t budge… it all depends on how well we understand the requirements. Do not slip into an analysis paralysis mode but make sure you know what you are doing. Nick has provided an exhaustive list which I call ‘The 209 Becauses’. I still need to ram them down my concious, they are worth ramming after all. To start with they are arranged into 5 levels; I figured out there are 3 Level 1’s ->for the Business Stakeholders, Business Analysts & Software developers respectively, 14 Level 2’s, 51 Level 3’s, 93 Level 4’s and 48 Level 5’s.
Did I hear what’s the Problem?
Problem: The requirements for software, as delivered by typical business analysts, is not sufficiently clear, insightful, or well understood to develop software systems that meet the needs of business users.
 because
got to get over it!

The Greater Sum… Let’s Talk!

The value of the ‘Whole’ is greater than the value of parts put together! does that sound paradoxial? But yes, thats very true & logical. “When you combine the ever-growing power of devices and the increasing ubiquity of the Web, you come up with a sum that is greater than its parts”. When silos break and synergy is established, the possibilities & opportunities explode. SaaS (Software + Services) is all about these possibilities.
Aristotle’s Metaphysics – Unity reconsidered
 1+1 = 11
The Synergism Hypothesis explains the evolutionary imapct. So ready to evolve?
Let’s Talk…