4 ms·
That's why you should only hire contractors, and shouldn't pay them while a build is running. Saves more money that way, and you don't have to care much about
by rpigab 4y ago
That's why you should only hire contractors, and shouldn't pay them while a build is running.
Saves more money that way, and you don't have to care much about build duration.
- panzerboiler 4y agoHallo. I am a contractor. Why you shouldn't pay for the time my machine is building your project?
- wruza 4y agoCause you can work on other projects meanwhile, multitasking is easy and never helps making mistakes. It’s also easy to contract on your terms. You just say “I want that for very cheap” and get flooded with interested contractors. /s
- DocTomoe 4y agoGood luck finding contractors who will agree to these terms. Waiting for built times is dead time which is filled with other activity, like documentation, or reading through the next requirement. What you will achieve with this policy is minimizing the number of build processes, from a few times a day to once or twice a week (or less), which is exactly what you do not want from a CI/CD / DevOps environment.
- randomdata 4y agoBesides, you're not paying for one's time. You're paying for one's availability. The difference is subtle, but significant.
- chronial 4y agoIs this sarcasm about our absurd reality of hyper-capitalism or are you serious?
- rpigab 4y agoI'm dead serious, we have to embrace the gig economy and everything it has to change in our lives for the better. Why would I be paying for bathroom breaks and idle time? I wish there was software to count how much time is lost when users minimize all windows or switch to desktop, so I could deduct it from their pay. I know some of this idle time is spent thinking about problems to solve related to the job, but it's something that can be done in your free time, or while commuting.
- chronial 4y ago> Why would I be paying for bathroom breaks and idle time? You want your workers to compile the code before committing it and moving on to the next task, right? But don't feel like you should pay for that? Or are you assuming that people are like fleshy machines that can just store the data they just used on disk and work on something else while the compilation is running and then they just put that data back into RAM once the compilation is done? People don't actually multitask that well. > [...] some of this idle time is spent thinking about problems to solve related to the job, but it's something that can be done in your free time, or while commuting. Now that just sounds like you don't feel like you should pay workers that do intellectual work for their work at all – they can do their work in their "free" time? By that logic I don't see why you don't just pay for the 1 minute it takes to commit the code once it's finished – in the end that's all you care about. Why would it be your problem how they get there?
- weego 4y agoIf you think you're paying a good developer for their time, you're stuck in Victoria era thinking.
- WesolyKubeczek 4y agoAs if it's something bad.