Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12345»»»

How Far Will You Go (To Work)? Expand / Collapse
Author
Message
Posted Wednesday, August 10, 2011 9:16 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Today @ 6:43 AM
Points: 6,779, Visits: 1,859
Comments posted to this topic are about the item How Far Will You Go (To Work)?

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #1158177
Posted Wednesday, August 10, 2011 10:13 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, June 13, 2014 12:40 PM
Points: 461, Visits: 753
It depends on what stage of life I was in.

At one point I was willing to drive whereever, however, as long as needed. I used to drive from far out suburban Chicago to pretty much downtown. Commutes over an hour, for a warehouse job, were ridiculous, but I didn't know any better.

Then I migrated into professional positions. It took time, but I was able to find a job about 5 minutes from home with a market leading company. I took a big step down, both in pay and in responsibility. Within 6 months I was back where I was in pay and job. Within the first year I was far ahead. With the short distance, pay, responsibility and respect, it was a great place to work.

Next I changed careers again into computers. I took a huge pay cut, and although I had moved farther away this job was slightly closer than the previous one at about 30 minutes. A very poor company, I left when they moved to Minnesota with the claim that "it doesn't snow much there"... Yeah right.

I worked as a consultant next. Do you count the drive or the flying time I had to sometimes do? The drive in was 70 minutes, home was 1-3 HOURS depending on I284! ARRRGGGHHHH. I gave it up after almost getting killed three times by three (or was it four) trucks on one night coming home. Found something within a half hour again.

After the terrorist issue a lot of people were out of work, I was no exception. I changed careers again, still computer related but different than what I did. I am now about 10 miles from home, the drive ranges from 15 to 40 minutes depending on how stupid drivers are at the time. You know, it might snow next week, I better drive 20 in a 55MPH zone to be safe!

Of all of them, I can't say any one drive was less stressful. Chicago traffic is the worst in the world as far as I am concerned, and I have driven in LA, Washington, Atlanta and other major cities. Those are NOTHING compared to the windy idiot driver city. Does it matter how long it is, I prefer shorter, but what would be nice would be to be able to get on the road and go, instead of hitting every traffic light, because drivers can't find the gas pedal. I would gladly drive 40 minutes if I could actually go, I can't stand a 10 mile drive that takes just as long. I feel THAT is a waste of my time.


Dave
Post #1158184
Posted Wednesday, August 10, 2011 11:50 PM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 29, 2013 12:54 AM
Points: 2, Visits: 28
I drive 1 hour one way, by car.
Depending on the traffic condition and the time of day I leave home or office this could vary between 1 hour and 1 1/2 hours.
It is the price I pay for getting the best of both worlds, IT and the outdoors. We own a rural property under the guise as a farm on the wayside of the farthest city borders.
I do remote into the office occasionally but the connection speeds here does not make that a real pleasant or productive experience so it very rarely used. So for the privileged joy of starry nights combined with a good career I have accepted that drive/traffic time is a part of life, as even in the worst of traffic days I just cannot fathom living in the concrete jungle.


DSF
Post #1158197
Posted Thursday, August 11, 2011 12:43 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:58 AM
Points: 23,005, Visits: 31,496
Most of my jobs were fairly close, 5 minutes to 30 minutes. That, of course, doesn't include the two jobs I held between November 1989 and March 2005.

The first job (after four months unemployment) was a 90 mile (on a good day 1.5 hours) one way commute. Did that for 3.5 years and no telecommute option.

The second position (after 5 months unemployment, and a short stint contracting for the previous employers software vendor) was a 68 mile one-way commute (about 1.25 hours). At first the only telecommute option was during the evenings if there was a system problem. That changed after about three years and I started working from home one day a week with the option to do so if the weather and road conditions were unsafe. The telecommute option died during my last year with this company.

What I find interesting about the long commutes; actually helped me work out solutions to problems, and I couldn't explain to people how I did it day after day. Heck, I drive to Denver today and I wonder how I did it for 15 years.

I don't want to do it again. I'm getting too old to spend that much time in the car. Plus, I think I lost out on some important family time, even though I left early and was usually home by 5 or 6.

I think a good commute time should not exceed more than 30 minutes. Anything longer, you should consider moving closer to work if you can.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1158210
Posted Thursday, August 11, 2011 1:27 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 3:12 AM
Points: 1,610, Visits: 5,482
Speaking personally, I would rather have a slightly longer commute than move deeper into the city to get to work--I like being able to see the occasional piece of greenery and not be constantly breathing petrol fumes! At the moment my commute varies between about 1.25 and 2 hours a day, depending on traffic.

