“When you get into a tight place and everything goes against you till it seems you could not hold on a minute longer, never give up then for that is just the place and time that the tide will turn.” - Harriet Beecher Stowe (1811 - 1896)
In response to my rant, Francois from Netvibes team replied and suggested to use the following url:
http://www.netvibes.com/?reset_cache=1
which resets the cache. I am assuming that it be used after one has moved stuff around to reset the cache and commit the recent changes.
But it all changed a couple of days ago…I was feeling a bit adventurous and decided to move some of the feeds around with an intention to organise it in a better way. I added new tabs (groups) and moved stuff around. I refreshed the browser after finishing the rearrangement and none of the recent changes were saved for some reason. All the feeds were categorised in the “Lost and Found” section and all other sections that I had created just disappeared.
I was absolutely perplexed and I had to go through all my feeds again and sort them out into different categories…let me tell you this it was painful and tedious. Well I got home and opened up my Netvibes and there is a whole list of the tabs that I created in the afternoon along with the old ones for some reason. so I had to delete the duplicate sections and sort it out again. I have not been back to work yet and I just hope that it is not all messed up again.
I have sent my feedback to the Netvibes team and I hope they would fix this issue or atleast let me know if it was a user error.
Do you know what this is used for??
Well I did not know that you could do this in microsoft word but apparently the use of Shift + F3 cycles through different types of cases so it would change the selected text from all uppercase to all lowercase to camelcase and so on.
What a discouraging start to Adobe Flex faddism. I meticulously tried the link on this page (Download Flex Builder 3) several times but it just does not work…I will try it on a different computer and see what happens.
“Being the captain of the Titanic is no fun.” - said by the GM’s Chairman in a letter to the shareholders
Read the rest here
Comments section on the youtube or any other forum is quite an interesting read and one does find rather exciting stuff on it…check the following video out on you tube and see it for yourself. This was one of the findings of my hours well spent on youtube…click on the link please
Getting used to a new gym is similar to getting used to a new programming langugage…
Do you agree???
Belated Merry Christmas….limited access to a computer has delayed christmas by a day on my site…apologies.
Bugs are inevitable in any piece of software and we all are aware of the fact that developers cut corners to make the software work. As far as hacks go unnoticed they can be referred to as calculated risks. Bugs sap our energy and focus and leave us exhausted at times.
My observation says that “Bugs initiates a blaming game”. I know it is a bad practice to pass the blame but I have committed such sins in the past and may do so in the future. In an astute manner, I always look up the error message on the Google unless of course I know what the issue is straightaway. Googling is often considered the single best unsophisticated approach to resolve the pandemonium thrown by the bug. I whole heartedly support such actions but I have changed my perspective recently following a simple revelation.
In fact I have come up with an epithet to describe it aptly – “Google is in fact not the solution to every issue”. Issue here is actually a software bug…you can substitute your definitions. Google is quite fallacious in the sense that it presents a whole list of solutions which are time consuming and in addition often highly irrelevant. It is in fact a text based search engine and in a given situation presents the searcher with an overwhelming list of links. This situation is commonly known as the “Information overload”.
Few weeks back I encountered an error message and immediately googled it with a hope to resolve the issue as soon as possible. I started sweeping through the links and tried to follow few solutions but nothing seemed to work. Finally after spending hours on it I went back to traditional manner of bug fixing. I roughly knew the source of the issue …I narrowed the issue down to one possibility and did few tests. Within minutes I knew the exact cause of the issue and not only that I even fixed it within five minutes. I am sure you have been in such situations before and you have formulated better escape plans…but unfortunately I did not and ended up spending hours on it.
Sometimes it is futile searching google or playing the blame game. One should investigate the code first and employ traditional bug fixing procedures. I thought it be a good idea to share my bitter experience with my fellow developers out there.
