It has often happened with me that what I considered was a problem was only a symptom of the real one. For the user, the symptom is usually the problem itself. That is why it is all the more important for a problem solver to sift through the symptoms and arrive at the underlying problem. One of the differences between the symptom and a problem is that the symptom will usually be more about the environmental factors and external systems. This includes those problems that occur intermittently are not easily reproducible. Instead of giving up on them, acknowledging a deeper problem and investigating a wider area might lead us to the real problem.
skip to navigation | content
ifacethoughtsfreshthoughts
- Icons Of The Last Generation
- Xfce 4.10 Now Available
- WordPress For Prototypes
- Slackware Needs You
- Get The Source
- Trying Out i3
- Why Don’t Gnome Shell/Unity Become Tiling Window Managers?
- See How Linux Is Built
- Indian Open Government Platform
- Improving Unix Commands
contactme
badgesand...
- accessibility
- blogging
- books
- cms
- css
- design
- desktop
- entrepreneurship
- estimation
- feeds
- for executives
- india
- linux
- mindworks
- mobile
- open source
- process
- programming
- project management
- rant
- requirements
- roi
- software for business
- standards
- testing
- this
- toc
- tools
- usability
- web
- wordpress
- wordpress global variables
This is the weblog of Abhijit Nadgouda where he writes down his thoughts on software development and related topics. You are invited to subscribe to the feed to stay updated or check out more subscription options. Or you can choose to browse by one of the topics.