Edit: That's both ways, by the way--I don't think I'd want to do a one-way two hour commute!
Post #1158215
Posted Thursday, August 11, 2011 1:44 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 3:40 AM
Points: 1,620, Visits: 1,066
I have 45 minutes by cycle (3 times a week on average), or 30 minutes by car each way (12 miles). I'll be honest, I would not like any longer, it is a bit of a waste of life. I'd encourage anyone who can to ride in when possible - it does make me feel a lot better.
Post #1158224
Posted Thursday, August 11, 2011 1:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 12, 2011 8:22 AM
Points: 1, Visits: 11
Most IT people in the Home Counties (the counties around London) commute into London, doing either car-train-tube or car-train-walk, so I would guess commutes average 60-90 minutes. Mine is currently 60 mins.

People within London will use normally use the tube (subway), but getting from affordable suburbs into the City also probably takes 60 mins. Personally, a 60 min journey which is mostly the train is bearable but mostly tube is not.

I've had a few contracts outside London with an average car journey of 30 minutes, which were good. However, anything longer is unlikely as contract rates drop off dramatically as soon as you go further away from London.
Post #1158225
Posted Thursday, August 11, 2011 1:51 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 3:47 PM
Points: 837, Visits: 1,259
Probably depends on how desperate I am for work at the time. At the moment, 30 minutes is about my max. I live far enough away from major city areas that there's no public transportation until I'm > 1/2 way to my destination. At that point, I might as well keep driving. I've seen some great job offers, but with the traffic conditions I'd easily be looking at 45-60 minutes minimum and likely work hours that would put that commute right in the middle of rush hour. No thanks.

If I really need a job, I'd be more likely to take a job requiring a longer drive. The pay is decent, but I hate losing that much time to just being in a car. I would definitely try to trade that off for working remotely. That brings other challenges, but at least traffic isn't one of them.



Post #1158230
Posted Thursday, August 11, 2011 2:05 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, July 21, 2014 4:57 AM
Points: 1,049, Visits: 3,002
I've certainly never done any crazy distance commutes (one of my wife's cousins used to commute daily in the UK from Kent to Birmingham - not far off 200 miles each way), but I've also never had a job within walking distance. I've lived and worked in London, meaning commutes of about an hour each way. I've lived outside London and commuted in, and that's ended up about an hour and a half each way. Currently, I live and work outside any major cities, and my commute of about 15 miles takes about half an hour.

All this said, the company I work for has a lot of benefits for me, many of which I didn't know about when I first joined. My decision of whether the commute was worthwhile was largely based on normal criteria like salary and proximity of similar comparable jobs. Now, I'd have to include much more subjective things too, such as how much it's worth to work for a company that treats me well, or is as flexible as this one is with regard to remote working, school holidays, domestic emergencies and so on. As a result, if I had to move house, I'd be happy to increase my commute by an hour each way to stay working where I do, but would probably reject a new job offer somewhere else that involved an hour and a half journey.


Semper in excretia, sumus solum profundum variat
Post #1158235
Posted Thursday, August 11, 2011 2:09 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 2:26 PM
Points: 2,422, Visits: 7,437
In my previous job, I used to commute 2 and a half hours each way - when the traffic was exceptionally good! I used to set off at around 5am to be in for 9am (normally arrived between 7:30 and 8:30), then get home anywhere between 8pm and 10pm. Stayed there for 11 months, before getting a job nearer to home (20 minutes each way).

My reasoning was simple - I worked in pubs until I was 24, but for three of those years I was studying at university to get a degree in computer science and move into Development. When I graduated, I was originally quite picky about location - 6 months later I was much less picky and took the first thing that accepted me



Not a DBA, just trying to learn

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better, quicker answers on SQL Server performance related questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



If you litter your database queries with nolock query hints, are you aware of the side effects?
Try reading a few of these links...

(*) Missing rows with nolock
(*) Allocation order scans with nolock
(*) Consistency issues with nolock
(*) Transient Corruption Errors in SQL Server error log caused by nolock
(*) Dirty reads, read errors, reading rows twice and missing rows with nolock


LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!
Post #1158237
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse