Showing posts with label Technology. Show all posts
Showing posts with label Technology. Show all posts

Tuesday, March 13, 2007

Javascript and Google Searchbot

Let's say you have made an online document management software, which is built with ajax flavor. No matter , how well is your app, it can turn out to be worthless, if people cant discover the right doc through their search keys that your app is supposed to give.

Yesterday , i have found a tiny research work of a guy, who proved it right that contents generated by javascript can never be indexed by a search engine (ex. Google).

As we all know search engines cant never execute javascript.Therefore,the growing number of ajax apps could lead goggle to think in different way for their search algorithm or it just don't matter.

Read it out..
does-google-index-dynamic-javascripted-content


A Reader's Toolbox

Many companies using Google standards for business internet marketing online for better reach of customers. For successful business you do not need only cheap domain name. In many countries free wireless internet is used boosting up servers for fast communication. You can see in many webhosting reviews use of internet booster is recommended for better speed. Especially for site hosting because to increase your website traffic your site should take less time to download. Many people use data recovery programs if they lost their data but if you keep you use pc backup then you can get

Saturday, December 2, 2006

Looking back at your mistakes..

After the end of every iteration in a project life cycle, we always think that we could have write our program more smartly. Humans are meant to made mistakes, but great ones are those who learn from them. Making mistakes is inevitable but we can't avoid them completely.

it is often a real good practice that we all do some analysis after accomplishing each iteration. For ex, all the developers can sit together for a coffee and discuss frankly what is best and the worst things they have done so far and what should be done to avoid those in future .But in reality, i believe that most of us never do this kind of practice.So what needs to be done, if we really want to impose this on a team. Any guess ?

Solution 1 :

Every organized company has a issue tracking system(we at Pageflakes never do a task unless it is properly entered in an issue tracker). Issue tracker is a great source for monitoring progress and accomplishment for an iteration. Issue tracker always says , how a bug has occurred or how to do a new task but it is never meant for the word "Why". Developer does his assigned tasks and marks it with some status and forwards it for further processing , but what if before changing a task , we ensure that a developer must answer, "how did i do the task?". If developers are pretty honest , at the end of each project cycle this can help to create a true project metrics that can become a true life saver someday.

Solution 2 :

These days we all use Microsoft outlook . i believe this is the holy grail in modern age to keep you organized round the clock. In outlook we can create an event send it to others as well to keep us synced( For ex: "Send weekly status") . Now, is it possible to send a reminder that will tell a developer to send the mistakes and best things that he/she has done for particular issue? I believe this is great.


So far, these are only two from many tactics that we can follow to rectify our mistakes. But the question is, at the end of the day do we really care?

Finally i leave you with this quote i found(source : http://www.codinghorror.com/)

Look, Mike," Tomas said. "I can hand off my code today and call it 'feature complete', but I've probably got three weeks of cleanup work to do once I hand it off." Mike asked what Tomas meant by "cleanup." "I haven't gotten the company logo to show up on every page, and I haven't gotten the agent's name and phone number to print on the bottom of every page. It's little stuff like that. All of the important stuff works fine. I'm 99-percent done."


Good day!

Monday, November 13, 2006

Sql Server 2005 - Powerful paging using WITH statement

Sql server 2005 formerly named "Yukon" , is bundled with loads of features that can rock a database developer's mind.Among many of features, one thing that is truly mind blowing is the mighty WITH statement. Previously , it is a real tedious task to do paging from database. Some of the option were creating temp table, using cursors,etc. But, now is the time to forget those tricky methodologies.

Lets consider a simple table called employee( emp_id, name, salary). Now, suppose that we need to create a gridview with paging. One option is to bring all the data from database and do the paging in client-side and another one is to do selective fetch. In both cases we can use a stored procedure that takes some parameter and returns a resultset.

Let's see the following...

CREATE PROCEDURE GetEmployees
@Status int,
@StartIndex int,
@PageSize int
AS

WITH FilteredList( [emp_id],[name], [salary], [RowNumber])
AS
(
SELECT
[emp_id],
[name],
[salary],
ROW_NUMBER() OVER ( ORDER BY [ID] DESC) AS [RowNumber]

FROM
Employee
)

SELECT
*
FROM
FilteredList
WHERE
RowNumber BETWEEN (@StartIndex + 1) AND (@StartIndex + @PageSize)


Actually , the WITH creates a in-memory data structure based on ROWNUMBER or any other identifier that we might give. Finally, we separate the result based on that identifier. But anyway in the end it makes our life more simple at the end of the day.

Here in Pageflakes, i use it almost everywhere possible, which surely saves my time and nothing else.