Overblog Suivre ce blog
Administration Créer mon blog
15 janvier 2013 2 15 /01 /janvier /2013 15:01

Hello Guys again,

Although my blog main concern is about SQL server, I like to share my experience in the telecommuting field, misconceptions and reality.

1. Telecommuters works more efficiently than Onsite people

I believe hiring telecommuters is eventually more efficient than OnSite people. Obviously, a telecommuter would come once a day or once a month or once a week or once a year to show his face and gather information but with the current technology, web conferences, training over the internet have become much better and easier so that working remotely is not even a new thing.

Most outsourcing in India is done via Skype, teamviewer, Webex, etc... Internet is also the main advantage for those Indian people, besides cost.

Also, flexibility, project-based budget and cost eficiency can be added to that. The telecommuter is happy about being at home most of the time and therefore can take a pay cut OR is ok to be independant and have less paid leave OR cost less in unnecessary additional cost like food, travelling reimbusement, professional phone, car, desk, computer, etc...

I have been successful to work with many consulting companies and direct clients this way. None of them thought I was not up to the task and get their money back easily.


2. Key to social progress

Another big aspect for telecommuter is that TIME IS MONEY! The first thing you gain is your commute. You gain like 1 to 2 hours on average PER DAY! of time, note considering transport cost as well.

But not only that, it is more difficult to accept part-time jobs when working on-site as your commute is proportionnally more expensive in terms of time and transport cost.

A telecommuter could easily ask to work part-time or 3/4 of the time instead of full-time. The company has interest in this as well as he can cut his cost.

Finally I think it is a key to social progress. Why do we need full-time people. Why a full-time DBA? Isn't it much better to get 3 part-time DBA, so that when one go to vaccation, the other is there. If one does nto know the answer, the other one does... Why not having talent for less cost and having several talents at once? Everybody is happy and this is why I call it social progress! 

Telecommuters usually do not care too much about career or money. They care about their well-being. They accepted to eearn less to spend more time with their family and/or their hobby. 

I believe it is the future for social progress! I hope people agree with me and hope that in the future companies would thinki about this way!

Telecommuting does not mean outsourcing to Indian people in India. It just mean getting more talents that chose well-being instead of career!

I am open to any comments on that.





Repost 0
Published by clementhuge.over-blog.com - dans General
commenter cet article
5 avril 2010 1 05 /04 /avril /2010 16:07

Clement Lyon

Hello All folks interested in the data-tier!

Given the importance of networking and internet, I decided to create this blog to interact with my fellow DBA friends and friends-to-be.

I am an independant Senior Sql server consultant who advises all-sized companies on how to develop a secured and scalable storage solution for their most important projects related to database.

I particularly like to work with all kind of industries, as it is always interesting to see how different the storage solution can be whether you have a very visible front end such as E-Commerce or very very busy traffic between servers such as telecommunication companies or Payment industries.

Lately I have been focusing on how to store exotic data like videos, xmls, geolocalization, bitmask and hierarchy data into relational or non relational data-tier. I also try to see how we can develop real geographic active-active redundancy at the data-tier to move forward. Architects emphasize with fairness, the fact that high availability does not go well with performance. The more available is your data, the more ressources you will use to get your data spread out and reduce at minimum all SPOFs. And if you want to reduce the performance bottleneck, you will need to invest in development, software or hardware.

The data-tier cannot stay centralized now as we need to ensure both performance and availability, Web and application tiers store their codes in different locations, so as to be database. Questions about latency will set up your data-tier architecture.

This blog will then focused on high volumetry, non relational key-value / column stores, in-row or in-lob data storage, data compression, IO etc.. all the effective source of optimization we need to focus on at the data-tier.

Talk to you soon folks!

Repost 0
Published by clementhuge.over-blog.com - dans General
commenter cet article