A note to self.
Jun. 10th, 2009 11:37 amWhen asked "So, do we actually *need* you for anything prior to $UNSCHEDULED_FUTURE_EVENT", the correct answer is not "not unless something breaks unexpectedly", even if that answer is true in every meaningful sense.
Yay for talking myself out of a job!
(I still have several other jobs and these guys intend to contract me again for $UNSCHEDULED_FUTURE_EVENT once it stops being unscheduled, and I've got an ongoing contract for "in case of emergency, call John". But I don't have the regular, guaranteed income from this specific client any more.)
Yay for talking myself out of a job!
(I still have several other jobs and these guys intend to contract me again for $UNSCHEDULED_FUTURE_EVENT once it stops being unscheduled, and I've got an ongoing contract for "in case of emergency, call John". But I don't have the regular, guaranteed income from this specific client any more.)
(no subject)
Date: 2009-06-10 04:18 pm (UTC)(I can never come up with one myself).
(no subject)
Date: 2009-06-10 05:02 pm (UTC)(no subject)
Date: 2009-06-10 05:18 pm (UTC)I worked myself out of revenue when I wrote/implemented a virtual disk installation on a bunch of my then-customers. I'd have the system boot up once a week, do automated OS updates, and then reboot back to a virtual disk image that couldn't be changed permanently from within, with data files stored separately from the programs and OS (A lot of these folks were using Win95/Win98 and never changed a single thing on the system year in and year out).
I suddenly went six months without them needing me to work on the machines, invariably because all they needed to do was reboot if the system started acting strange. Better than eighty percent of my repeat customers gone because I made their Windows installations stable.
(no subject)
Date: 2009-06-10 05:20 pm (UTC)(no subject)
Date: 2009-06-10 05:23 pm (UTC)(no subject)
Date: 2009-06-10 07:10 pm (UTC)'While the system is stable for the most part, I have a list of tweaks that should make the system more robust / secure / etc now that the current framework is in place'.
This is almost always the case as there's generally things you didn't have time / opportunity to do in the initial phase of implementation that can make things better / more stable. So it's also true.
But in the cases where it's 100% completely done, no tweaks / pinches / revisions? You say what he said.
The basic problem of doing good work is that there tend to be two rewards:
- More / Harder work to be done in less time.
- Less / No work because everything's fine no.
Condolences TWK.
(no subject)
Date: 2009-06-10 07:32 pm (UTC)And in this situation, they don't. I was at the "stable but a list of tweaks" stage a year and a half ago with their server and network. Now, the primary company has been purchased, and the new owners have their own IT department and policies. Meaning, they don't need me. I simply confirmed what they suspected.
(no subject)
Date: 2009-06-10 08:55 pm (UTC)Still I find honesty is the right approach because it brings them back when they *do* have the need.
(no subject)
Date: 2009-06-10 04:21 pm (UTC)(no subject)
Date: 2009-06-10 04:54 pm (UTC)Which is not the same as a regular paycheck, even if it *is* at a higher rate per hour.
(no subject)
Date: 2009-06-10 05:03 pm (UTC)(no subject)
Date: 2009-06-10 07:37 pm (UTC)Fuck that!
(no subject)
Date: 2009-06-10 08:56 pm (UTC)(no subject)
Date: 2009-06-11 03:11 am (UTC)(no subject)
Date: 2009-06-12 06:21 pm (UTC)Not sure why you think on balance that it's sad you wouldn't actually do that kind of thing.
(no subject)
Date: 2009-06-13 03:33 am (UTC)(no subject)
Date: 2009-06-13 08:58 pm (UTC)(no subject)
Date: 2009-06-14 03:44 pm (UTC)(no subject)
Date: 2009-06-16 09:22 pm (UTC)(no subject)
Date: 2009-06-17 11:19 am (UTC)(no subject)
Date: 2009-06-12 06:20 pm (UTC)(no subject)
Date: 2009-06-10 11:44 pm (UTC)