4 ms·
> I’ve yet to find a service that saves 5 hours per week per employee. How do I estimate the actual savings in time? Sure you have, albeit by another name like
by dijit 6y ago
> I’ve yet to find a service that saves 5 hours per week per employee. How do I estimate the actual savings in time?
Sure you have, albeit by another name likely.
GitHub/Gitlab as a service easily saves more than 5hrs a week.
I have custom slack bots that easily save me a couple hours a week in aggregate.
Then there’s services such as managed CI or, heck even things like the “search” function on a wiki, those are all things that can be provided by a service.
But a tool like this will show you much much it might be worth investing in a service vs hiring someone dedicated and running something yourself.
> Work expands to fill available time. Will my employee use that time to the company’s advantage?
There’s two points to this argument;
1) if I save an employee time, what value does that give me?
2) if I’m an employee, and efficiency is improved; I still have to be in the office 9hrs per day.
The first argument is at odds with the notion that most knowledge worker jobs tend to only be around 40% productive.[0]
There’s no evidence that it goes lower than that; most of the reasons that percentage is so low, though, is friction. Friction can take many forms such as a bureaucratic process for approvals to change things- all the way to “needing to talk to that one guy who knows the thing, and teams is having an outage”. It’s hard to quantify, but there are so many frictions and there is evidence to suggest that removing these frictions increases productivity, not lessens it. (To a value of 80% which represents a significant increase).
(I will supply citations when I get to my pc, this comment is from a phone)
Problem 2 goes into the expectation that if you’re in the office you must be busy- there’s no value to you the employee of the company gets more efficient! Except obviously that’s not true in a more macro sense; I wouldn’t argue that. I would instead argue that the feeling of empowerment that comes with doing actual work and not busywork will make people more engaged and not less.
You wouldn’t feel motivated in your job if you had to assemble your chair each time you wanted to sit in it, it would be tedious and not challenging and certainly cause you to mentally check out.
[0]: https://talentculture.com/how-knowledge-workers-really-spend-their-time/ https://talentculture.com/how-knowledge-workers-really-spend...
- wil421 6y agoHow does Github save time over the predecessors like self hosted a Git or SVN repository?
- deviantfero 6y agoPull request management, code reviews, CI flows, github actions, github does have many features that other git clients don't, certainly not a self hosted git or SVN repositories, and those features save a lot of time just in the ease of initial setup.
- jeremymcanally 6y agoPermissions. I specifically remember talking to Tom and Chris about how that was really the main point of rage that spawned the idea of GitHub (and its original slogan “Git hosting: No longer a pain in the ass”).
- ori_b 6y agoDid you spend 5 hours per week per employee managing permissions in git?
- cmbell715 6y agoMaybe not managing permissions directly. But I could easily see a number like that, or higher, being plausible if you consider clean up from junior devs accidentally pushing to development/main branches thinking they were on their feature branch. Which is an issue directly solved by permissions.
- jeremymcanally 6y agoSetting up and managing keys, spinning up new repos, etc. would suck up an inordinate amount of time. This was especially true when I worked at consultancies. Blocking developer work with “Sorry gotta wait on Todd to add you to the server and set you up on Git,” when Todd would avoid it like the plague because it sucked would lose a lot of time. If you averaged the time out, it may not have hit the five hour per week mark, but it combined with other time savers (linking Git directly with the issue tracker for example instead of having to figure out how to cross reference them) easily did/does.
- 6y ago
- lucideer 6y ago> Sure you have, albeit by another name likely. > GitHub/Gitlab as a service easily saves more than 5hrs a week. > I have custom slack bots that easily save me a couple hours a week in aggregate. > Then there’s services such as managed CI or, heck even things like the “search” function on a wiki, those are all things that can be provided by a service. These are three highly subjective, very unconvincing statements. I use Github, Gitlab, multiple slackbots (some I wrote, some others wrote), managed CI, and a few search services internally in my company every day. I have no confidence that any of them are timesavers in the way that you state. Slackbots in particular have been shown to use more time than they save (context switching is extremely costly). Github is a source-code host that ads distracting social features, notification queues, etc. all which can add to an employees distraction load and decrease productivity when compared to a more basic code-host. I'm not saying they don't save time in aggregate, but there's certainly arguments on either side.
- mattigames 6y ago> all which can add to an employees distraction load and decrease productivity when compared to a more basic code-host. Is a bit naive to think those features are the ones distracting the employees, when if you watch a developer at work 98% of the time-wasters are the strongly attractive ones: YouTube, Instagram, etc.
- lucideer 6y agoDunno where you work, but this doesn't correlate in my workplace.
- dijit 6y agoI know a company which I will not name, that was passing source-code around with a USB drive. Their version of an SVN lock was basically 'who has the USB stick right now'. And while this is an absurd and extreme example (and a true one, crucially) you can't deny that github would have saved those developers countless hours. Maybe even enough hours to pay a person full time to manage something on-site: but that's why this topic (and the OP's site) is interesting, how do we quantify it?
- projektfu 6y agoTo the extent that a service avoids yak shaving, definitely that value can be quantified. How do I know it won’t cause yak shaving though?