4 ms·
Sysadmins get this. You want a service to remain exactly the same for your 4 year deployment and work the whole time. You don't want updates. I feel the same f
by calinet6 14y ago
Sysadmins get this. You want a service to remain exactly the same for your 4 year deployment and work the whole time. You don't want updates.
I feel the same for my day-to-day work. It better work, it better not change much, and I better like it. ST2 fulfills all those needs, and I expect no updates. The OP may not understand that philosophy, but he should respect it.
- nsmartt 14y agoIt's interesting that this is the same mindset as non-technical consumers. They don't want anything to change, ever, because it breaks their workflow. I suppose there's a tendency for some to be on the bleeding edge. I suspect everyone has to find their own middle ground. There are areas where we prefer the latest and greatest, and then there are areas where we want stability. I find that I'm fond of the bleeding edge until it starts to interfere with my work-- though it could probably be argued that it interferes with my work all the time and that I fail to notice because it's routine somehow.
- calinet6 14y agoInteresting parallel. I think the motivations are actually similar: for both sysadmins and non-tech end users, change is a disruptive thing rather than a desire; what they desire is a stable working product as a means to an end. It's only high-tech early adopters who see change as a benefit for its own sake.
- bdunbar 14y ago> They don't want anything to change, ever, because it breaks their workflow. I'm like that. I'm willing to change, but there needs to be a compelling reason. I think of 'my computer' the same way I do my work area. If my phone is over -there- one day and the next day it's over _here_ .. it's distracting. I spend all day reaching out with the wrong hand when the phone rings.