Wednesday, August 31

Social Media revolution is fad ?

As posted by MIKE_CORSO in his post Many business organizations, companies, private shop owners, individuals think whether to use Social Media marketing or not.
Well, this video below here, is your answer :

PS : At Qalixa , we are still researching what channels to use for marketing and what not. We encourage readers to comment their views.
Please visit Qalixa

Wednesday, August 10

Implement Google Instant Page technology to your website or blog

Google announced about Instant Page technology on their webmaster central blog here. The technology behind this technique can be implemented in your website or blog, and can be very effective if you have idea, around where next user is going to navigate. On Chrome, this will make the next page webpage load in no time. So, what change you need to do on your website / blog ?
Here are the details :

1) Websites :
Open your website template and, before the closing </head> tag, include the following code:
<link rel="prerender" href="">
The URL ( should point to the next “logical” page. For instance, if you have a photo gallery or a long article that spans multiple pages, the URLs could point to different parts of the page. The prerender tag on Page 1 could point to Page 2 while the prerender tag on Page 2 could point to Page 3 and so on.
A small business website may link to their “about” page or the “products” pages from the “home” page using the Instant Pages tag as that’s where potential customers are likely to go once they land on the home page.
2) Wordpress blogs :
Open your header.php file, copy-paste the following code inside the closing <head> tag  and you’re done.
<?php if (is_archive()) { ?><!-- Instant Pages for Google Chrome -->
<link rel="prerender" href="<?php echo get_next_posts_page_link(); ?>">
<?php } ?> 

3) Blogger blogs :
Still searching for a way to enable it. If any of our reader has the code to change in template or header, please share with us.


Here is the video describing about Google's Instant Page technology :

This is the chart for this year's browser trend from Stat Counter.
If you compare the graph, you will come to know that chrome is increasing popularity, and we are hoping that after this instant page loading feature, chrome will gain more popularity.

Note : One of best thing apart from the fact that it is free, Qalixa works with majority of browsers.

Wednesday, August 3

Adding Poll to your blog

Dear viewers, we have recently added Poll into our blog, using third party free tool, Poll Daddy.
We came to know about Poll Daddy from, from here.

We are finding it quite interesting, and we hope, our viewers will be polling in their votes :)

If you want to know how to create a Poll, you can check at this link.

We are looking for more suggestions and are thinking, what should be the update frequency of the polls, any suggestions ?

We do hope, we will be able to find out some interesting polls for our viewer(s)

Njut till dess och ta hand 
-- Isabella 

Further Readings : 

Tuesday, August 2

Programmer’s guide to stress-free coding

A project’s building block is a programmer.Generally, they are always under heavy stress, because of project deadlines, commitment, technical complexities, mis-understandings, communication gaps , pressure from management etc…
For a stress-free coding, Qalixa team is using a simple approach of “RIDBIO” concept !
“ Get the Requirement & Use your Imagination ;Discuss the imagination & Build in Order “

1) Understand the Requirement & Use your Imagination
Before starting your work, use your imagination to understand what the task/ requirement is. Try to imagine how much elements will be used, how much classes may need to code, on UI part, how much changes or new elements are required.
thinking-monkey1                thinking3
2) Discuss the Imagination & Build in Order
Coding is like building a house, how are you going to build your house ?
As shown below in graphic, or you are going to build it in order ?
Many times it happen that a programmer gets away with complexities of the project, and is unable to deliver what he is capable of. One should always stay focussed about task, and should try to complete it in smaller parts.
Do the simple bits first, you may never need the complex bits ! ”
Always code the simple cases first. Not only is it more likely that the requirements and specification process has got the simple cases right (more people at more meetings can understand them), but it's less hassle if you have to throw them and start again.

3) Test , test, test & TEST
Think of it like building a house.Before you build the walls, you want to make pretty sure the foundations are stable. If you find a fault with the footings after the walls are raised it's going to cost a lot to get it fixed. If the roof's gone on and the furniture is in place, that same fault might cost more than the house to put right. One should make sure that every function, every method, every object, every subroutine has an associated automatic test harness which tests normal, limit and error cases for every parameter, and makes sure it does the right thing.
4) Working in  ‘ bits ‘
If you work regular office hours, try to divide your work into chunks you can complete in a day. Try to build and test some sort of subsystem by the end of a week, and so on. It seems obvious, but it's amazing how many people don't even try to do this.
First it lets you free your mind from clutching onto part-finished work. I've never been able to fully relax if I have remember where I've got up to for tomorrow; well, not and do any useful work the next day, anyway. The second benefit is the happy "kick" we all get from "closure". I get a physical sense of release when I've finished and tidied a piece of work; a feeling of "now I could do anything!".

Summarizing up the things :

Coding : At the end of the day, if the program doesn't run and make money for the client, you haven't done anything.

Testing : You have to know when you're done. The tests tell you this. If you're smart, you'll write them first so you'll know the instant you're done. Otherwise, you're stuck thinking you maybe might be done, but knowing you're probably not, but you're not sure how close you are.

Listening : You have to learn what the problem is in the first place, then you have to learn what numbers to put in the tests. You probably won't know this yourself, so you have to get good at listening to clients - users, managers, and business people.

Designing : You have to take what your program tells you about how it wants to be structured and feed it back into the program. Otherwise, you'll sink under the weight of your own guesses.

Rate the Post