|
|
The machine has you by the nuts. What value are you placing on your own time and sanity?
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
At the moment I value learning and experience more than time, I guess.
Not for very long though, not THIS much time anyway 
Looking for solutions 
|
|
|
|
|
You're young man. So for right now it doesn't seem like a big deal, but years and years of spending 4 hours on the road every day will rob you of everything good in life. People on their death beds always talk about their relationships (improving them, etc.) with the people in their life being the most important thing ever. You cannot and will not have a healthy life with healthy relationships if you spend that much time devoted to the day job and commuting. You may as well hand them over your soul right now.
In short... move or telecommute. It will take its toll man, it's only a matter of time.
Jeremy Falcon
|
|
|
|
|
Get a cheap hotel in the week, do the job, prove yourself indispensable, then start working remote
|
|
|
|
|
IIRC you are renting so suck it up and move your ass nearer the work you enjoy. You did like living where you are, you are not going to in the future it is nowhere as nice as when you could spend some time at home.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You recall incorrectly, I bought my house and have a mortgage.
If I were to sell my house and start renting I'd be left with a lot of money on the bank.
Selling my house won't be a problem, buying my way back into the neighbourhood will, there's not much for sale there (especially my house since it's a bit bigger than other houses).
|
|
|
|
|
Sander Rossel wrote: I bought my house and have a mortgage
That makes it much more difficult, what are the rent returns like? We rented our house out and moved to avoid a 2 hour commute and we had 2 kids in school.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I'd probably make a good profit if I rented out my house, so that's a good thought.
|
|
|
|
|
Scrum by the book sounds like religion, both superficial enemies of mine. Not as bad as traffic, but I ride a bike, so when I commute, there is seldom a problem. Except for raging thunderstorms.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
—Aleister Crowley
|
|
|
|
|
Back in 2000 I got my first proper job at a nationally recognised software house. I would have been mad not to have taken it. Trouble was it was a 3 hour round trip each day. I used to leave the house at 6am and get back around 6 - 7pm. My commute was dictated by roadworks and traffic.
As soon as I completed my probation (which was 6 months) I moved to be nearer the job and took my family with me. I was exhausted every evening, and my weekends were spent catching up on rest and sleep.
Commutes such as that are not kind to the work / life balance. You need to enjoy your life, not just your work. I speak from hard won experience.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
One day you will be over it and look for another job.
Meanwhile enjoy the learning experience!
|
|
|
|
|
Exactly, that's how I currently look at it!
Thanks
|
|
|
|
|
Sander Rossel wrote: I now drive 1200 a week!
So you live ~100 km away from work?  That's a terrible commute by any standards. In the long term, I don't see how you can keep it up.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
120 km actually
|
|
|
|
|
I was assuming some non-commuting driving, as well.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Old Commute: roughly 90/minutes, assume no public transit problems
New Commute: roughly 18 min.
I essentially have added an extra day of life to each week.
If they transfer me 'back' - I'm outta here.*
* It's only fun if it's fun.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
Regardless of the version, are you capable of performing the tasks assigned?
Yes, newer version may have newer features, but are they necessary to perform the task?
|
|
|
|
|
Tim Carmichael wrote: Regardless of the version, are you capable of performing the tasks assigned?
"Sort of." Some OS projects I want to use are built for at least C# 6.0, which means I would have to go through and revert the code back to C# 5.0. And I'm not wasting my life doing that because the IT people refuse to upgrade their remote build processes.
The irony is that while we're using VS2015, we have to set the the target C# version to 5.0!!!
|
|
|
|
|
Tim Carmichael wrote: you capable of performing the tasks assigned?
Any real programmer should be capable of performing any task in pure assembly language. That being said, just because one can/is capable, doesn't mean he should.
|
|
|
|
|
Tim Carmichael wrote: Regardless of the version, are you capable of performing the tasks assigned?
Yes, newer version may have newer features, but are they necessary to perform the task?
In the short term these questions are reasonable. In the long term? Not so much.
The more any IDE/framework/package/library/etc ages, the less likely it is to upgrade cleanly when jumping multiple versions. Old features are deprecated and later removed, etc., forcing extensive rework. As Murphy says, pretty much anything that can go wrong, will go wrong.
"well, just re-write it!"
Every time someone says that I roll my eyes. It's rarely that simple. All too often the organization is either behind or barely keeping up on current things, so adding a rewrite in just doesn't fit. Ideally I agree with re-writing, but my idealism died a long time ago ...
On the other hand, starting with a relatively new version of everything is a good choice. It puts off the need to upgrade longer than starting with older version(s). When the newest version becomes stable (in the case of Microsoft, after the 2nd service pack is released ) compile the program in the new version. If the compile is clean, keep it. If it's not clean, look at the problems and triage.
Another reason for keeping current is hiring. Need new people? Good luck finding someone good who wants to work in technology that is 3 to 5 revs back. Been there, it truly sucks to find an excellent candidate with all the right skills and great references ... who looks at me like I'm nuts when I tell 'em what versions that company mandated. 
My current project is VS2015, C# 6, .NET 4.6. Once the project goes to Production, we'll evaluate if going to VS2017/C# 7/.NET 4.6.2 is a good idea. We will not upgrade in mid-development -- there's nothing in the newer version we need although we know we don't need the headache of a mid-stream upgrade. Once the product goes to production we'll evaluate the newer versions. It is likely that the next project will be VS2017/etc., although at this time CORE is not on the plate as we don't need it.
|
|
|
|
|
So, we went from DLL Hell, to IDE Hell, to IDE+C# Version Hell...
Since the first one affected USERS, it had to be fixed.
But I cringe at the versioning going on with .NET and C# versions.
And how old projects never recompile cleanly on a new VS version.
Thankfully we have VMs.
But I totally understand managing the build cycles and defining how/what we support.
Otherwise you get a mismatch of requirements for the products across the enterprise.
So much complexity...
|
|
|
|
|
Honestly, C# isn't that bad. My biggest headaches were trying to staff a Java project where the client mandated all components were versions 3 to 6 years old. Kept finding good people who had no interest in working with old technology.
As both a consultant and an FTE, I agree with that. We need to focus on building and maintaining our resume so that we remain marketable. Working in "ancient" technology doesn't often help in finding that next contract/job.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif)
'ing archaic.
