|
Same for me (I'm 51 now). Top !
|
|
|
|
|
I moved as a developer in manufacturing and utility environments since 1986.
For the first 13 years, I was on call for the items I developed/supported, and that was 7x24x365. There was also 24x7x365 on site coverage by a separate group - they 'operators' if you will. They had a manual for each system describing common issues and how to address them. We would only be called if there was an issue they couldn't resolve.
Even at that, having in depth knowledge of the system, we could resolve most of the issues without having to log in.
Then.. new position - not on call for the first 7 years while I was a contractor; the last 5 years were as an employee and then I was on call for everything in the department, and that was about 1 week out of 8.
In my position now, I am on call every 10 weeks. All 'calls' are handled as text messages and support can be done remotely - I take my laptop phone every night.
So... on call? I like what I do for a living; I develop relationships with the rank-and-file and they appreciate the service they get.
|
|
|
|
|
I also work in the manufacturing industry and have had many years of on call support. Even though it is not always fun, it was very valuable.
In the manufacturing industry (industrial robotics) it really helps to understand the environment in which these machines operate. It is important to also understand all the different kinds of users.
This domain knowledge is what differentiates the great developers from good or average developers. The code we write is not always that difficult, but without an understanding of the context, it is easy to make the wrong technical decisions.
I am glad I did the on-call support early in my career. Definitely....
|
|
|
|
|
I don't do "on-call", I don't do more than eight hours per day unless I decide that I need/want to, and I don't work weekends.
How do you make that happen? Write good code. It also helps if you're a bit of a prick.
I once walked out of an interview when they said, "We expect you to work at least 60 hours per week."
I responded, "On salary? Are you out of your f*ckin minds?", and I was out the door.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: I responded, "On salary? Are you out of your f*ckin minds?", and I was out the door.
You took time to respond to them? So kind of you.
As soon as that 'we expect 60 hours' was said just walking out without saying a thing would have sent the loudest message.
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
That is kind of what I did. They sound almost the exact words.
We were going to schedule a visit the their office, when I learned that they really expected 60-70 hours with on-call, I cancelled the trip.
|
|
|
|
|
You can tell them off while getting out of your chair and walking you know.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Work so that you might live, do not live to work.
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
Liked your motto.
|
|
|
|
|
NotPolitcallyCorrect wrote: Work so that you might live, do not live to work. I believe the absolute reverse of that.
If you don't love your work, your life's not worth living.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: your life's not worth living
Ah, so, if you spend your whole life working, when do you have time to live?
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
Everyone* spends the majority of their waking hours working.
If you hate your work, you're pretty much screwed.
* Everyone with a full-time job, that is.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I don't hate my work, it has plenty of fun moments and is fulfilling, but I wouldn't do it if I didn't get paid. There are dozens of other things I would be doing if I didn't need the money; family, friends, enthusiasms. It's an amazing world out there beyond my programs. That's how I see it.
That reminds me of a great quote about the "world" though not specifically relevant to the discussion.
" You can't take a little bloody nose, maybe you ought to go back home and crawl under your bed. It's not safe out here. It's wondrous, with treasures to satiate desires both subtle and gross. But it's not for the timid."
- Q, Star Trek Next Gen
|
|
|
|
|
Sorry, but all Sci-Fi quotes directed at me have to be either from Firefly or The Hitch-Hikers' Guide to the Galaxy (but NOT the godawful disney atrocity!)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You must forgive me, as a young mind I suckled upon the breasts of Kirk and Spock.
|
|
|
|
|
Well, it's full of stars, and maybe I'm getting to old for this.
I'll phone home, to see if anyone's in, and get the smeg out of here, if there is.
Don't worry, though; I'll be back.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: If you hate your work
If has nothing at all to do with loving or hating your work.
Speed of sound - 1100 ft/sec
Speed of light - 186,000 mi/sec
Speed of stupid - instantaneous.
|
|
|
|
|
Ah, that explains it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Programming (development) is my hobby, also my work. I like working, but when my free times could at any time belongs to my boss or company, it is time to hang the hat and move on.
|
|
|
|
|
Good attitude.
Giving a little extra when there's a rush on is one thing, but I've worked place where there was always a rush on.
The down side of leaving, though, is that situations like that are where you can get to know some really great people.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Depending on the amount of time on call. I spent four years working on site for a bank. As a company we provided 24/7 support and normally someone would be on site within 30 minutes if there was an out of hours outage. As the tech lead of the team, most calls escalated to me. Yup 24/7 support for 4 years. Even during my holidays I was on call; I took to going diving as I could keep away from the phone.
I made a lot of money with that gig and only gave it up because I was getting married and there was no way on earth I could have kept it going with a wife [especially not Mrs Wife] and now with kids. There was a life, but it came after work. I partied very hard and lived a very good life, but it was a bachelor's life.
veni bibi saltavi
|
|
|
|
|
I turned down one from a start-up in 2008 for the same reason despite the pay being very handsome. Money is one thing, but my peace of mind and my time with family is not for sale.
|
|
|
|
|
Now that all my children have grown and moved out. I will value my time alone peace and quite. I would rather spend time play video games (FO4 anyone) than on the phone.
|
|
|
|
|
Leng Vang wrote: the pay is among the best ($250-300K)
Geez, at that pay rate, I would have happily written a diagnostic flowchart script and call-forwarded my phone to a call center in India, probably could get away with paying them $15K to take the calls.
Marc
|
|
|
|
|
See my response to him. I call bullshit
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|