Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Not true. A shift is the amount of time you are expexted to be working for your employer. This period of time usually has very strict start and end [wall] time. All the time after that is yours. If you have multiple shifts - folks from the other shift will start working on their tasks as soon as it starts.
There is no need for 2 devs on different shifts work on the same ticket. But that does not mean it is not possible or that it's useless. It all depends on how well can you manage your tasks, how well can you distribute your work in the team. -
@netikras Salary is a thing.
-
@Root and this is related how?
-
@netikras With salary, you're expected to complete a certain amount of work, not be present for a certain amount of hours. It's a fundamentally different trade / contract, somtekms referred to as a "gentleman's agreement." There are no shifts on salary.
-
@Root umm.. I am working shifts and I still have agreed on my salary 😁
if you are hired to complete/release the project then yeah, it's possible that you are charged for work done. Yet it's still possible to work on project-basis and be charged per-hour :)
there is more than one payment model you know :) -
@netikras I worked at a company that gave me salary but tracked hours. I worked an extra 9 hours one week, then got sternly chewed out the next week for being 30 minutes short. 😕 They just used salary as a way of getting out of paying overtime. Made me very angry.
That's not how salary should work. -
@Root this is shit.. Where is that? "The land where dreams come true"?
I don't think we have that bad employers over here. At least I haven't yet heard of any cases like that. -
@netikras It was only the one employer. Every other place I've been salaried was very lax with scheduling and overlap. As long as I got my work done, they didn't care when it got done, or how many hours I put in.
-
@netikras is English your first language? (Not derogatory)
-
@arcsector nopes, far from that. Why?
-
There's likely to be clashes here because this is *very* culture / industry dependent, and people's experiences will therefore differ.
I've seen companies where "shifts" really do apply to devs, because they need an entire 24/7/365 dev team on standby for disaster recovery purposes. Of course, most of the time there's no disaster, so it was just normal dev work.
Opposite end, I've seen companies where they don't really care when in the day you work, and where in the world you are, as long as you're clearly doing your work. -
@AlmondSauce @351483773 and the SA's are responsible for the product lifecycle management post-release. The only thing devs should be responsible for is bug patching and security patches.
-
@arcsector Usually, but not always. In some sectors, you've got clients willing to pay (very) big bucks to have an entire dev team on standby 24/7. If you've then got devs that are willing to accept those big "overtime" bucks for working in unsociable hours, I don't see the problem personally.
The word "shift" in reference to a workday should NEVER be used in a dev environment. There is noservice that needs to constantly be maintained, thats what customer support is for. A shift gives the mentality that you have a set time that you are responsible for a service.
Devs are responsible for finishing a product on a deadline; that is not a shift, that is a fucking workday. I especially hate it when managers refer to them as shifts, because it shows just how little they understand what the devs are doing. They think of bug fixes like they think of flipping burgers; a task that performs a service. It's not a service, stop acting like it is.
rant
i know my logic is flawed fuck you